What problem does it solve? Domain terms drift silently across a project: the client says "appointment," the code says "session," and the UI says "booking" — three names for one concept, or one name smeared across three concepts. This Skill catches overloaded or conflicting terminology, resolves each concept to a single canonical name, and captures the result in a GLOSSARY.md so every surface (client conversations, design system, codebase) uses the same word for the same thing. ## Core Features & Use Cases - Challenge and sharpen terms: Call out words that conflict with the existing glossary and propose one precise canonical term with retired synonyms listed under "Avoid." - Scenario-test boundaries: Invent edge cases (e.g., "a customer buys a 5-pack and books 2 dates — how many rows exist?") to force precision where two concepts touch. - Cross-surface reconciliation: Check each resolved name against what the client says, what the UI shows, and what the code names, then fix contradictions on all three. - Use Case: A salon booking app uses "booking" for both a prepaid package and a calendar slot. The Skill disambiguates them into Package, Booking, and Session, updates the UI copy and table names, and writes the resolution to GLOSSARY.md before any further code is written. ## Quick Start Ask the AI to build a glossary that resolves the conflicting domain terms in this project, reconciling how the client, the UI, and the code each name the same concepts.
