glossary

Name: glossary
Availability: InStock
Author: 686f6c61

Create and maintain a project-specific glossary from code and documentation.

105|8|Updated Feb 18, 2026

Search Tags:#project management #documentation #communication #vocabulary #glossary #terminology

Ready to run

npx skills add https://github.com/686f6c61/alfred-dev --skill glossary-686f6c61

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/686f6c61/alfred-dev/tree/main/skills/documentacion/glossary
Command: npx skills add https://github.com/686f6c61/alfred-dev --skill glossary-686f6c61

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses ambiguity and miscommunication within a project team by establishing a clear, consistent, and agreed-upon vocabulary for all key terms.

Core Features & Use Cases

Term Identification: Scans code, documentation, and user input to find potentially ambiguous terms.
Glossary Creation: Generates a structured Markdown file (docs/glossary.md) with columns for Term, Definition, Context, and "Do Not Confuse With".
Code Coherence Check: Verifies that code elements (variables, classes) align with glossary definitions.
Use Case: When a new feature is being developed, use this Skill to ensure all team members understand terms like "Active User," "Session," and "Guest" in the same way, preventing bugs caused by differing interpretations.

Quick Start

Use the glossary skill to identify and define key terms for the current project.

Frequently Asked Questions about glossary

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

FAQPage Schema

How do I create a project glossary to prevent team miscommunication?▼

To prevent team miscommunication, you can create a project glossary by scanning code and documentation to identify ambiguous terms, defining them concisely, and generating a structured Markdown file.

How does a project glossary ensure consistent terminology across code and documentation?▼

A project glossary ensures consistent terminology by defining key terms and verifying that code elements like variables and classes align with those definitions, linking them back to the codebase for coherence.

What is the best way to define project terms clearly for a new feature?▼

The best way to define project terms clearly is to identify key terms from user input and code, then document them with their context and similar terms to avoid confusion, preventing bugs from differing interpretations.

Can I check if code variables align with defined glossary terms?▼

Yes, you can perform a code coherence check to verify that code elements such as variables and classes align with the definitions established in your project glossary, preventing ambiguity.

What format is used to maintain project terminology definitions?▼

Project terminology definitions are maintained in a structured Markdown file that includes columns for Term, Definition, Context, and Do Not Confuse With to ensure consistent understanding.

When do I need a glossary for project management documentation?▼

You need a glossary for project management documentation when ambiguity arises around terms like Active User or Guest, ensuring all team members share a consistent understanding and reducing errors.