What problem does it solve? Domain terminology drifts and design decisions get forgotten as a codebase evolves, leaving future readers guessing why things were built a certain way. This Skill actively sharpens your project's domain model during design sessions by challenging fuzzy terms, stress-testing concepts with edge-case scenarios, and recording glossary entries and Architecture Decision Records (ADRs) 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. - Active Terminology Challenges: Detects when your language conflicts with the existing glossary or when terms are vague, and cross-references stated behavior against actual code to surface contradictions. - Disciplined ADR Recording: Offers to write sequentially numbered ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - 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 records an ADR explaining why Ordering and Billing communicate via domain events instead of synchronous HTTP. ## Quick Start Help me sharpen the domain model for my billing module and record any significant architectural decisions we make along the way.
