ubiquitous-language
Skill1.1k starsChanged 6 months agoMITView on GitHub
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".
65 other projects use a version of this, 52 of them edited.
Trending
Quiet since August.about the whole repository
Most recently taken up by
- Robo-Co-op/robobuilder-standardedited, first seen Nov 16, 2026
- richard12511/claude-skillsedited, first seen Nov 16, 2026
- draekien/skillstheir own version, first seen Nov 15, 2026
- aegntic/compound-engineeringedited, first seen Nov 8, 2026
- chrislacey89/skillsedited, first seen Nov 4, 2026
- Boom-Vitt/skills-thaiedited, first seen Nov 1, 2026
Who's talking about karlomikus/bar-assistant
- karlomikus/vue-salt-rim“bar-assistant version”GitHub · Aug 9, 2026 · 1 reactions
- karlomikus/vue-salt-rim“Add runtime cache busting”GitHub · Feb 3, 2026 · 1 reactions
- elfhosted/enhancements“Bar Assistant — self-hosted home cocktail bar manager”GitHub · Apr 28, 2026
- karlomikus/vue-salt-rim“Optionally hide "My Shelf" and associated features.”GitHub · Apr 24, 2026
- YunoHost/apps“Add Bar Assistant to wishlist”GitHub · Feb 18, 2026
The biggest 5 of 18 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 18
Talked about on GitHub (18 times).
On GitHub · 18
- Aug 9, 2026bar-assistant version — karlomikus/vue-salt-rim1 reaction
- Feb 3, 2026Add runtime cache busting — karlomikus/vue-salt-rim1 reaction
- Apr 28, 2026Bar Assistant — self-hosted home cocktail bar manager — elfhosted/enhancements0 reactions
- Apr 24, 2026Optionally hide "My Shelf" and associated features. — karlomikus/vue-salt-rim0 reactions
- Feb 18, 2026Add Bar Assistant to wishlist — YunoHost/apps0 reactions
13 more on GitHub
- Jul 17, 2025Bar assistant — community-scripts/ProxmoxVE0 reactions · 1 comment
- Jul 10, 2025Unable to start the services on different ports — bar-assistant/docker0 reactions · 7 comments
- Feb 20, 2025Update support for taxonomies — bar-assistant/data0 reactions
- Jan 16, 2025feat: implement oauth login — bar-assistant/docker0 reactions
- Jan 14, 2025feature: oauth login — karlomikus/vue-salt-rim0 reactions
- Nov 10, 2024basic example for oidc — karlomikus/vue-salt-rim0 reactions
- May 5, 2024Configuration for Meilisearch when API Key is required appears to be missing from documentation — karlomikus/vue-salt-rim0 reactions · 2 comments
- Oct 20, 2023[feat] Show cocktail and ingredient updated at/by information — karlomikus/vue-salt-rim0 reactions
- Sep 19, 2023Add Healthcks and Depends_on Healthy Condition — bar-assistant/docker0 reactions · 1 comment
- Jul 13, 2023Home Resource Planning — claha/smart-home0 reactions · 1 comment
- Apr 20, 2023[Add]: Bar Assistant — trueforge-org/truecharts0 reactions · 2 comments
- Jan 2, 2023New dashboard — karlomikus/vue-salt-rim0 reactions
- Jun 17, 2021Software to check out — claha/dotfiles0 reactions · 1 comment
Used with
Projects with it also use request-refactor-plan, edit-article and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
simo97Skillrequest-refactor-plan
Use this skill when user wants to create a refactor plan.
Also in 42 projects that use this
simo97Skilledit-article
The user will invoke this skill to help them edit an article.
Also in 35 projects that use this
boyingliu01Skillbatch-grill-me
A relentless interview that asks every frontier question at once, round by round. Thin alias of `grilling` (#540) — upstream mattpocock/skills absorbed this protocol into grilling; XP-Gate keeps this name as the sprint-flow Phase 2 entry point so orchestration docs stay stable.
Also in 5 projects that use this
HK-hubSkillprd-to-plan
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".
Also in 9 projects that use this
AnasX7Skillscaffold-exercises
Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
Also in 30 projects that use this
AnasX7Skillsetup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
Also in 38 projects that use this
- +4 more from simo97
Other versions65 projects use a version of this.
Word for word · 0
None found.
Edited · 52
- amazingloft999-droid/mattpocock-skills★ 42299% same
- InditexTech/weavejs★ 27699% same
- loulanyue/skills★ 23199% same
- ayoubben18/ab-method★ 19385% same
- aurorasoft2/Matt_Pocock_Skills★ 13399% same
- VisualxIntelligence/mattpocok-skills★ 5599% same
- jan-bogaerts/md2★ 4299% same
- metrogg/AgentHub★ 1999% same
- Future-CX/AI-Architecture-Toolkit★ 833% same
- chrislacey89/skills★ 718% same
42 more not listed
Wrote their own version · 13
- CodeAlive-AI/ai-driven-development★ 184same name
- jscraik/Agent-Skills★ 9same name
- mattwynne/skills★ 7same name
- aiqadam/qadam-flow★ 5same name
- amit-t/skills★ 4same name
- conjurer-rich/skills★ 1same name
- draekien/skills★ 1same name
- DROOdotFOO/agent-skills★ 1same name
- jpoindexter/theft-kit★ 1same name
- Sturla22/skills★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- bar-assistant-application-serviceSkill
- clean-ddd-hexagonalSkill
The file
We split this skill into the rules it gives an agent
8 rules. 6 are common, 0 are distinctive, and 2 are very specific to this project.
6
Common
Most of the 61 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
Write a UBIQUITOUS_LANGUAGE.md file with this structure:
- Common: line 61
Be opinionated: When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.
- Common: line 62
Flag conflicts explicitly: If a term is used ambiguously in the conversation, call it out in the "Flagged ambiguities" section with a clear …
- Common: line 65
Show relationships: Use bold term names and express cardinality where obvious.
- Common: line 67
Group terms into multiple tables: when natural clusters emerge (e.g.
- Common: line 86
When invoked again in the same conversation:
- Very specific: line 88
Read the existing UBIQUITOUS_LANGUAGE.md
- Common: line 90
Update definitions if understanding has evolved
“Common” is measured: kept by at least 6 in 10 of the 61 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.mdin 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 |
| **Invoice** | A request for payment sent to a customer after delivery | Bill, payment request |
## People
| Term | Definition | Aliases to avoid |
| ------------ | ------------------------------------------- | ---------------------- |
| **Customer** | A person or organization that places orders | Client, buyer, account |
| **User** | An authentication identity in the system | Login, account |
## Relationships
- An **Invoice** belongs to exactly one **Customer**
- An **Order** produces one or more **Invoices**
## Example dialogue
> **Dev:** "When a **Customer** places an **Order**, do we create the **Invoice** immediately?"
> **Domain expert:** "No — an **Invoice** is only generated once a **Fulfillment** is confirmed. A single **Order** can produce multiple **Invoices** if items ship in separate **Shipments**."
> **Dev:** "So if a **Shipment** is cancelled before dispatch, no **Invoice** exists for it?"
> **Domain expert:** "Exactly. The **Invoice** lifecycle is tied to the **Fulfillment**, not the **Order**."
## Flagged ambiguities
- "account" was used to mean both **Customer** and **User** — these are distinct concepts: a **Customer** places orders, while a **User** is an authentication identity that may or may not represent a **Customer**.Rules
- Be opinionated. When multiple words exist for the same concept, pick the best one and list the others as aliases to avoid.
- Flag conflicts explicitly. If a term is used ambiguously in the conversation, call it out in the "Flagged ambiguities" section with a clear recommendation.
- Only include terms relevant for domain experts. Skip the names of modules or classes unless they have meaning in the domain language.
- Keep definitions tight. One sentence max. Define what it IS, not what it does.
- Show relationships. Use bold term names and express cardinality where obvious.
- Only include domain terms. Skip generic programming concepts (array, function, endpoint) unless they have domain-specific meaning.
- Group terms into multiple tables when natural clusters emerge (e.g. by subdomain, lifecycle, or actor). Each group gets its own heading and table. If all terms belong to a single cohesive domain, one table is fine — don't force groupings.
- Write an example dialogue. A short conversation (3-5 exchanges) between a dev and a domain expert that demonstrates how the terms interact naturally. The dialogue should clarify boundaries between related concepts and show terms being used precisely.
<example>Example dialogue
Dev: "How do I test the sync service without Docker?"
Domain expert: "Provide the filesystem layer instead of the Docker layer. It implements the same Sandbox service interface but uses a local directory as the sandbox."
Dev: "So sync-in still creates a bundle and unpacks it?"
Domain expert: "Exactly. The sync service doesn't know which layer it's talking to. It calls
execandcopyIn— the filesystem layer just runs those as local shell commands."
</example>Re-running
When invoked again in the same conversation:
- Read the existing
UBIQUITOUS_LANGUAGE.md - Incorporate any new terms from subsequent discussion
- Update definitions if understanding has evolved
- Re-flag any new ambiguities
- Rewrite the example dialogue to incorporate new terms
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

