What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural decisions, leading to inconsistent language in code and repeated debates about settled choices. This Skill actively sharpens a project's domain model by maintaining a CONTEXT.md glossary and recording ADRs as decisions crystallize. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with opinionated term definitions, canonical vocabulary, and terms to avoid, supporting both single-context and multi-context repositories via CONTEXT-MAP.md. - Architecture Decision Records: Writes numbered ADRs in docs/adr/ following a minimal template, offered only when decisions are hard to reverse, surprising without context, and the result of real trade-offs. - Active Language Sharpening: Challenges terms that conflict with the glossary, proposes precise canonical names for vague language, and cross-references stated behavior against actual code. - Use Case: While designing an ordering system, a user says "account" ambiguously; the Skill asks whether they mean Customer or User, updates CONTEXT.md with the resolved term, and later records an ADR explaining why ordering and billing communicate via domain events instead of synchronous HTTP. ## Quick Start Help me define the domain terminology for my project and record the key architectural decisions we make along the way.
