ubiquitous-language

Extract and formalize domain terminology from conversations into a structured Markdown glossary.

3|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/malinskibeniamin/skills --skill ubiquitous-language-malinskibeniamin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/malinskibeniamin/skills/tree/main/ubiquitous-language
Command: npx skills add https://github.com/malinskibeniamin/skills --skill ubiquitous-language-malinskibeniamin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and formalize domain terminology from conversations into a consistent glossary saved to a local file.

Core Features & Use Cases

  • Scan the conversation for domain-relevant nouns, verbs, and concepts
  • Propose a canonical glossary with opinionated term choices
  • Write to UBIQUITOUS_LANGUAGE.md in the working directory using the format described in the Output Format
  • Output a summary inline in the conversation

Quick Start

Run the domain-term extraction workflow and save the glossary 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 domain terminology from conversations into a glossary?

To extract domain terminology, scan conversations for relevant nouns, verbs, and concepts, then formalize them into a structured glossary document with terms, definitions, aliases, and relationships.

What is a ubiquitous language glossary and when do I need one?

A ubiquitous language glossary is a structured document capturing canonical domain terms and definitions. You need one when ambiguous terminology in domain-expert discussions causes miscommunication across development teams.

How do I create a markdown glossary from domain-expert discussions?

Create a markdown glossary by running a domain-term extraction workflow that proposes canonical terms with opinionated choices, then writes structured terminology tables and an example dialogue to UBIQUITOUS_LANGUAGE.md.

Can I update an existing glossary as conversations evolve?

You can update an existing glossary using a re-run workflow designed to evolve the glossary as conversations progress, ensuring the terminology document stays current with ongoing domain-expert discussions and developer prompts.

Does the glossary output include YAML frontmatter and structured term relationships?

The glossary output includes YAML frontmatter with name and description fields, plus structured markdown containing terminology tables, aliases, term relationships, and an example dialogue for context.

What's the best way to capture domain language from developer prompts?

The best way to capture domain language from developer prompts is applying an extraction workflow that identifies domain-relevant concepts, proposes canonical term choices, and writes a reusable glossary file to standardize communication.