skills.rest
RonanCodes
RonanCodesCOMMUNITY
Explore all skills by this author →
Website𝕏@ronancodesGitHub

ubiquitous-language

Extract domain terms from code and docs into a GLOSSARY.md file.

Updated Aug 23, 2026
Search Tags:#codebase#ddd#glossary#terminology#ubiquitous-language#domain-terms
One-click install
npx skills add https://github.com/RonanCodes/ronan-skills --skill ubiquitous-language-ronancodes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ubiquitous-language
Source: https://github.com/RonanCodes/ronan-skills/tree/main/skills/ubiquitous-language
Command: npx skills add https://github.com/RonanCodes/ronan-skills --skill ubiquitous-language-ronancodes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Extract and maintain a DDD-style ubiquitous language glossary for a project to ensure consistent terminology across code, docs, and conversations.

Core Features & Use Cases

  • Build and maintain a centralized glossary of domain terms extracted from code, README, CLAUDE.md, and comments.
  • Deduplicate terms, propose definitions, and track aliases to avoid confusion across modules.
  • Use for onboarding, cross-team alignment, and ensuring consistent language in conversations and documentation.

Quick Start

Interactively add a term to the glossary and regenerate GLOSSARY.md.

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 consistent ubiquitous language across a multi-language monorepo?▼

To maintain a ubiquitous language across a multi-language monorepo, you can extract domain terms from code constructs, README files, and CLAUDE.md, then deduplicate and codify them into a generated GLOSSARY.md at the project root.

How do I extract domain terms from code and docs to build a DDD glossary?▼

You can build a DDD glossary by extracting domain terms directly from code constructs, README files, and CLAUDE.md entries, then deduplicating the terms and proposing definitions to generate a centralized GLOSSARY.md.

What is the best way to align domain terminology for cross-team onboarding?▼

Aligning domain terminology for cross-team onboarding involves maintaining a centralized glossary that tracks aliases and definitions, ensuring consistent language across code, documentation, and team conversations.

Can I use this ubiquitous language approach for projects with existing glossary entries?▼

Yes, this approach supports projects with existing glossary entries by extracting and deduplicating those terms alongside code constructs and documentation, then regenerating a unified GLOSSARY.md at the project root.

Why does my codebase have inconsistent domain terms across different modules?▼

Inconsistent domain terms across modules occur without a centralized glossary to track aliases and definitions; extracting and codifying terms from code and docs into a GLOSSARY.md resolves this confusion.

Does generating a glossary require manually adding every domain term?▼

No, generating a glossary does not require manually adding every term because the process extracts domain terms directly from code constructs, README files, and CLAUDE.md, then deduplicates them automatically.

Related Skills

Explore More Software Engineering Skills→
malinskibeniaminmalinskibeniamin
3

ubiquitous-language

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

Community
Advanced
JohannesKoningsJohannesKonings
9

domain-modeling

Standardize domain terminology and document architectural decisions in software projects.

Community
Intermediate
dacydacy

ddd-skill

Formalize domain boundaries into bounded contexts, aggregates, and event schemas.

Community
Advanced
EnigmaWUEnigmaWU
1

define-bounded-contexts

Define bounded contexts and map integration contracts for domain-driven design.

Community
Advanced