ubiquitous-language

Extract and formalize domain-specific terminology from conversations into a canonical glossary.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you extract and formalize domain terminology from conversations, ensuring clarity and consistency in terminology usage.

Core Features & Use Cases

  • Extract Domain Terms: Scan conversations to identify and extract domain-specific nouns, verbs, and concepts.
  • Identify Ambiguities: Flag and resolve ambiguities in terminology usage.
  • Create Glossary: Propose a canonical glossary with clear definitions and relationships.
  • Use Case: Ideal for software development teams to establish a common language and understanding of domain concepts.

Quick Start

Run the 'ubiquitous-language' skill during a team meeting to capture and formalize the domain terminology discussed.

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-specific terminology from team conversations?

To extract domain-specific terminology from conversations, this Skill scans your discussion transcripts to identify domain nouns, verbs, and concepts, then formalizes them into a structured glossary. It specifically flags ambiguities and proposes canonical terms to ensure shared understanding.

What is ubiquitous language in software development and when do I need it?

Ubiquitous language in software development is a shared, rigorous vocabulary used by both domain experts and developers. You need it when team conversations reveal ambiguous terminology, requiring formalization to align domain concepts with implementation and prevent miscommunication.

How do I create a DDD glossary from meeting transcripts?

You create a DDD glossary from meeting transcripts by processing the conversation through this Skill, which extracts domain terms, identifies ambiguities, and proposes canonical definitions with clear relationships, outputting a structured glossary for ongoing maintenance.

Can I use this to resolve ambiguities in domain terminology during collaborative sessions?

Yes, you can use this Skill during collaborative sessions to resolve ambiguities in domain terminology. It analyzes conversation inputs, flags terms with conflicting definitions, and proposes canonical alternatives to establish a precise common language.

What is the best way to maintain a domain glossary as project terminology evolves?

The best way to maintain a domain glossary as terminology evolves is to process new conversation inputs through this Skill, which formalizes newly discussed terms, flags updated ambiguities, and proposes canonical updates to your existing structured glossary.

Does this Skill require structured conversation input to extract DDD terminology?

Yes, extracting DDD terminology requires structured conversation input to accurately identify domain nouns and verbs. The Skill needs organized text to effectively flag ambiguities and propose canonical terms for your final glossary output.