What problem does it solve? Domain terminology drifts and architectural decisions get forgotten as projects grow, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens the project's ubiquitous language and records hard-to-reverse decisions the moment they crystallize. ## Core Features & Use Cases - Glossary Management: Maintains an opinionated CONTEXT.md of canonical domain terms with explicit _Avoid_ synonyms, supporting both single-context repos and multi-context setups via CONTEXT-MAP.md. - Language Sharpening: Challenges conflicting or vague terms during design discussions, stress-tests domain relationships with concrete edge-case scenarios, and cross-references claims against the actual code. - Architecture Decision Records: Offers ADRs in docs/adr/ only when a decision is hard to reverse, surprising without context, and the result of a real trade-off, using a minimal sequential-numbered format. - 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 picks event-sourced writes over a CRUD model. ## Quick Start Ask the agent to help pin down the domain terminology for your feature and record any significant architectural decisions as ADRs.
