Mistake to constraint
A repeated mistake is an environment bug. Do not add another prompt paragraph first.
Order (strongest first)
- Type narrowing or runtime guard — make the illegal state unrepresentable. See
templates/runtime-guard.py. - Lint rule — copy
templates/eslint-rule.cjsortemplates/semgrep-rule.yml. Prefer an existing ruff selector fromtemplates/ruff-snippet.tomlbefore a new plugin. - Test — a regression that fails if the mistake returns.
- Directory convention — put the dangerous thing in a folder that review and CI already treat as special.
- Rules line — last. Only when 1–4 cannot hold the line.
Ledger
Keep CONSTRAINTS.md at the repo root of the consuming project. Start from the template next to this skill.
Each row: date, mistake, guard added, kind (type / runtime / lint / test / directory / rules).
Rules
- One mistake, one guard. Do not stack a lint rule and a rules line for the same bug unless the lint cannot see it.
- Do not install ESLint, ruff, or semgrep. Wire the template into tools the repo already runs.
- Do not file tracker issues. Open a draft PR with the guard and a verify-loop command.