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 choices already made. 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 term definitions, including canonical terms and words to avoid, supporting both single-context and multi-context repositories via CONTEXT-MAP.md. - ADR Recording: Writes lightweight, sequentially numbered ADRs in docs/adr/ only when decisions are hard to reverse, surprising without context, and the result of real trade-offs. - Language Sharpening: Challenges vague or conflicting terminology during design sessions, cross-references claims against actual code, and stress-tests domain relationships with concrete edge-case scenarios. - Use Case: While designing a billing feature, the user says "account" ambiguously; the Skill asks whether they mean Customer or User, updates CONTEXT.md with the resolved term, and offers an ADR when the team decides Billing communicates with Ordering via domain events instead of synchronous HTTP. ## Quick Start Ask the assistant to help define the domain terms for your project and record why you chose your current architecture in an ADR.
