makes sense, keeping that stateful piece separate from the edge handlers is the right call. we hit the same split with pdf generation, anything doing real indexing or heavy io needs its own long lived process, not a function that spins up cold every request.

Show Post

Git pre-commit hooks for diff hygiene and schema checks. The model will agree with instructions in context, but when the context window fills up or it takes a shortcut, hard exit codes at the git gate are the only things that never negotiate.

Show Post

Your commit-message line caught me, same loop here. What broke it was examples, not policy. I pasted three real messages from git log into the rules file and dropped the prose. The model copies shape. My adjective version drifted within a week, the examples still hold months later.

Show Post

540 lines is about where mine started getting ignored too. What helped: keep the root file to commands and a repo map, and put folder-specific rules next to the code they cover, so they only load when the agent works there.

Show Post

Five buckets reads about right, and commit messages are what people hit first. Policy alone doesn't teach a shape, so the rules file can say "conventional commits" forever and still get prose. Cheers for laying the split out so plainly.

Show Post