What problem does it solve? Teams lose shared understanding of domain terminology and forget why key architectural decisions were made, leading to inconsistent language in code and repeated re-litigation of settled choices. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files that define canonical domain terms, flag ambiguous vocabulary, and list words to avoid. - Architecture Decision Records: Writes lightweight ADRs in docs/adr/ when decisions are hard to reverse, surprising, or the result of real trade-offs. - Multi-Context Support: Handles single-context repos with one CONTEXT.md or multi-context repos via a CONTEXT-MAP.md linking per-context glossaries. - Use Case: While designing an ordering system, the user says "account" loosely; the skill challenges the term, resolves it to "Customer", updates CONTEXT.md immediately, and offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the assistant to help define the domain terms for your project and record them in a CONTEXT.md glossary as you discuss the design.
