ubiquitous-language

Identify domain terms, surface ambiguities, and propose canonical glossary entries.

Updated Mar 26, 2026

Search Tags:#ddd #glossary #terminology #ubiquitous-language #domain-terms #ambiguities

Ready to run

npx skills add https://github.com/RemseyMailjard/superpowers --skill ubiquitous-language-remseymailjard

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/RemseyMailjard/superpowers/tree/main/.github/skills/ubiquitous-language
Command: npx skills add https://github.com/RemseyMailjard/superpowers --skill ubiquitous-language-remseymailjard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Domain conversations often produce inconsistent terms and ambiguous meanings that hinder shared understanding. This skill extracts and formalizes terminology into a consistent, canonical glossary that can be saved as UBIQUITOUS_LANGUAGE.md.

Core Features & Use Cases

Scan the conversation for domain-relevant nouns, verbs, and concepts.
Identify ambiguities and synonyms, and propose canonical terms with clear definitions.
Write to UBIQUITOUS_LANGUAGE.md in the working directory and optionally surface a short usage example.

Quick Start

Run this skill on the current conversation to generate UBIQUITOUS_LANGUAGE.md and surface ambiguities.

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 domain glossary from an unstructured conversation?▼

This Skill identifies domain terms, surfaces ambiguities, and proposes canonical terms in a structured glossary. It applies to technical and non-technical dialogues, requirements discussions, and design reviews to ensure shared understanding.

How do I identify terminology ambiguities and synonyms in requirements discussions?▼

You can identify terminology ambiguities and synonyms by analyzing the conversation to extract domain-relevant concepts and highlighting conflicting terms. It then proposes canonical terms with clear definitions to resolve the inconsistencies in your requirements discussions.

What is the best way to enforce canonical terminology when domain terms conflict?▼

The best way to enforce canonical terminology when domain terms conflict is by generating a structured glossary file that defines and mandates the canonical terms. This ensures all subsequent design reviews and dialogues adhere to the agreed-upon vocabulary.

Can I generate a ubiquitous language markdown file for non-technical dialogues?▼

Yes, you can generate a ubiquitous language markdown file for non-technical dialogues. The tool applies to both technical and non-technical conversations, extracting domain terms and writing the canonical glossary directly to a UBIQUITOUS_LANGUAGE.md file.

Does generating a domain glossary require any specific dependencies or components?▼

Generating a domain glossary requires no specific dependencies or components. You simply run the process on the current conversation to extract domain terms, surface ambiguities, and output the canonical glossary file in your working directory.