andrefigueira

Create a new .context domain folder with overview and patterns files following the Substrate methodology. Use when adding a new documentation domain to the project.

Validate .context/ files for quality, staleness, and conformance to the Substrate methodology. Run after making changes to documentation.

Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.

Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules) from the .context/ documentation. Use when setting up a project for a specific AI coding tool.

Surface the right classical law, pattern, or heuristic at the right moment during code review, architecture decisions, estimation debates, debugging, technical-debt conversations, team and org observations, operations and reliability work, security design, and any "should we do X" discussion. TRIGGER when the user (a) names a classical law (Conway's, Brooks's, Hyrum's, Postel's, Gall's, Tesler's, CAP, Murphy's, Demeter, SOLID, DRY, KISS, YAGNI, Pareto, Dunning-Kruger, Goodhart's, Parkinson's, Hofstadter's, Chesterton's Fence, Worse-Is-Better, Rule of Three, Information Hiding, Hoare's Billion-Dollar Mistake, Twelve-Factor App, Four Golden Signals, Error Budgets, SLO, Chaos Engineering, Blameless Postmortem, Principle of Least Privilege, Defense in Depth, etc.), (b) asks for a second opinion, what could go wrong, tradeoffs, or a sanity check, (c) is estimating or planning, (d) is debating a refactor, rewrite, abstraction, or new framework, (e) is discussing team structure, hiring, or org design, (f) is dealing