glossary

Track and enforce canonical domain terminology across code and documentation.

2|Updated Mar 27, 2019

Search Tags:#code review #ddd #glossary #ubiquitous language #naming #terminology

Ready to run

npx skills add https://github.com/silcam/lessons-from-luke --skill glossary-silcam

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/silcam/lessons-from-luke/tree/main/.claude/skills/glossary
Command: npx skills add https://github.com/silcam/lessons-from-luke --skill glossary-silcam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents domain terminology drift by keeping one canonical name for each concept across code, specifications, and discussions.

Core Features & Use Cases

Capture glossary entries with concise definitions and related links.
Detect naming inconsistencies and synonym conflicts during development and review.
Use it when naming classes, types, functions, or clarifying domain language in specs.
Example: confirm whether "UserProfile" and "UserAccount" describe the same concept before introducing both.

Quick Start

Ask the glossary skill to check a term, define it clearly, and align the surrounding code or documentation to the canonical wording.

Frequently Asked Questions about glossary

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

FAQPage Schema

How do I prevent domain terminology drift across code and documentation?▼

To prevent domain terminology drift, use a glossary to track and enforce canonical domain terminology. This ensures one consistent name for each concept across classes, specifications, and discussions, stopping naming inconsistencies before they enter your codebase.

What is ubiquitous language and how do I enforce it during code review?▼

Ubiquitous language is a shared, canonical vocabulary used across code and documentation. You enforce it during code review by validating terms against a glossary, detecting synonym conflicts, and aligning class, type, and function names to the defined wording.

How do I check if two domain names like UserProfile and UserAccount describe the same concept?▼

You can check if terms describe the same concept by querying a glossary to detect synonym conflicts. It validates the proposed names against canonical domain terminology, confirming whether they are duplicates before introducing both into your codebase.

Can I use a glossary to manage DDD naming conventions for types and functions?▼

Yes, you can use a glossary to manage DDD naming conventions. It captures entries with concise definitions and applies term validation to classes, types, and functions, ensuring ubiquitous language stays consistent across development and specification workflows.

What is the best way to detect naming inconsistencies in domain-driven design?▼

The best way to detect naming inconsistencies in domain-driven design is to use glossary-based term validation. This mechanism identifies synonym conflicts and drift during development, ensuring your code aligns with the canonical ubiquitous language.

When do I need glossary-based term validation for my codebase?▼

You need glossary-based term validation when naming classes, types, or functions, and when clarifying domain language in specifications. It is required whenever ubiquitous language must stay consistent across code and documentation to prevent terminology drift.