Most coding assistants behave like sharp interns with no durable context. They can write code, but they don’t reliably accumulate repo-specific understanding, and they repeat the same mistakes. A three-rule scaffold fixes this by forcing a persistent loop: inspect → write down constraints → implement → record what was learned → tighten constraints. The result is less guesswork, fewer regressions, and faster follow-on work—without prescribing templates.
In real repos, failure modes are boring and repeatable:
- The assistant guesses commands, entrypoints, or project structure.
- It applies generic “best practices” that conflict with local conventions.