add-conventionlisted

# add-convention Add a convention — but only after assessing whether it should exist and where it belongs. This skill is a gatekeeper and a router, not a stenographer. ## Step 0 — Preconditions and context 1. Confirm the repo is bootstrapped. 2. Read `CONVENTIONS.md` and `AGENTS.md` in full so you can detect overlap with existing rules and judge fit. ## Step 1 — Assess: is this worth codifying? Apply triage. Recommend **against** adding when: - It is already covered (explicitly or implicitly) by an existing convention — point to it instead of duplicating. - It is a one-off, not a recurring decision — codifying it adds noise. - It is likely to churn — premature rules become stale cruft. - It is too vague to be testable or actionable as written. Recommend **for** adding when it is a recurring decision whose ambiguity causes rework, it is stable, and it can be stated so an agent can follow it without further interpretation. State your recommendation and the reason before doing anything. ## Step 2 — Route: where does it belong? Decide the home, and explain the choice: - **Hard rule agents must obey** → a bullet in `AGENTS.md` §Hard rules, with the substance in `CONVENTIONS.md`. Use for non-negotiable constraints. - **Authoring / process guidance** → a section in `CONVENTIONS.md`. Use for "how we do things" that informs but doesn't gate. - **Shared term / definition** → `GLOSSARY.md` (if the repo has one). - **It is actually a decision, not a convention** (an ar