What problem does it solve? Teams lose track of domain terminology and the reasoning behind architectural choices, leading to inconsistent language in code and repeated debates about settled decisions. This Skill captures a project's ubiquitous language in CONTEXT.md files and records significant trade-offs as lightweight ADRs the moment they crystallize. ## Core Features & Use Cases - Ubiquitous Language Management: Maintains opinionated CONTEXT.md glossaries with canonical terms and explicitly avoided synonyms, supporting both single-context repos and multi-context setups via CONTEXT-MAP.md. - Architectural Decision Records: Creates sequentially numbered ADRs in docs/adr/ only when decisions are hard to reverse, surprising without context, and the result of a real trade-off. - Active Model Sharpening: Challenges conflicting terminology, proposes precise terms for vague language, stress-tests domain relationships with edge-case scenarios, and cross-references claims against actual code. - Use Case: While designing an ordering system, a 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 Help me define the domain terminology for my billing module and record why we chose Postgres for the write model.
