What problem does it solve? Domain terminology drifts and design decisions get forgotten as a project grows, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens your domain model during design sessions by challenging fuzzy terms, stress-testing concepts with edge-case scenarios, and recording glossary entries and architecture decision records the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Maintains a CONTEXT.md glossary with canonical terms, tight definitions, and explicitly avoided synonyms, supporting both single-context repos and multi-context setups via CONTEXT-MAP.md. - Active Term Challenging: Flags conflicts between what you say and what the glossary or code says, proposes precise terms for vague language, and invents concrete scenarios to probe domain boundaries. - Disciplined ADR Recording: Offers architecture decision records only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using a minimal sequential-numbered format in docs/adr/. - Use Case: While designing an ordering system, you casually say "account". The Skill asks whether you mean Customer or User, updates CONTEXT.md with the resolved term, and later offers an ADR when you decide Ordering and Billing will communicate via domain events instead of synchronous HTTP. ## Quick Start Ask the assistant to help design your domain model and record the terminology and key architectural decisions in CONTEXT.md and docs/adr as you discuss them.
