ux-nomenclature

Enforce glossary-approved UX terms in React components and data files.

Updated Aug 25, 2025
One-click install
npx skills add https://github.com/joaopelegrino/app-controle --skill ux-nomenclature
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-nomenclature
Source: https://github.com/joaopelegrino/app-controle/tree/main/.claude/skills/ux-nomenclature
Command: npx skills add https://github.com/joaopelegrino/app-controle --skill ux-nomenclature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates inconsistent terminology across the user interface, which often leads to user confusion and increased cognitive load. By enforcing a strict glossary, it ensures a unified and intuitive user experience throughout the educational platform.

Core Features & Use Cases

  • Automated Terminology Enforcement: Automatically detect and suggest corrections for prohibited terms (e.g., "Sistema de Aprendizado" to "Curso") in React components and data files.
  • Hierarchical Naming Conventions: Guide the application of a standardized naming hierarchy for learning content (e.g., "Curso > Seção > Aula").
  • Standardized UI Text: Ensure consistent phrasing for buttons, placeholders, and help texts (e.g., "← Voltar ao Hub", "Meu Caderno de Notas").
  • Use Case: When editing BashLearningSystem.jsx, if you type "Ver Notas", the skill will automatically flag it and suggest "📖 Estudar" based on the ÉPICO 12 glossary.

Quick Start

Use the ux-nomenclature skill to replace all instances of "Sistema de Aprendizado" with "Curso" in the src/components/ directory.

Frequently Asked Questions about ux-nomenclature

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

FAQPage Schema
How do I enforce consistent terminology across React components and data files?

Enforce consistent UX nomenclature by applying glossary-approved term substitutions during component development and data updates. The skill automatically detects prohibited terms and suggests replacements aligned to your official glossary, ensuring unified phrasing across buttons, placeholders, and UI text throughout the platform.

What's the best way to standardize UI text like button labels and placeholder copy?

Standardize UI text by defining approved phrasing for buttons, placeholders, and help texts in a central glossary, then apply those standards consistently across components. This eliminates variation and reduces user confusion from inconsistent terminology.

How do I replace deprecated terms with approved equivalents during pull request reviews?

Use automated checks during code review to flag deprecated terms and suggest glossary-approved replacements. Review pull requests against the official glossary, replacing old terms with standardized equivalents and verifying compliance before merge.

Can I apply hierarchical naming conventions to organize learning content structure?

Yes. Apply hierarchical naming conventions to structure learning content—for example, Course > Section > Lesson—ensuring consistent terminology at each level. This standardized hierarchy guides users through content with predictable, intuitive naming throughout the platform.

What happens if I don't enforce consistent UX terminology across the interface?

Inconsistent terminology increases cognitive load and user confusion. Without enforced glossary compliance, users encounter conflicting labels and phrasing, degrading the user experience and making navigation less intuitive across the platform.

Does this work with existing React component workflows and refactoring processes?

Yes. The skill integrates into React component development, editing, and UI refactoring workflows. Apply it when updating components or data files to ensure all terminology changes comply with the glossary and maintain consistency during refactoring.