agents-md-synclisted

# Maintain agent guidance Use this skill when the root or nested `AGENTS.md` tree may have drifted, grown, or started constraining agents unnecessarily. The goal is not to document the whole repository. It is to keep inherited context small, durable, and useful at every scope. ## Place context deliberately Before adding guidance, classify it: | Destination | Admission test | |---|---| | Root `AGENTS.md` | Broadly applicable, non-obvious, durable, and costly when missed | | Scoped `AGENTS.md` | The same, but limited to one subtree | | Skill | A workflow loaded for a recognizable task | | Existing docs or source | Detailed reference material or implementation truth | | Nowhere | Generic advice or facts an agent can discover cheaply | Prefer the narrowest destination. Do not repeat the same instruction at multiple levels. ## Seed scopes sparingly A stable, major subtree may have a stub `AGENTS.md` before it has local guidance. A stub provides an obvious extension point and states only that the area currently adds no instructions beyond its parent. Do not copy root rules into it. Seed area boundaries, not every package. Replace a stub only when guidance passes the same admission test as any other scoped instruction. ## Audit procedure 1. Inventory the root and nested guidance tree. Read the affected guide, its parents, and its children fully; inspect their Git diff and relevant history. Use commit history to find likely drift, not as a requirement to summarize