What problem does it solve? Teams lose alignment when domain terms drift, vocabulary stays fuzzy, and the reasoning behind architectural choices is never written down. This Skill actively sharpens a project's domain model during design sessions by challenging ambiguous terms, stress-testing concepts with concrete scenarios, and recording decisions the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Maintains a CONTEXT.md glossary with opinionated canonical terms and explicit "avoid" lists, supporting both single-context repos and multi-context setups via CONTEXT-MAP.md. - Architectural Decision Records: Creates lightweight ADRs in docs/adr/ with sequential numbering, but only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Active Model Sharpening: Challenges conflicting terminology, proposes precise terms for vague language, invents edge-case scenarios, and cross-references user statements against actual code behavior. - Use Case: While designing an ordering system, a user says "cancel the account." The Skill flags that the glossary defines cancellation for Orders, not Customers, asks which is meant, 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 help define the domain terminology for your project and record any significant architectural decisions as ADRs.
