ubiquitous-language

Extract domain-specific terminology from technical conversations into a UBIQUITOUS_LANGUAGE.md glossary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves communication gaps and terminology drift in software projects by extracting, normalizing, and documenting domain-specific language directly from your conversations.

Core Features & Use Cases

  • Terminology Extraction: Automatically identifies domain-relevant nouns and verbs from technical discussions.
  • Conflict Resolution: Flags ambiguous terms and identifies synonyms to ensure a single source of truth.
  • Documentation: Generates a structured UBIQUITOUS_LANGUAGE.md file that serves as a living glossary for developers and domain experts.

Quick Start

Ask the assistant to extract the ubiquitous language from our current conversation and save it to a glossary file.

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 technical conversations to build a glossary?

To build a ubiquitous language glossary, this skill parses natural language dialogue to identify domain entities, relationships, and semantic ambiguities, outputting a structured UBIQUITOUS_LANGUAGE.md documentation file.

What is a ubiquitous language glossary in domain-driven design?

A ubiquitous language glossary is a consistent set of domain-specific terms shared by developers and domain experts. It resolves communication gaps and terminology drift by serving as a documented single source of truth.

How do I resolve semantic ambiguities and terminology drift in software architecture documentation?

You resolve semantic ambiguities by identifying synonyms and flagging ambiguous terms during natural language extraction. This normalizes conflicting definitions into a single source of truth for your architectural documentation.

Can I generate a DDD glossary file directly from project onboarding discussions?

Yes, you can generate a DDD glossary file from onboarding discussions. The skill automatically identifies domain-relevant nouns and verbs from technical conversations and documents them in a structured markdown file.

Does ubiquitous language extraction work without external dependencies or architecture frameworks?

Yes, ubiquitous language extraction works without external dependencies. It independently parses natural language dialogue to identify domain entities and relationships, requiring no specific architecture frameworks to function.

When should I not use automated ubiquitous language extraction for DDD workflows?

You should avoid automated ubiquitous language extraction when your technical conversations lack sufficient context for parsing natural language, or when domain experts cannot review the flagged semantic ambiguities for accuracy.