| name | ubiquitous-language |
| description | Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD". |
| disable-model-invocation | true |
Ubiquitous Language
Extract and formalize domain terminology from the current conversation into a consistent glossary, saved to a local file.
Process
- Scan the conversation for domain-relevant nouns, verbs, and concepts
- Identify problems:
- Same word used for different concepts (ambiguity)
- Different words used for the same concept (synonyms)
- Vague or overloaded terms
- Propose a canonical glossary with opinionated term choices
- Write to
UBIQUITOUS_LANGUAGE.md in the working directory using the format below
- Output a summary inline in the conversation
Output Format
Write a UBIQUITOUS_LANGUAGE.md file with this structure:
# Ubiquitous Language
## Order lifecycle
| Term | Definition | Aliases to avoid |
| ----------- | ------------------------------------------------------- | --------------------- |
| **Order** | A customer's request to purchase one or more items | Purchase, transaction |
| | A request for payment sent to a customer after delivery | Bill, payment request |
| Term | Definition | Aliases to avoid |
| ------------ | ------------------------------------------- | ---------------------- |
| | A person or organization that places orders | Client, buyer, account |
| | An authentication identity in the system | Login, account |
An belongs to exactly one
An produces one or more
"account" was used to mean both and — these are distinct concepts: a places orders, while a is an authentication identity that may or may not represent a .
