Ubiquitous language

Skill DROOdotFOO/agent-skills/skills/ubiquitous-language

Extract and maintain a DDD ubiquitous language glossary from conversations. TRIGGER when: user asks to define domain terms, extract a glossary, build a ubiquitous language, or says "ubiquitous language". Also when domain ambiguity, synonym conflicts, or overloaded terms appear in conversation. DO NOT TRIGGER when: user wants code review, API docs, or module naming conventions (those are implementation, not domain).From its SKILL.md

Install

npx -y skills add DROOdotFOO/agent-skills --skill ubiquitous-language

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.3 KB, 610 tokens by cl100k_base, as published. Nobody here has run it

ubiquitous-language

Extract canonical domain terminology from conversations. Be opinionated. Flag ambiguity. Pick winners. Write UBIQUITOUS_LANGUAGE.md.

Process

Scan -- Read the conversation (or codebase) for domain-specific terms
Identify problems -- Flag: ambiguous terms, synonyms used interchangeably, overloaded terms (same word, different meanings in different contexts), terms with no clear definition
Propose canonical glossary -- Pick one term per concept. Be opinionated. If two terms compete, choose the more precise one and list the loser as an alias to avoid
Write file -- Output UBIQUITOUS_LANGUAGE.md in the project root
Merge on re-run -- If the file exists, merge new terms into existing tables. Flag conflicts between old and new definitions

Output Format

Group terms into multiple tables by domain area (not one giant table).

## [Domain Area Name]

| Term   | Definition                                | Aliases to avoid      |
| ------ | ----------------------------------------- | --------------------- |
| Ledger | Append-only record of all balance changes | log, journal, history |

### Relationships

- A Ledger contains many Entries (1:N)
- Each Entry references exactly one Account (N:1)

### Example dialogue

> "When a user transfers funds, a new Entry is appended to the Ledger."
> NOT: "When a user moves money, a new log item is added to the history."

### Flagged ambiguities

- "Account" -- used to mean both user identity and financial account.
  DECISION: use "Account" for financial, "User" for identity.

What You Get

A UBIQUITOUS_LANGUAGE.md file in the project root with canonical terms grouped by domain area
Tables listing each term's definition, aliases to avoid, relationships with cardinality, and example dialogue
Flagged ambiguities where the same word means different things in different contexts, each with a documented decision

Rules

Be opinionated -- Pick one canonical term per concept, always
Flag conflicts -- If the conversation uses two terms for one concept, call it out explicitly and choose a winner
Domain terms only -- Exclude module names, class names, function names, and implementation details. Capture the business/problem-space language
Tight definitions -- One sentence max. If you need two, split the concept
Show relationships -- Include cardinality (1:1, 1:N, N:N)
Group into tables -- One table per domain area, not one flat list
Include example dialogue -- Show how the term should be used in conversation
Merge, don't replace -- Re-running adds new terms and flags conflicts with existing definitions

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.