Architect
draw the system, make the agent follow it
Coding agents add structure faster than anyone reviews it. Architect turns the diagram into a gate: the agent reads it, and every structural change comes back to me as a picture to approve.
Left alone, an agent invents a new service, a new util layer, a new dependency and a new folder. Each one is defensible. Together they make a codebase unreviewable in a week. A prompt that says follow the architecture is advice, not a gate.
The architecture lives in one architect.md at the repo root. Each box claims part of the repo with a glob, which is what turns a drawing into a contract. It diffs cleanly and gets reviewed in a pull request like any other file.
The agent calls check_change before it writes. A drawn edge is allowed instantly. A forbidden edge comes back with the reason. Anything new goes through propose_change, which blocks until I approve or reject it on the canvas.
A new component, a new edge, a new third party package, and a file outside every glob. Those four cover the usual ways a clean graph quietly turns into a mesh. I never approve a text diff, only a picture of my system with the change in it.
Code mode reads the repo as it really is, folder by folder, down to a function call graph with source. A bundled language server gives architect.md diagnostics, completion and rename in any editor, and a worktrees tab finds and safely removes stale git worktrees. Architect ships with its own architect.md, so it is its own demo and test fixture.
