ux-writing

Write and review UI copy including buttons, errors, empty states, and microcopy using voice and tone rules.

Updated Jul 20, 2026
One-click install
npx skills add https://github.com/idy-00/paytrack --skill ux-writing-idy-00
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-writing
Source: https://github.com/idy-00/paytrack/tree/main/backend/.agents/skills/ux-writing
Command: npx skills add https://github.com/idy-00/paytrack --skill ux-writing-idy-00

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interface copy is often inconsistent, confusing, or written ad hoc by developers. This Skill produces or reviews UI text — buttons, error messages, empty states, notifications, labels — against a defined voice and tone system so every string is clear, concise, and consistent. ## Core Features & Use Cases - Copy formulas: Buttons frontload the verb and name the outcome; confirmation dialogs restate the action and object; errors follow the what→why→how structure with no dead ends. - Tone matching: Adjusts language to the user's emotional state (onboarding, success, routine, error, destructive), using plainer language under higher stress. - Pre-ship checklist: Enforces a 10-item review covering sentence case, numerals, labels over placeholders, inclusive language, and translatability. - Use Case: When designing a destructive action like account deletion, use this Skill to write the dialog title, a confirm button that restates the action ("Delete account"), and a type-to-confirm step for high-stakes operations. ## Quick Start Ask the assistant to write or review the error message and confirmation dialog copy for a specific UI flow in your product.

Frequently Asked Questions about ux-writing

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

FAQPage Schema
How do I write good error messages for a UI?▼

Structure error messages as what happened, why it happened, and how to fix it. Avoid dead ends, error codes, stack traces, and blaming the user, and always give a clear next action.

How to write confirmation dialog copy for destructive actions?▼

Make the confirm button restate the action and object, such as "Delete account" instead of "OK" or "Yes". The title asks the question and the button answers in matching words; irreversible actions require a type-to-confirm step.

What should an empty state say in a product UI?▼

An empty state should communicate value first, then offer a first action. Avoid bare text like "No data" and instead explain what the user gains and what to do next.

Does this copy review cover accessibility and localization?▼

Yes. The checklist enforces labels instead of placeholders, no color-only or direction-only instructions, and translatability rules such as avoiding string concatenation, referencing i18n and RTL guidance.

When should UI copy use plainer language?▼

Use plainer language as user stress increases, such as during errors or destructive flows. Onboarding and success moments can carry more personality, while high-stakes moments prioritize clarity.