skills.rest
jeremydhoover-blip
jeremydhoover-blipCOMMUNITY
Explore all skills by this author →
GitHub

defining-feature-vocabulary

Create canonical vocabularies defining product feature terms and usage rules.

7|7|Updated Feb 20, 2026
Search Tags:#vocabulary#feature definition#content design#naming#terminology#linguistics
One-click install
npx skills add https://github.com/jeremydhoover-blip/hoover-content-system --skill defining-feature-vocabulary
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: defining-feature-vocabulary
Source: https://github.com/jeremydhoover-blip/hoover-content-system/tree/main/skills/content-context/defining-feature-vocabulary
Command: npx skills add https://github.com/jeremydhoover-blip/hoover-content-system --skill defining-feature-vocabulary

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the problem of inconsistent, ambiguous, or user-unfriendly terminology within a feature by establishing a clear, canonical vocabulary.

Core Features & Use Cases

  • Canonical Terminology: Defines precise terms for core concepts within a feature.
  • Usage Guidance: Specifies where and how terms should be used.
  • Conflict Resolution: Identifies and resolves naming conflicts with existing terms or conventions.
  • Use Case: When launching a new collaboration feature, use this Skill to define terms like "workspace," "member," and "role," ensuring all teams (product, design, engineering, content) use the same language.

Quick Start

Use the defining-feature-vocabulary skill to create a canonical vocabulary for the new user profile feature.

Frequently Asked Questions about defining-feature-vocabulary

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

FAQPage Schema
How do I create canonical terminology for a new product feature?▼

Defining feature vocabulary involves creating canonical terms for product concepts, setting usage guidance, and resolving naming conflicts. This ensures all teams use consistent, user-friendly terminology during content creation and product launches.

What is the best way to resolve terminology inconsistencies across product teams?▼

The best way to resolve terminology inconsistencies is to build a canonical vocabulary that explicitly defines terms, usage rules, and prohibited alternatives. This aligns product, design, engineering, and content teams on consistent naming conventions.

How do I establish naming conventions for concepts within a feature?▼

You establish naming conventions by defining canonical terms, specifying where and how they apply, and identifying prohibited alternatives. Validating the finalized vocabulary against a defined rubric ensures terminology consistency across the feature.

When do I need to define a canonical vocabulary for my software project?▼

You need a canonical vocabulary when launching new product features or preparing content to prevent ambiguous terminology. It ensures all teams use identical language for concepts like workspaces, members, and roles during product launches.

Are there validation rules for defining terminology and usage guidance?▼

Yes, defining terminology requires validating the finalized vocabulary against a defined rubric. This ensures the usage rules and naming conventions effectively resolve terminology inconsistencies before supporting content creation or product launches.

Related Skills

Explore More Content & Communication Skills→
maltemdmaltemd

defining-feature-vocabulary

Create canonical terminology defining terms, usage rules, and prohibited alternatives for a feature.

Community
Intermediate
Takashi-MatsumuraTakashi-Matsumura

用語・表記ガイドライン

Standardize Japanese terminology and Katakana usage across code, documentation, and UI.

Community
Basic
RogueRopeRogueRope
2

tov-editor

Edit copy to align with the Tone & Writing Style Guide brand voice.

Official
Basic
yash-gargyash-garg

ubiquitous-language

Extract and standardize domain terminology into a DDD-style glossary.

Community
Intermediate