ubiquitous-language

Extracts domain terminology from a conversation and normalizes it into a glossary file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns messy, inconsistent domain language into a clear, shared glossary so teams can align on what each term means and avoid ambiguity.

Core Features & Use Cases

  • Glossary Extraction: Scans the current conversation for domain nouns, verbs, and concepts that deserve precise definitions.
  • Ambiguity Detection: Flags overloaded terms, synonyms, and conflicting usage so the team can choose canonical wording.
  • Canonical Terminology: Produces opinionated definitions with aliases to avoid, helping product, design, and engineering speak the same language.
  • Use Case: A team discussing a DDD domain model can use this Skill to formalize terms like customer, order, shipment, and invoice into a consistent reference document.

Quick Start

Ask the Skill to extract a ubiquitous language glossary from the current 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 extract a ubiquitous language glossary from a DDD discussion?

To extract a ubiquitous language glossary, you can use a tool to scan conversational context for domain nouns and concepts, normalizing them into a consistent reference document with canonical terms and aliases.

What is the best way to detect terminology ambiguity in domain modeling?

Detecting terminology ambiguity involves scanning domain modeling conversations to flag overloaded terms, synonyms, and conflicting usage, allowing the team to choose canonical wording and align on precise definitions.

How do I normalize domain terminology into a consistent glossary file?

You normalize domain terminology by extracting domain nouns and verbs from discussions, then writing the normalized results into a UBIQUITOUS_LANGUAGE.md file complete with concise definitions and explicit relationships.

Can I track aliases and canonical terms for domain-driven design conversations?

Yes, you can track aliases and canonical terms by extracting domain terminology from DDD discussions and producing opinionated definitions that explicitly list aliases to avoid, ensuring engineering and product speak the same language.

When do I need to formalize domain terms into a ubiquitous language document?

You need to formalize domain terms into a ubiquitous language document when team discussions produce messy, inconsistent domain language and you must align product, design, and engineering on what each term means to avoid ambiguity.