design-ux-copy

Write and review UX microcopy for buttons, errors, empty states, and dialogs.

Updated May 26, 2026
One-click install
npx skills add https://github.com/avel123111/triplanio --skill design-ux-copy-avel123111
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-ux-copy
Source: https://github.com/avel123111/triplanio/tree/main/.claude/skills/design-ux-copy
Command: npx skills add https://github.com/avel123111/triplanio --skill design-ux-copy-avel123111

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing clear, consistent interface copy is hard — error messages confuse users, CTAs are vague, and empty states leave people stuck. This Skill provides structured patterns and principles for producing UX copy that is clear, concise, and actionable. ## Core Features & Use Cases - Copy Patterns: Ready-made structures for CTAs, error messages, empty states, confirmation dialogs, tooltips, loading states, and onboarding text. - Copy Review: Evaluate existing microcopy against five principles — clear, concise, consistent, useful, and human. - Structured Output: Delivers recommended copy, tone-labeled alternatives, rationale, and localization notes. - Use Case: When a payment fails in your checkout flow, ask for an error message and receive copy structured as what happened, why, and how to fix it, plus alternative tones. ## Quick Start Ask the assistant to write an error message for a failed payment in the checkout flow, including the user's emotional state and any character limits.

Frequently Asked Questions about design-ux-copy

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

FAQPage Schema
How do I write a good error message for my app?

Structure error messages as what happened, why it happened, and how to fix it. For example: "Payment declined. Your card was declined by your bank. Try a different card or contact your bank." Keep the tone empathetic and actionable.

What should a call-to-action button say?

Start CTAs with a verb and be specific about the outcome, such as "Start free trial" or "Save changes" instead of generic labels like "Submit." The button label should match exactly what happens when clicked.

How do I write copy for an empty state screen?

Use the structure: what this is, why it is empty, and how to start. For example: "No projects yet. Create your first project to start collaborating with your team." This orients the user and gives a clear next action.

Can this review existing UX copy instead of writing new copy?

Yes, you can paste existing microcopy for review. It is evaluated against five principles — clear, concise, consistent, useful, and human — and you receive improved alternatives with tone labels and rationale.

What information do I need to provide to get good UX copy?

Provide the screen or flow context, what the user is trying to do and how they feel, the desired tone (formal, friendly, playful, reassuring), and constraints like character limits or platform guidelines.