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 about settled choices. This Skill actively sharpens a project's domain model during design discussions and records it in CONTEXT.md glossaries and ADR files. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with canonical terms, tight definitions, and explicitly avoided synonyms, supporting both single-context and multi-context repos via CONTEXT-MAP.md. - Terminology Challenges: Detects when usage conflicts with the existing glossary, sharpens vague terms, and cross-references stated behavior against actual code. - Architecture Decision Records: Offers ADRs only when decisions are hard to reverse, surprising without context, and the result of real trade-offs, using a minimal numbered format in docs/adr/. - Use Case: While designing an ordering system, a user says "account" loosely; the Skill asks whether they mean Customer or User, updates CONTEXT.md with the resolved term, and offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the assistant to use the domain-modeling skill to review the terminology in your design discussion and record the resolved terms in CONTEXT.md.
