What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural choices, leading to inconsistent language in code and repeated debates about settled decisions. This Skill actively builds and sharpens a project's domain model by maintaining a ubiquitous-language glossary (CONTEXT.md) and recording architecture decision records (ADRs) as decisions crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Challenges conflicting or fuzzy terms during design discussions and updates CONTEXT.md inline with precise canonical definitions and terms to avoid. - Architecture Decision Records: Offers ADRs sparingly — only when a decision is hard to reverse, surprising without context, and the result of a real trade-off — using a lightweight numbered format in docs/adr/. - Multi-Context Support: Handles 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, resolves the term, updates CONTEXT.md immediately, and later offers an ADR when the team picks event-sourced writes over a CRUD model. ## Quick Start Ask the assistant to help pin down the domain terminology for your project and record the key architectural decisions as ADRs.
