Staff-engineer layer for AI coding agents: routes per-edit architectural constraints for AI coding agents

This repo adds context on "how things should be done", much like a CONTRIBUTING.md or CONTEXT.md

What it provides beyond that is: * profiles, which can also be implemented as a directive in any prompt, eg "use CONTEXT-lite.md" * opinionated choices about host implementation (Codex use CONTEXT.md/Claude us CLAUDE.md, etc) * CPP/Python/Universal rulesets

I think we are converging on similar approaches to how deterministic quality verification with coding agents should be performed, but from different angles.

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.

https://github.com/mateffy/gesetz

Hi HN - author here.

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.