skills.rest
maltemd
maltemdCOMMUNITY
Explore all skills by this author →
GitHub

defining-feature-vocabulary

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

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

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 non-existent terminology within a feature, ensuring clear communication and a unified user experience.

Core Features & Use Cases

  • Canonical Terminology: Establishes precise, agreed-upon terms for all core concepts within a feature.
  • Conflict Resolution: Identifies and resolves naming conflicts between different teams or existing standards.
  • Use Case: When launching a new feature, use this Skill to define terms like "workspace," "member," and "role" so that product, design, and engineering all use the same language, preventing confusion in UI copy, documentation, and code.

Quick Start

Use the defining-feature-vocabulary skill to create the 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 establish consistent terminology for a new software feature?▼

Canonical terminology for a feature is established by defining core terms, setting usage rules, and listing prohibited alternatives. This process aligns product, design, and engineering teams on a unified language, preventing confusion in UI copy and code.

What is the best way to resolve naming conflicts between existing product features?▼

Naming conflicts are resolved by harmonizing terminology and establishing strict naming conventions for concepts. This identifies inconsistencies between teams or existing standards and replaces them with agreed-upon canonical terms.

How do I create a content design vocabulary for terms like workspace and member?▼

Creating a content design vocabulary requires adhering to defined templates and rubrics that validate output. This establishes precise, agreed-upon terms for core concepts, ensuring clear communication and a unified user experience.

When do I need to define canonical terminology for my product?▼

Canonical terminology is needed when launching a new feature or addressing inconsistent, ambiguous, and non-existent terms. Defining terms early prevents confusion across UI copy, documentation, and code throughout the product lifecycle.

Can I use this approach to standardize terminology across different teams?▼

Yes, standardizing terminology across teams is a primary use case. It resolves naming conflicts between different teams or existing standards, ensuring that product, design, and engineering all use the same language.

What are the limitations of manually defining feature terminology without templates?▼

Without defined templates and rubrics for output validation, manually defining terminology risks introducing ambiguity. The approach requires strict adherence to these structures to successfully establish canonical terms and resolve inconsistencies.

Related Skills

Explore More Content & Communication Skills→
CodeAlive-AICodeAlive-AI

ubiquitous-language

Manage a unified domain thesaurus for consistent naming across codebases.

Official
Advanced
jeremydhoover-blipjeremydhoover-blip
7

defining-feature-vocabulary

Create canonical vocabularies defining product feature terms and usage rules.

Community
Intermediate
viktorbezdekviktorbezdek
10

consistency-standards

Audit codebases and documentation for naming, terminology, and reuse inconsistencies.

Community
Intermediate
k97k97
4

animation-vocabulary

Translate subjective motion descriptions into standardized animation and UI terminology.

Community
Basic