Staff-engineer layer for AI coding agents: routes per-edit architectural constraints for AI coding agents |
Staff-engineer layer for AI coding agents: routes per-edit architectural constraints for AI coding agents |
What it provides beyond that is:
* profiles, which can also be implemented as a directive in any prompt, eg "use CONTEXT-lite.md" as opposed to a different agent reasoning level. You'll just have to memorize them?
* opinionated choices about host implementation (for Codex use CONTEXT.md and Claude use CLAUDE.md, etc)
* cpp/Python/Universal rulesets
There's some nice invariant rules and structure[1], to be sure, but that doesn't justify the install for me.
[1] Everything in the packs are machine-readable rule atoms that are similar to SARIF and RFC 9457. There is also an avante-guarde routing system for selecting to add additional packs to context.
I’ve been tinkering on a package to capture linking, testing and gating quality output in a framework unified way across coding agents.
I would love to have a chat with you about how you see this space developing and how you look at it.
Problem I kept hitting: ask the agent for a 15-line fix, get a 500-line renovation that still compiles and passes tests.
Boffin is a small control layer for AI coding agents. Before an edit, it feeds the agent only the architectural constraints for the file it is about to touch, then makes it verify the result. Not another static AGENTS.md for the whole repo.
On DuckDB, a guided refactor landed at +17 / -17 lines with 2,104 assertions passing. Same shape of cases also on FastAPI and LangChain (in the repo examples/).
Try it: npx boffinit cursor
Also works with Claude Code, Codex, and OpenCode.
Happy to answer questions — especially if you have a place where the agent keeps "improving" load-bearing code.
The AI generated text is also not doing you any favors.