ubiquitous-language

Extract domain terminology from conversations into a UBIQUITOUS_LANGUAGE.md glossary.

Updated Dec 11, 2024
One-click install
npx skills add https://github.com/huaxel/dotfiles --skill ubiquitous-language-huaxel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/huaxel/dotfiles/tree/main/skills/ubiquitous-language
Command: npx skills add https://github.com/huaxel/dotfiles --skill ubiquitous-language-huaxel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extracts domain terminology from conversations, resolves ambiguities, and saves a canonical glossary to UBIQUITOUS_LANGUAGE.md.

Core Features & Use Cases

  • Terminology extraction: scans dialogue to identify domain terms, synonyms, and conflicting usages.
  • Ambiguity flagging: highlights terms with multiple meanings and proposes unambiguous alternatives.
  • Glossary generation: writes a well-structured UBIQUITOUS_LANGUAGE.md in the working directory.
  • Use Case: when modeling a domain or refining team terminology, run this to stabilize terms.

Quick Start

Run this skill to generate a canonical glossary from the current conversation.

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 a conversation and build a glossary?

To extract domain terminology, this skill scans your conversation to identify nouns and verbs, detects synonyms and conflicting usages, and generates a canonical glossary saved as UBIQUITOUS_LANGUAGE.md.

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

Ubiquitous language in domain-driven design is a shared, unambiguous vocabulary used by teams to align domain models. You need it when precise terms matter for product discussions, domain modeling, or knowledge transfer.

How can I resolve ambiguities and conflicting usages of domain terms?

You can resolve ambiguities by running this skill to flag terms with multiple meanings, highlight conflicting usages from your dialogue, and propose unambiguous alternatives for your glossary.

Does this domain glossary extraction require any specific dependencies or setup?

No dependencies or components are required. You simply run the skill to analyze your current conversation and write the generated glossary directly to your working directory.

What is the best way to formalize domain terminology for team knowledge transfer?

The best way to formalize domain terminology is to analyze current product discussions, detect domain terms and synonyms, flag ambiguities, and write a well-structured UBIQUITOUS_LANGUAGE.md file for team reference.

How do I generate a markdown glossary from domain modeling discussions?

You can generate a markdown glossary by running this skill during domain modeling discussions; it analyzes the conversation for domain terms and writes a structured UBIQUITOUS_LANGUAGE.md file to your working directory.