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 of canonical domain terms with explicit _Avoid_ lists, 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. - Live Model Sharpening: Challenges conflicting terminology, proposes precise canonical terms, invents edge-case scenarios, and cross-references user statements against the actual code to surface contradictions. - Use Case: While designing an ordering system, the user says "cancel the account" — the Skill flags that the glossary defines Customer and User as distinct concepts, resolves the term inline, updates CONTEXT.md, and offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the agent to help define the domain language for your project and record any significant architectural decisions as ADRs while you design.
