ubiquitous-language

Name: ubiquitous-language
Availability: InStock
Author: grant-vine

Manage and normalize domain terminology in a centralized glossary file.

1|Updated Mar 6, 2026

Search Tags:#documentation #collaboration #communication #glossary #aliases #terminology #domain-language

Ready to run

npx skills add https://github.com/grant-vine/wunderkind --skill ubiquitous-language-grant-vine

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create and maintain a shared domain glossary so humans and agents use consistent terms across products and disciplines, reducing miscommunication and ambiguity.

Core Features & Use Cases

Capture canonical terms and their definitions to establish a single source of truth.
Map aliases and deprecated synonyms to prevent terminology drift.
Update and evolve the glossary in place (e.g., .sisyphus/glossary.md) as the product language changes.
Support cross-team usage during PRD reviews, architecture discussions, and design sessions to align terminology.

Quick Start

Scan project conversations and update .sisyphus/glossary.md with canonical terms, aliases, and unresolved ambiguities.

Frequently Asked Questions about ubiquitous-language

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain a shared domain glossary to align terminology across teams?▼

To align terminology with a shared glossary, you capture canonical terms, map deprecated synonyms, and update definitions incrementally in a centralized markdown file to maintain a single source of truth.

What is the best way to resolve terminology drift and synonyms during PRD reviews?▼

Resolving terminology drift during PRD reviews requires mapping aliases and deprecated synonyms to canonical terms, ensuring cross-team usage remains consistent and reducing ambiguity in architecture discussions.

How do I normalize domain language for product, design, and engineering collaboration?▼

Normalizing domain language for collaboration involves capturing structured definitions and aliases in a shared glossary, enforcing consistent terms across design reviews and architecture discussions to prevent miscommunication.

Can I update a centralized glossary incrementally as product language changes?▼

You can update a centralized glossary incrementally as product language changes by evolving definitions in place and maintaining versioned glossary entries to track terminology updates over time.

What problems does unmanaged terminology cause in cross-team documentation?▼

Unmanaged terminology in cross-team documentation causes miscommunication and ambiguity, which a shared domain glossary solves by establishing structured definitions and resolving synonyms to prevent terminology drift.