capturing-golden-rules

To turn recurring code review mistakes into enforceable conventions, append the failure to a root golden-rules.md file with a unique ID, an origin description, and a check to enforce it in future changes.

Codifying guardrails when drift is detected involves capturing the recurring failure into a durable golden rule within golden-rules.md, establishing a check to guide future work and prevent repeated errors.

You create a golden rule by appending an entry to golden-rules.md that includes a unique ID, a description of the failure's origin, and a specific check to enforce the convention during future code reviews.

Capturing golden rules requires a root golden-rules.md file to store the rules and a SKILL.md frontmatter with a unique name and description to integrate with drift-analyst and /gc workflows.

Yes, you can use drift-analyst /gc workflows to surface and prune outdated rules, ensuring your codified guardrails in golden-rules.md remain relevant and consistently enforced across teams.