domain-glossarylisted

# Domain Glossary Work with the user to create or improve the project's domain vocabulary and key conceptual decisions. CONTEXT.md is the storage vehicle — the real work is getting the language right. The target CONTEXT.md is the one in the **current project's root** — not this skills-source repo's CONTEXT.md. If invoked inside the `silvio-l/skills` repo itself, treat the existing CONTEXT.md as a skill-authoring meta-glossary (not a business domain) and confirm with the user before extending it. ## Start 1. Check whether CONTEXT.md exists in the project root. 2. If it **exists**: read it fully. Identify existing terms, definitions, conventions, and conceptual decisions. Flag duplicates, contradictions, vague formulations, and potentially stale content — but propose changes only, change nothing yet. 3. If it **does not exist**: propose a structure and section outline. Ask for approval before writing anything. ## Mandatory: use the grill-me skill throughout Invoke the `grill-me` skill for every relevant term or conceptual decision: - Challenge each term: is it precise, unambiguous, future-proof, AI-readable? - Ask about scope: what does this term include? What does it explicitly exclude? - Surface alternatives and explain the trade-offs. - Point out consequences of a choice (e.g. naming collision with a library, ambiguity with another domain term). - Never silently accept vague or overloaded language. Ask questions one at a time. ## Step-by-step workflow ``` 1. Analyze