ubiquitous-language

Extract domain terminology from conversations into UBIQUITOUS_LANGUAGE.md with drift reports.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill ubiquitous-language-amodelandme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/amodelandme/skill-tree-dotnet/tree/main/.claude/skills/ubiquitous-language
Command: npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill ubiquitous-language-amodelandme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and formalize domain terminology from the current conversation into a consistent glossary, 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".

Core Features & Use Cases

  • Scans conversations to identify domain-relevant nouns, verbs, and concepts.
  • Proposes canonical terms and writes them to UBIQUITOUS_LANGUAGE.md with optional drift analysis.
  • Provides a structured drift detection report to surface undocumented terms, term drift, and aliases in use.

Quick Start

Ask the AI to run the ubiquitous-language workflow on the current conversation to generate and update 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 extract domain terminology from conversations to build a consistent glossary?

To build a consistent glossary, this Skill scans your conversations to identify domain-relevant nouns and verbs, proposes canonical terms, and writes them to UBIQUITOUS_LANGUAGE.md. It also flags ambiguities to enforce consistent domain terminology across discussions.

What is ubiquitous language in domain-driven design and when do I need to formalize it?

Ubiquitous language in domain-driven design is a shared, canonical vocabulary used by both developers and domain experts. You need to formalize it when you want to define domain terms, harden terminology, and prevent semantic drift during domain modeling.

How do I detect terminology drift and undocumented aliases in domain discussions?

You can detect terminology drift by running this workflow on your current conversation. It generates a structured drift detection report that surfaces undocumented terms, identifies term drift, and highlights aliases currently in use.

Can I use this to generate a domain glossary without any external dependencies?

Yes, you can generate a domain glossary without external dependencies. The Skill operates independently to formalize domain terminology from your chat context and writes the canonical terms directly to UBIQUITOUS_LANGUAGE.md.

What is the best way to maintain domain terminology consistency across multiple modeling sessions?

The best way to maintain terminology consistency is to apply this workflow during domain modeling and glossary construction. It updates UBIQUITOUS_LANGUAGE.md with canonical terms and returns an inline summary for the current chat to enforce alignment.