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 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. - Active Terminology Challenge: Detects when your language conflicts with the existing glossary or the actual code, and surfaces the contradiction immediately. - Disciplined ADR Recording: Offers Architecture Decision Records 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 a billing feature, you say "account" loosely; the Skill asks whether you mean Customer or User, updates CONTEXT.md with the resolved term, and records an ADR when you decide Billing communicates with Ordering via domain events instead of synchronous HTTP. ## Quick Start Ask the agent to help pin down the domain terminology for your project and record any significant architectural decisions as ADRs.
