What problem does it solve? Domain terminology drifts and architectural decisions get forgotten, leaving future readers guessing why the code looks the way it does. This Skill actively sharpens a project's ubiquitous language and records hard-to-reverse decisions as they happen. ## Core Features & Use Cases - Glossary maintenance: Challenges conflicting or fuzzy terms in conversation and updates CONTEXT.md inline the moment a term is resolved, with explicit _Avoid_ lists for rejected synonyms. - 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. - Code cross-referencing: Verifies stated domain behavior against the actual implementation using ecp structural queries and surfaces contradictions. - Use Case: While designing a billing feature, the user says "account" loosely; the Skill pins down whether they mean Customer or User, writes the definition into CONTEXT.md, and records an ADR for the event-sourced write model decision. ## Quick Start Ask the assistant to help pin down the domain terminology for your project and record the key architectural decisions as ADRs.