skills.rest
pixelastic
pixelasticCOMMUNITY
Explore all skills by this author →
Website𝕏@pixelasticGitHub

glossary

Drills domain vocabulary and updates GLOSSARY.md with resolved terms.

38|6|Updated Sep 13, 2012
Search Tags:#documentation#glossary#consensus#knowledge-management#terminology#drill#domain-vocabulary
One-click install
npx skills add https://github.com/pixelastic/oroshi --skill glossary-pixelastic
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/pixelastic/oroshi/tree/main/tools/ai/claude/config/skills/glossary
Command: npx skills add https://github.com/pixelastic/oroshi --skill glossary-pixelastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drills domain vocabulary to resolve terminology ambiguities and updates the project GLOSSARY.md.

Core Features & Use Cases

  • Drills vocabulary one term at a time until consensus is reached and updates are written to the glossary.
  • Supports module-specific and repo-wide glossaries by resolving terms and documenting relationships.
  • Improves consistency and reduces misinterpretation across modules during development and documentation.

Quick Start

Run a term-drill session to identify and finalize terms for the target glossary.

Frequently Asked Questions about glossary

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

FAQPage Schema
How do I resolve domain terminology ambiguities in my project documentation?▼

You resolve domain terminology ambiguities by drilling vocabulary one term at a time until consensus is reached, then writing the finalized definitions to a project GLOSSARY.md file for consistent documentation.

What is the best way to maintain a module-specific glossary for domain vocabulary?▼

Maintaining a module-specific glossary involves drilling domain vocabulary to resolve term definitions and relationships for varying modules, then updating the target glossary to reduce misinterpretation across development.

How does a term drill session work for updating a project glossary?▼

A term drill session works by reading existing glossaries, prompting you to resolve specific terminology ambiguities one by one until consensus is reached, and writing the finalized terms using a defined format.

Can I document term relationships across varying modules in a repo-wide glossary?▼

Yes, you can document term relationships across varying modules in a repo-wide glossary by drilling domain vocabulary to resolve terminology and updating the central GLOSSARY.md file to improve consistency.

Why does my team misinterpret domain vocabulary during development?▼

Teams misinterpret domain vocabulary during development due to unresolved terminology ambiguities; drilling domain terms to reach consensus and documenting them in a glossary reduces this misinterpretation across modules.

Do I need an existing GLOSSARY.md file to start drilling domain terminology?▼

No, you do not need an existing GLOSSARY.md to start drilling, as the process reads existing glossaries if present, prompts for term resolution, and writes finalized terms to the file using the defined format.

Related Skills

Explore More Software Engineering Skills→
fray-cloudfray-cloud

ubiquitous-language

Extract domain terms from conversations and write UBIQUITOUS_LANGUAGE.md.

Community
Intermediate
zagarlucaszagarlucas

openapi-spec-writer

Generate OpenAPI 3.0/3.1 specifications for REST APIs with reusable components.

Community
Advanced
yongwoonyongwoon
8

ywc-ubiquitous-language

Extract domain terms from source code and create glossary documents.

Community
Intermediate
cropsggcropsgg
15

domain-context

Standardize domain terminology across projects using CONTEXT.md and ADRs.

Community
Intermediate