ux-microcopy-audit

Audits interface copy against UX-writing standards and produces severity-rated issues with rewrites.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-microcopy-audit-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-microcopy-audit
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/ux/audits/microcopy
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill ux-microcopy-audit-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface copy reviews are often impressionistic and incomplete, missing hidden states like errors, empty states, and tooltips, and never checking terminology consistency across a flow. This Skill turns copy review into a structured audit with named criteria, severity ratings, and concrete rewrites. ## Core Features & Use Cases - Full content inventory: Sweeps all copy in a screen or flow, including hidden content such as error messages, empty states, confirmations, and notifications. - Criteria-based evaluation: Checks clarity, concision, action-orientation, consistency, tone fit, error/empty states, inclusivity, and honesty, with severity ratings (Critical, Major, Minor). - Rewrite-driven output: Every finding includes a concrete rewrite, plus consistency notes and the top three highest-impact fixes. - Use Case: After generating a new onboarding flow, run this audit to catch vague CTAs like "Submit", jargon-filled error messages, and inconsistent terms like "booking" vs. "scheduling" before shipping. ## Quick Start Audit the microcopy on this checkout flow and give me a severity-rated issue list with rewrites for each problem.

Frequently Asked Questions about ux-microcopy-audit

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

FAQPage Schema
How do I audit UX microcopy in my product?▼

Start with a full content inventory of every piece of text, including hidden states like errors, empty states, and tooltips. Then evaluate each item against criteria such as clarity, concision, action-orientation, and tone, and provide a rewrite for every flagged issue.

What makes a good UX writing audit checklist?▼

A good checklist covers clarity and plain language, concision, action-oriented button labels, terminology consistency, tone fit for the moment, error and empty state quality, inclusivity, and honesty. Each finding should be severity-rated and paired with a concrete rewrite.

How do I write better error messages and empty states?▼

Error messages should state the problem and the fix without blaming the user or using all caps. Empty states should teach the first action rather than showing a blank screen, and success states should acknowledge completion.

Does this audit cover accessibility and dark patterns?▼

It flags plain-language and clarity issues but defers technical accessibility mechanics like alt text and screen-reader behavior to an accessibility audit. Manipulative copy such as confirmshaming is flagged and routed to a dark-patterns audit for intent classification.

When should I run a microcopy audit in the design process?▼

Run it when reviewing existing UI copy for clarity and consistency, or as a validation step after generating any new screen or flow. It is especially valuable for catching hidden copy in error and empty states that single-screen reviews miss.