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 Architecture Decision Records (ADRs) as decisions crystallize. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with opinionated, tightly-defined domain terms, including terms to avoid, supporting both single-context and multi-context repositories via CONTEXT-MAP.md. - Terminology Challenges: Detects when language conflicts with the existing glossary or when vague terms are used, and proposes precise canonical terms. - ADR Recording: Offers to write lightweight ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off. - 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 records an ADR when the team decides Ordering and Billing communicate via domain events instead of synchronous HTTP. ## Quick Start Ask the assistant to help define the domain terms for your project and record the key architectural decisions in CONTEXT.md and docs/adr/.
