Change Has a Rule

• Trigger: you are about to introduce a new practice, not just follow an existing one
• Search existing rules first so you amend instead of duplicating
• Propose the rule text and slug, then wait for confirmation before writing files
• Skip typos, generated output, and work that already follows an existing rule
• If the change contradicts a rule, propose updating or deleting that rule, do not work around it

Good: a new install flag is about to land, you propose meta/install-flag-defaults and wait

Bad: you ship the flag, then mention a possible rule after the files are already written