ubiquitous-language

Extract domain terminology from conversations into a markdown glossary.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/Herxinsasa/Skills-Collector --skill ubiquitous-language-herxinsasa
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/Herxinsasa/Skills-Collector/tree/main/mattpocock-skills/skills/deprecated/ubiquitous-language
Command: npx skills add https://github.com/Herxinsasa/Skills-Collector --skill ubiquitous-language-herxinsasa

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often use inconsistent or ambiguous domain terminology in conversations and documentation, leading to misalignment between stakeholders, misimplemented requirements, and avoidable rework during development.

Core Features & Use Cases

  • Conversational Term Extraction: Scans ongoing discussions to identify domain-relevant nouns, verbs, and concepts.
  • Ambiguity Detection: Flags conflicting term usage, including synonyms for the same concept and the same word used for different meanings.
  • Canonical Glossary Generation: Produces a structured, opinionated glossary with clear definitions, aliases to avoid, and relationship mappings between domain terms.
  • Persistent Storage: Saves the glossary to a local UBIQUITOUS_LANGUAGE.md file for long-term team reference. Common use cases include DDD project onboarding, requirement review sessions to align stakeholder terminology, architecture discussions to standardize domain language, and domain knowledge base maintenance.

Quick Start

Use the ubiquitous-language skill to extract a domain glossary from our recent discussion about order fulfillment workflows 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 domain glossary from requirement discussions to align terminology?

Extract a domain glossary by scanning conversational context to identify domain nouns and verbs, then generating a canonical glossary with definitions and relationship mappings saved to UBIQUITOUS_LANGUAGE.md.

What is the best way to detect ambiguous domain terms and synonyms in DDD projects?

Detect ambiguous domain terms by scanning ongoing discussions to flag conflicting usage, such as synonyms for the same concept or the same word used for different meanings, outputting a canonical glossary.

How do I standardize domain language for cross-team architecture discussions?

Standardize domain language by formalizing extracted terminology into a structured glossary that includes definitions, aliases to avoid, and relationship mappings, ensuring consistent usage across teams.

Can I automatically save a ubiquitous language glossary to a local file for team reference?

Yes, you can automatically save the generated ubiquitous language glossary to a local UBIQUITOUS_LANGUAGE.md file, providing long-term reference for domain-driven design projects and stakeholder alignment.

When do I need to formalize a ubiquitous language glossary for domain modeling?

Formalize a ubiquitous language glossary when teams use inconsistent terminology in conversations and documentation, leading to misimplemented requirements and rework during domain modeling.

What are the limitations of using conversational context to extract domain terminology?

Using conversational context to extract domain terminology relies on existing discussion text, meaning it requires sufficient conversational input to identify domain-relevant nouns, verbs, and ambiguous term usage accurately.