crit-content-voice

Evaluate UI microcopy and propose voice options with a terminology glossary.

3|Updated Feb 23, 2026
One-click install
npx skills add https://github.com/metedata/design-crit --skill crit-content-voice
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crit-content-voice
Source: https://github.com/metedata/design-crit/tree/main/skills/crit-content-voice
Command: npx skills add https://github.com/metedata/design-crit --skill crit-content-voice

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Evaluates and guides the consistency of UI voice, tone, and terminology across screens by proposing concrete microcopy directions and a glossary.

Core Features & Use Cases

  • Generates 2-3 voice options across the four voice dimensions (Formal-Casual, Serious-Playful, Technical-Simple, Authoritative-Friendly).
  • Produces complete microcopy specimens for buttons, placeholders, tooltips, errors, and empty states in-context.
  • Builds a terminology glossary (canonical terms, rejected alternatives, and context notes) to enforce consistency across the product.
  • Supports a round-based critique with a compare view to help teams converge on a locked voice.

Quick Start

Provide your project brief and current design context to generate 2-3 voice options and a glossary.

Frequently Asked Questions about crit-content-voice

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

FAQPage Schema
How do I audit UI microcopy for consistent voice across different screens?

To audit UI microcopy for consistent voice, you can generate 2-3 voice options using a four-dimension framework, produce complete in-context microcopy specimens for buttons and errors, and build a terminology glossary to enforce consistency across surfaces.

What is a four-dimension voice framework for evaluating product tone?

A four-dimension voice framework evaluates product tone across Formal-Casual, Serious-Playful, Technical-Simple, and Authoritative-Friendly spectrums to propose concrete microcopy directions and guide brand consistency.

How do I create a UI terminology glossary to enforce consistent microcopy?

You create a UI terminology glossary by defining canonical terms, listing rejected alternatives, and adding context notes, ensuring teams enforce consistent terminology and voice across the product.

What is the best way to write microcopy for empty states and error messages?

The best way to write microcopy for empty states and error messages is to generate complete in-context specimens aligned with a locked voice decision, ensuring the tone matches your project brief and design references.

Can I compare multiple voice options to help my team converge on a final UI tone?

Yes, you can compare multiple voice options using a round-based critique with a compare view, which helps teams evaluate different tone directions and converge on a locked voice for the product.

What do I need to provide to generate voice options for my UI microcopy?

To generate voice options for your UI microcopy, you need to provide your project brief and current design context, which are analyzed to propose suitable tone directions and a terminology glossary.