Docs

Keep the repo legible to humans and agents.

Principles

• Docs rot silently — every code change is a possible doc change
• Documentation is part of the interface; optimize for scanability, rhythm, and visual clarity, not just correctness
• Routing docs stay short; depth lives in docs/
• No duplication when a pointer will do
• Use repo-relative links for in-repo docs; external links are fine in sources and references
• Doc drift is a real failure, not polish debt

Handoffs

• Missing boot, smoke, e2e, logs, or agent-readiness infrastructure → use agent-readiness
• Need to judge existing code, a diff, branch, or PR with evidence → use review
• Need to validate your own completed change on the real surface → use verify