What problem does it solve? Teams lose shared understanding of domain terminology and the reasoning behind architectural decisions, leading to inconsistent language in code and repeated debates over settled choices. ## Core Features & Use Cases - Glossary Management: Create and update CONTEXT.md files that define canonical domain terms, flag avoided synonyms, and support multi-context repos via CONTEXT-MAP.md. - Architecture Decision Records: Write lightweight ADRs in docs/adr/ with sequential numbering, offered only when decisions are hard to reverse, surprising, and involve real trade-offs. - Language Sharpening: Challenge vague or conflicting terminology during design discussions and cross-reference stated behavior against actual code. - Use Case: While designing an ordering system, a user says "account" ambiguously; the skill proposes precise terms like Customer vs User, records them in CONTEXT.md, and drafts 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.
