Verified:GitHub

ubiquitous-language

Extracts domain terminology from a conversation into a UBIQUITOUS_LANGUAGE.md glossary with definitions and aliases-to-avoid.

1|Updated May 5, 2026

Search Tags:#documentation #domain modeling #ddd #glossary #terminology alignment #ambiguous terms #canonical definitions

Ready to run

npx skills add https://github.com/yashs33244/my-mac-claude --skill ubiquitous-language-yashs33244

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/mattpocock/deprecated/ubiquitous-language
Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill ubiquitous-language-yashs33244

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It resolves ambiguous or inconsistent domain terminology by extracting an opinionated glossary from your conversation so everyone uses the same meanings.

Core Features & Use Cases

Glossary extraction: Identifies domain-relevant terms and their relationships from the current conversation.
Canonical term decisions: Picks preferred names and lists aliases to avoid when multiple words refer to the same concept.
Ambiguity flagging: Explicitly calls out conflicting usage and recommends clearer terminology.
Human-readable output: Writes a structured glossary to UBIQUITOUS_LANGUAGE.md with definitions, relationships, and an example dialogue.

Quick Start

Extract a DDD-style ubiquitous language glossary from this conversation and save it to UBIQUITOUS_LANGUAGE.md.

Frequently Asked Questions about ubiquitous-language

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a ubiquitous language glossary from a domain modeling discussion?▼

To create a ubiquitous language glossary, the Skill extracts and formalizes domain terminology from your conversation into a structured UBIQUITOUS_LANGUAGE.md file. This output includes canonical definitions, aliases-to-avoid, relationships, flagged ambiguities, and an example dialogue to ensure terminology alignment.

What is the best way to resolve ambiguous domain terms in DDD?▼

Resolving ambiguous domain terms in DDD involves extracting an opinionated glossary from your conversation that identifies synonymous or overloaded concepts. The Skill flags conflicting usage, picks canonical terms, and documents aliases to avoid, ensuring everyone uses the same meanings.

How do I extract canonical definitions for overloaded terms in domain-driven design?▼

Extracting canonical definitions for overloaded terms involves analyzing the conversation to pick preferred names and listing aliases to avoid when multiple words refer to the same concept. The Skill automates this by writing structured definitions and relationships to a markdown glossary.

Can I generate a markdown glossary from an existing conversation with ambiguous terminology?▼

Yes, you can generate a markdown glossary from an existing conversation. The Skill processes the current discussion to identify domain-relevant terms, flag ambiguities, and output a human-readable UBIQUITOUS_LANGUAGE.md file with canonical definitions and a short example dialogue.

When do I need to formalize domain terminology into a glossary?▼

You need to formalize domain terminology into a glossary when terms in your DDD or domain modeling discussions become ambiguous, synonymous, or overloaded. Formalizing prevents miscommunication by documenting canonical definitions and explicitly calling out conflicting usage.

What does a ubiquitous language glossary file contain?▼

A ubiquitous language glossary file contains canonical definitions, aliases-to-avoid, term relationships, flagged ambiguities, and a short example dialogue. It serves as a human-readable reference to maintain terminology alignment across the domain modeling process.