What problem does it solve? Teams lose shared understanding of domain terminology and forget why architectural decisions were made, leading to inconsistent language in code and repeated debates. This Skill actively sharpens a project's domain model by maintaining a CONTEXT.md glossary and recording ADRs when significant decisions occur. ## Core Features & Use Cases - Glossary Management: Creates and updates CONTEXT.md files with opinionated, precise term definitions, including terms to avoid, 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: Offers to write lightweight Architecture Decision Records 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, the user says "cancel the account"; the Skill flags that the glossary defines Customer and User as distinct concepts, resolves the term, updates CONTEXT.md, and later records an ADR explaining why ordering and billing communicate via domain events instead of HTTP. ## Quick Start Help me build a domain model for this project by creating a CONTEXT.md glossary and recording key architectural decisions as ADRs.
