What problem does it solve? Domain terminology drifts and architectural decisions get forgotten, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens a project's ubiquitous language and records hard-to-reverse decisions as they happen. ## Core Features & Use Cases - Ubiquitous Language Management: Maintains an opinionated CONTEXT.md glossary with canonical terms and explicitly avoided synonyms, supporting both single-context and multi-context repos via CONTEXT-MAP.md. - Architectural Decision Records: Creates numbered ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Live Model Sharpening: Challenges conflicting terminology, proposes precise terms for vague language, stress-tests domain relationships with edge-case scenarios, and cross-references claims against the actual code. - Use Case: While designing a billing feature, the user says "account" ambiguously; 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-based communication between Ordering and Billing. ## Quick Start Ask the assistant to use the domain-modeling skill to define the term "Order" in CONTEXT.md and record why the write model uses event sourcing as an ADR.
