glossary

Capture and define domain terms for software project glossaries.

89|32|Updated May 28, 2026

Search Tags:#Claude Code #project documentation #domain glossary #term capture #consistent definitions

Ready to run

npx skills add https://github.com/genkovich/sdd --skill glossary-genkovich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/genkovich/sdd/tree/main/skills/glossary
Command: npx skills add https://github.com/genkovich/sdd --skill glossary-genkovich

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Ensures consistent and clear definitions for domain terms across your project, preventing misunderstandings and maintaining a shared understanding.

Core Features & Use Cases

Domain Term Capture: Capture and define domain terms as they emerge, preventing meaning drift.
Two-Level Contract: Support both project-wide and feature-specific terms.
Socratic Interaction: Guides users through the definition process, ensuring a complete understanding.
Integration with Other Skills: Supplies definitions to skills like 'specify', 'clarify', and 'design'.

Quick Start

Add a new term to the glossary by typing: "/sdd:glossary {term}"

Frequently Asked Questions about glossary

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

FAQPage Schema

How do I maintain consistent domain term definitions across a software project?▼

To maintain consistent domain term definitions, use a project glossary skill that captures terms as they emerge during development, resolving ambiguities through Socratic interaction to prevent meaning drift across the codebase.

What is the best way to capture and resolve ambiguous domain terminology in code?▼

Capturing and resolving ambiguous domain terminology is best handled through Socratic interaction, which guides users step-by-step to define terms completely, ensuring clear, canonical definitions are stored in the project glossary.

Can I manage both project-wide and feature-specific glossary terms?▼

Yes, you can manage both project-wide and feature-specific terms using a two-level contract structure, allowing you to scope domain definitions globally or isolate them to specific software features.

How do I integrate a domain glossary with other Claude Code skills?▼

You integrate a domain glossary by supplying its canonical definitions to other Claude Code skills like 'specify', 'clarify', and 'design', ensuring shared terminology is used consistently across project documentation and workflows.

When do I need a domain glossary for my project documentation?▼

You need a domain glossary when your project documentation starts losing a shared understanding of terms, requiring a system to capture emerging domain vocabulary and prevent misunderstandings across the codebase.