glossary-creation

Extract and consolidate project terms into a standardized glossary at docs/glossary.md.

Updated Nov 27, 2025

Search Tags:#templates #documentation #consistency #glossary #engineering #terms

Ready to run

npx skills add https://github.com/GenerativeAgents/training-claude-code-example --skill glossary-creation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: glossary-creation
Source: https://github.com/GenerativeAgents/training-claude-code-example/tree/main/.claude/skills/glossary-creation
Command: npx skills add https://github.com/GenerativeAgents/training-claude-code-example --skill glossary-creation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps establish and maintain a project glossary to ensure consistent definitions across documentation and code.

Core Features & Use Cases

Templates & Guidance: Provides templates and examples to standardize term definitions.
Glossary Integration: Merges extracted terms from docs into a central glossary.
Use Case: When onboarding or expanding the codebase, create a shared vocabulary that reduces ambiguity.

Quick Start

Use the glossary-creation skill to generate docs/glossary.md from your existing docs structure, using the provided terminology templates.

Frequently Asked Questions about glossary-creation

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

FAQPage Schema

How do I create a project glossary to standardize terminology across documentation?▼

Create a project glossary by extracting terms from existing docs—product requirements, functional design, architecture, repository structure, and development guidelines—then consolidate them into a unified docs/glossary.md file. Use template-driven definitions including term explanations, related terms, usage examples, and data-model references to ensure consistency.

What should a glossary definition include to maintain documentation consistency?▼

Each glossary term should follow a template with: definition, explanation, related terms, usage examples, and data-model references. This structured approach ensures consistent terminology across all project documents and reduces ambiguity during onboarding.

Can I merge existing glossary terms with newly extracted terms from my docs?▼

Yes. The glossary-creation workflow prioritizes existing definitions in docs/glossary.md, then integrates newly extracted terms from your documentation sources. This preserves established terminology while filling gaps across product requirements, functional design, architecture, and development guidelines.

When should I create or update a project glossary?▼

Create or update a glossary during onboarding, codebase expansion, or when documentation becomes scattered across multiple files. A centralized glossary reduces miscommunication and ensures new team members understand shared vocabulary quickly.

What documents should I source terms from when building a glossary?▼

Source terms from your core documentation: docs/product-requirements.md, docs/functional-design.md, docs/architecture.md, docs/repository-structure.md, and docs/development-guidelines.md. This captures terminology across product, design, technical, and operational domains.