Product Terminology

Manage a centralized domain glossary with conflict-aware term updates.

6|3|Updated Apr 12, 2026

Search Tags:#documentation #consistency #glossary #terminology #domain-driven

Ready to run

npx skills add https://github.com/carson-sweet/sweetclaude --skill product-terminology

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Product Terminology
Source: https://github.com/carson-sweet/sweetclaude/tree/main/skills/product-terminology
Command: npx skills add https://github.com/carson-sweet/sweetclaude --skill product-terminology

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml.

What problem does it solve?

This Skill eliminates ambiguity and communication silos by providing a structured way to define, track, and enforce a shared domain vocabulary across your project.

Core Features & Use Cases

Centralized Glossary: Maintains a single source of truth for domain terms, including definitions, rationales, and aliases.
Conflict Resolution: Proactively identifies naming conflicts and synonyms during the addition process to prevent terminology drift.
Use Case: When onboarding new team members or starting a new feature, use this to ensure everyone uses the same language, preventing the confusion caused by using different names for the same concept.

Quick Start

Use the product-terminology skill to add a new term to the project glossary.

Frequently Asked Questions about Product Terminology

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

FAQPage Schema

How do I maintain consistent terminology across project documentation?▼

You can maintain consistent terminology by using a centralized domain glossary that tracks definitions, rationales, and forbidden synonyms to prevent terminology drift across your project. It serves as a single source of truth for all team members.

What is the best way to prevent naming conflicts when adding new domain terms?▼

The best way to prevent naming conflicts is through conflict-aware updates that proactively identify existing synonyms and naming collisions during the addition process. This stops terminology drift before it enters your codebase or documentation.

How do I set up a shared domain glossary for my team?▼

You set up a shared domain glossary by accessing your project session state to locate and maintain a dedicated markdown file. This file acts as the central repository for your domain vocabulary, definitions, and aliases.

Does this terminology tool require any specific dependencies to run?▼

Yes, the terminology management tool requires the pyyaml dependency to operate. It also requires access to the project session state to locate and update the glossary markdown file.

Why does my team need a domain-driven glossary for onboarding?▼

You need a domain-driven glossary for onboarding to eliminate ambiguity and communication silos. It ensures new team members use identical language for the same concepts, preventing confusion caused by using different names across features.

Can I track forbidden synonyms and aliases in a project glossary?▼

Yes, you can track forbidden synonyms and aliases in the project glossary. The system manages defined terms, their rationales, and explicitly forbidden synonyms to enforce a strict, shared domain vocabulary across your codebase.