What problem does it solve? Domain terminology drifts silently in codebases: synonyms multiply, near-duplicate identifiers appear, and names change mid-feature without any recorded decision. This Skill makes a repository-declared glossary the naming authority for each bounded context and forces every new, changed, or suspect domain term through an explicit detect-propose-decide-record-rename protocol. ## Core Features & Use Cases - Five-step language protocol: Detect missing or duplicated terms, propose them to a human with a recommendation, record approved terms in the glossary, and rename code, tests, and schemas together in one reviewable change. - Glossary format guidance: Bootstrap a glossary from greenfield conversations or brownfield code, with context-scoped aliases, deprecation records, and an optional Contextive YAML example. - Mechanical enforcement design: Define glossary-driven lint ratchets for identifiers, test titles, and DSL verbs, with positive-control fixtures proving forbidden vocabulary is caught. - Use Case: While building a payments feature you need a verb for a customer leaving checkout. The Skill stops you from silently coining cancelCheckout, walks you through proposing abandonCheckout with a definition and example, and records it in the ordering context glossary alongside the code change. ## Quick Start Ask the agent to check whether the domain term you are about to use exists in the project's glossary and to run the language protocol if it does not.
