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 when significant trade-offs are made. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with canonical domain terms, tight definitions, and explicitly avoided synonyms, supporting both single-context and multi-context repos via CONTEXT-MAP.md. - Language Sharpening: Challenges vague or conflicting terminology during design discussions and cross-references stated behavior against actual code to surface contradictions. - ADR Recording: Writes lightweight, sequentially numbered 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 a billing feature, the assistant notices you say "account" ambiguously, resolves it to "Customer" in CONTEXT.md, and records an ADR explaining why 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 them in a CONTEXT.md glossary.
