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 by challenging fuzzy terms, stress-testing concepts with concrete scenarios, and recording glossary entries and ADRs the moment decisions 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 numbered ADRs in docs/adr/ 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, cross-references claims against actual code, and invents edge-case scenarios to force precision during design discussions. - Use Case: While designing an ordering system, a user says "cancel the account" — the Skill flags that the glossary defines cancellation for Orders, not Accounts, 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 assistant to use the domain-modeling skill to define the term "Order" in CONTEXT.md and record why we chose Postgres for the write model as an ADR.