What problem does it solve? Teams lose shared understanding of domain terminology and forget why architectural decisions were made, leading to inconsistent language in code and repeated debates. This Skill actively builds and sharpens a project's domain model by maintaining a ubiquitous-language glossary (CONTEXT.md) and recording architectural decision records (ADRs) as they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Challenge conflicting terms, sharpen vague vocabulary, and update CONTEXT.md inline the moment a term is resolved, with opinionated canonical terms and avoided synonyms. - Architectural Decision Records: Offer ADRs sparingly—only when a decision is hard to reverse, surprising without context, and the result of a real trade-off—using a minimal numbered format in docs/adr/. - Multi-Context Support: Handle both single-context repos (one root CONTEXT.md) and multi-context repos via a CONTEXT-MAP.md that maps bounded contexts and their relationships. - Use Case: While designing an ordering system, the user says "account" ambiguously; the Skill asks whether they mean Customer or User, records the resolved term in CONTEXT.md, and offers an ADR when the team picks event-sourced orders 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 the team chose Postgres for the write model as an ADR.
