domain-glossarylisted

# Ubiquitous Language Glossary This skill turns an ongoing conversation into a **DDD-style ubiquitous language** document. It scans for domain terms, resolves ambiguities, proposes canonical names, and writes a living glossary to `DOMAIN_GLOSSARY.md` in the working directory. ## When to Use Use this skill when: - You’re discussing a domain, feature, product, or system and want **shared language**. - You mention “ubiquitous language”, “domain model”, or “DDD”. - You keep tripping over overloaded terms (“account”, “user”, “customer”) and want them nailed down. You can re-run this skill as the conversation evolves to keep the glossary up to date. ## Process 1. **Scan the conversation and context** - Read the current conversation, plus any attached docs or PRDs, for **domain-relevant** nouns, verbs, and concepts. - Ignore generic technical terms (array, function, endpoint) unless they carry domain meaning here. 2. **Detect language problems** Identify and note where: - The **same word** is used for different concepts (ambiguity). - **Different words** are used for the same concept (synonyms). - Terms are vague, overloaded, or inconsistently applied. 3. **Propose a canonical glossary** - Choose **one canonical term per concept** and be opinionated about names. - For each term, write a **tight, one‑sentence definition** that says what it *is*, not how it’s implemented. - List “aliases to avoid” so everyone sees which terms should be retired i