Be specific, not vague (\"Save changes\" not \"Submit\") Be concise (every word must earn its place) Use the user's language, not technical jargon Lead with the act
Microcopy and UX Writing focuses on crafting clear, concise, and user-centered text for all user interface elements. It ensures button labels, error messages, empty states, and confirmations communicate specific actions or statuses without ambiguity. This skill emphasizes using the user’s language, avoiding jargon, and leading with the action or benefit to improve clarity and reduce friction in digital experiences.
By applying consistent terminology and well-structured messaging, this skill helps reduce user errors, increase task completion rates, and enhance overall user satisfaction. For example, replacing vague buttons like “Submit” with precise labels like “Save changes” can measurably improve conversion rates by reducing hesitation or confusion during critical interactions.
This skill is essential for conversion rate optimization (CRO) specialists aiming to refine user flows and boost engagement through better interface text. Growth leads managing onboarding funnels will find value in clear empty states and success messages that drive user retention. Additionally, agency strategists and UX designers working on client projects can leverage this skill to audit and improve UI copy, minimizing drop-offs and support tickets caused by unclear messaging.
Practitioners start by auditing existing interface text, identifying generic or ambiguous labels such as “OK” or “Submit.” Next, they rewrite buttons and calls-to-action using verb + noun structures like “Create project” or “Delete account” to specify actions clearly. Then, they craft error messages following the formula: what happened, why, and what to do next, avoiding blame and technical jargon. Finally, they design empty states and success messages that guide users on how to proceed or celebrate milestones, ensuring every word serves a purpose.
How specific should button labels be? Button labels should be as specific as possible, naming the exact action and object to avoid ambiguity. What tone should error messages use? Error messages must be neutral and helpful, never blaming the user or alarming them. Should empty states include calls to action? Yes, effective empty states explain why the area is empty and provide a clear next step or button to guide the user forward.
Attach the Microcopy and UX Writing skill to any Metaflow agent task involving UI text creation or review to ensure clarity and consistency in user-facing copy. Expect the agent to generate or audit button labels, error messages, empty states, and confirmation dialogs that follow proven principles of specificity and user language. This skill helps streamline content decisions and reduce iterative revisions during development and testing phases. You can expand on this by exploring related skills focused on...
For broader context, see our roundup of claude skills for marketing, and read common Claude Code content mistakes for related setup guidance.