What problem does it solve? Domain terminology drifts and architectural decisions get forgotten as projects grow, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens a project's domain model 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 canonical terms and explicit _Avoid_ alternatives, supporting both single-context repos and multi-context setups via CONTEXT-MAP.md. - Architecture Decision Records: Creates lightweight, sequentially numbered ADRs in docs/adr/, but only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - Active Model Sharpening: Challenges terms that conflict with the glossary, proposes precise names for vague language, and cross-references user statements against the actual code to surface contradictions. - Use Case: While designing an ordering system, a user says "cancel the account." The Skill flags that the glossary defines Customer and User separately, 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 Help me pin down the domain terminology for my ordering system and record the architectural decisions we make along the way.
