Lesson · 12 min
Rules that cannot be skipped
Project instructions beat hoping the agent remembers your taste.
Put the non-negotiables where the agent always reads them: architecture boundaries, 'do not add dependencies,' 'do not touch migrations,' 'run typecheck.' A rule that lives only in your head is not a rule. A rule in a file at the repo root is.
- Keep the rules short. A 40-page bible will be partially ignored.
- Phrase as must / must not, with a command to run.
- If the agent violates a rule, stop and put the rule in the file — do not nag.