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 domain model during design sessions by challenging fuzzy terms, stress-testing concepts with concrete scenarios, and recording glossary entries and decisions 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 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 canonical terms, invents edge-case scenarios, and cross-references user statements against actual code behavior. - Use Case: While designing a billing feature, the user says "cancel the account." The Skill flags that the glossary defines cancellation at the Order level, forces a precise resolution, updates CONTEXT.md inline, and offers an ADR recording why partial cancellation is supported. ## Quick Start Help me pin down the domain terminology for our ordering system and record any architectural decisions we make along the way.
