ux-copy

Write and review UX microcopy for interface elements with structured recommendations.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ngochuy13/intern-dev --skill ux-copy-ngochuy13
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ux-copy
Source: https://github.com/ngochuy13/intern-dev/tree/main/skills/ux-copy
Command: npx skills add https://github.com/ngochuy13/intern-dev --skill ux-copy-ngochuy13

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

UX teams need fast, consistent wording for interfaces, but manually drafting microcopy (errors, CTAs, empty states, tooltips, onboarding) is time-consuming and often inconsistent across screens.

Core Features & Use Cases

  • Microcopy drafting and review: Generate or critique copy for specific UI elements and flows (e.g., CTAs, confirmation dialogs, error messages, empty states, tooltips, loading states, onboarding text).
  • Tone and constraint alignment: Adapt wording to the user’s emotional state and the intended tone (empathetic for errors, reassuring for warnings, etc.) while respecting platform and character-limit considerations.
  • Structure that improves clarity: Produce action-oriented CTAs, actionable error messages (what happened/why/how to fix), and structured empty/confirmation dialog copy.

Quick Start

Tell the ux-copy skill the screen or flow context, the user state, the desired tone, and any constraints, then ask it to write or review the exact copy you need.

Frequently Asked Questions about ux-copy

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

FAQPage Schema
How do I write clear UX microcopy for interface elements like CTAs and error messages?

To write clear UX microcopy, transform your UI context into concise, human-centered text. Generate action-oriented CTAs and actionable error messages that explain what happened, why, and how to fix it while maintaining a consistent tone across web and app flows.

What is the best way to write empathetic error messages and empty states for an app flow?

The best way to write error messages and empty states is to align the wording with the user's emotional state. Produce empathetic, reassuring copy for warnings and structured empty states that guide users, ensuring the tone matches the specific screen context and constraints.

Can I generate onboarding text and confirmation dialogs that fit specific character limits?

Yes, you can generate onboarding text and confirmation dialogs tailored to specific character limits. Provide the screen context, desired tone, and platform constraints to produce structured microcopy recommendations that respect your exact length requirements.

How do I review and improve existing CTA wording for better conversion and clarity?

Review existing CTA wording by evaluating it against practical UX writing principles like clarity, concision, and action-orientation. Generate improved alternative copy options complete with structured rationale to ensure your CTAs convert effectively and maintain a human tone.

Does this UX writing approach work for both web and mobile app screen flows?

Yes, this UX writing approach works for both web and mobile app screen flows. It adapts microcopy for tooltips, loading states, and confirmation dialogs across platforms while respecting specific platform constraints and character-limit considerations.

Why should I use structured UX copy alternatives instead of writing microcopy manually?

You should use structured UX copy alternatives because manually drafting microcopy for empty states and onboarding is time-consuming and often inconsistent. Structured recommendations provide clear alternatives with rationale, ensuring fast, consistent wording across all screens.