skills.rest
jnlanahan
jnlanahanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

glossary

Extract domain terms into a shared glossary at .claude/glossary.md.

Updated Apr 30, 2026
Search Tags:#documentation#domain modeling#glossary#ambiguity resolution#product discovery#terminology
One-click install
npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill glossary-jnlanahan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: glossary
Source: https://github.com/jnlanahan/Product-Agents-and-Skills/tree/main/skills/2-Define-Glossary
Command: npx skills add https://github.com/jnlanahan/Product-Agents-and-Skills --skill glossary-jnlanahan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents domain confusion by extracting the key terms from a product discussion and formalizing them into a consistent glossary.

Core Features & Use Cases

  • Glossary Extraction: Extracts domain-relevant nouns and concepts from the current conversation into structured definitions.
  • Ambiguity Resolution: Flags cases where the same word means different things and recommends canonical naming plus “aliases to avoid.”
  • Persistent Knowledge Output: Writes/extends a glossary at .claude/glossary.md and records decisions in .claude/progress.md for continuity across runs.

Quick Start

Run the glossary Skill when the conversation already contains enough domain detail to name the problem space, so it can save the normalized terms to .claude/glossary.md.

Frequently Asked Questions about glossary

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

FAQPage Schema
How do I create a shared domain glossary from messy project terminology?▼

Use the glossary Skill to consolidate inconsistent project terminology by extracting key terms from a product discussion, flagging naming ambiguity, and writing normalized definitions to a shared glossary file for product teams.

What is the best way to resolve terminology ambiguity during product discovery?▼

Resolving terminology ambiguity involves flagging cases where the same word means different things, recommending canonical naming, and listing aliases to avoid so domain experts and developers share aligned language.

How do I document domain modeling terms for development discussions?▼

Document domain modeling terms by extracting domain-relevant nouns and concepts from the current conversation into structured definitions, then saving the normalized terms to a persistent glossary file for continuity across runs.

Can I use a glossary extraction tool without prior domain expert input?▼

No, you should run glossary extraction when the conversation already contains enough domain detail to name the problem space, ensuring the extracted terms accurately reflect the product design and build discussions.

Where are extracted glossary definitions and progress decisions stored?▼

Extracted glossary definitions and progress decisions are stored persistently by writing the normalized terms to a glossary markdown file and appending post-flight output records to a separate progress markdown file.

Related Skills

Explore More Product & Management Skills→
kevinnftkevinnft
13

ubiquitous-language

Extract domain terminology from conversations into a structured glossary file.

Community
Intermediate
tonombtonomb

ubiquitous-language

Extract domain terminology and definitions into a Markdown glossary.

Community
Intermediate
cropsggcropsgg
15

tool-use-verification

Verify tool invocations with pre-flight and post-flight checks.

Community
Advanced
haryelramalhoharyelramalho

ubiquitous-language

Extracts domain terminology from a conversation and normalizes it into a glossary file.

Community
Basic