skills.rest
masakinihirota
masakinihirotaCOMMUNITY
Explore all skills by this author →
𝕏@masakinihirotaGitHub

clarify

Rewrites unclear UX copy, error messages, labels, and instructions for interface comprehension.

Updated Jul 21, 2026
Search Tags:#clarity#microcopy#copywriting#ux writing#content design#error messages#interface text
One-click install
npx skills add https://github.com/masakinihirota/2026src-ni --skill clarify-masakinihirota
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/masakinihirota/2026src-ni/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/masakinihirota/2026src-ni --skill clarify-masakinihirota

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text, vague error messages, and jargon-heavy labels frustrate users and generate support tickets. This Skill systematically identifies and rewrites unclear UX copy so users understand what happened and what to do next. ## Core Features & Use Cases - Copy Assessment: Diagnoses jargon, ambiguity, passive voice, wrong tone, and missing context in existing interface text. - Systematic Rewriting: Improves error messages, form labels, button text, empty states, loading states, success messages, confirmation dialogs, and navigation labels using before/after patterns. - Clarity Principles: Enforces rules like being specific, active, human, and consistent while avoiding blame, jargon, and vague wording. - Use Case: When a user reports that an error message like "Error 403: Forbidden" confuses customers, the Skill rewrites it as "You don't have permission to view this page. Contact your admin for access." ## Quick Start Ask the assistant to review and improve the confusing error messages and button labels in your app's settings page.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve unclear error messages in my app?▼

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. For example, replace "Invalid input" with "Email addresses need an @ symbol. Try: name@example.com" and link to help resources when applicable.

What makes good UX writing for buttons and CTAs?▼

Good button text describes the specific action using active voice, like "Create account" or "Save changes" instead of generic labels like "Submit" or "OK". Match the user's mental model and be specific about what happens next.

How should empty states and loading states be written?▼

Empty states should explain why nothing is shown and present a clear next action, like "No projects yet. Create your first project to get started." Loading states should set time expectations and explain what is happening.

When should confirmation dialogs be used in UX copy?▼

Use confirmations only for risky or destructive actions, stating the specific action and its consequences, such as "Delete 'Project Alpha'? This can't be undone." Avoid overusing them for routine actions.

What are common UX writing mistakes to avoid?▼

Avoid unexplained jargon, blaming users, vague messages like "Something went wrong", unnecessary passive voice, inconsistent terminology, and placeholders used as the only field labels since they disappear when users type.

Related Skills

Explore More Design & Creative Skills→
shuretokkishuretokki

clarify

Rewrite unclear interface text into concise, actionable microcopy.

Community
Intermediate
Chris-MaskeyChris-Maskey

progressive-disclosure

Sequence interface information with staged reveal triggers and success metrics.

Community
Intermediate
dhruvil7797dhruvil7797

clarify

Rewrite unclear UX copy, error messages, labels, and instructions across interfaces.

Community
Intermediate
rodrigo-altissimorodrigo-altissimo

copywriting-squad-claude-hopkins

Audits marketing copy using Claude Hopkins' scientific advertising principles and generates A/B test plans with metrics.

Community
Advanced