clarify

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

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/ivaylo91/Shopping-Mobile-App --skill clarify-ivaylo91
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/ivaylo91/Shopping-Mobile-App/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/ivaylo91/Shopping-Mobile-App --skill clarify-ivaylo91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text frustrates users, causes errors, and generates support tickets. This Skill identifies jargon, ambiguity, passive voice, and tone mismatches in your product copy and rewrites it so users understand immediately. ## Core Features & Use Cases - Copy Assessment: Diagnoses clarity problems including jargon, ambiguity, missing context, and tone mismatch based on audience and user mental state. - Systematic Rewriting: Improves error messages, form labels, button text, tooltips, empty states, success messages, loading states, confirmation dialogs, and navigation labels with before/after examples. - Clarity Verification: Checks rewritten copy for comprehension, actionability, brevity, consistency, and appropriate tone. - Use Case: Your app shows "Error 403: Forbidden" and users keep contacting support. Use this Skill to rewrite it as "You don't have permission to view this page. Contact your admin for access." ## Quick Start Ask the AI to review and improve the confusing error messages and button labels in your 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: [email protected]" and link to help resources when applicable.

How to write better button and CTA text for interfaces?

Describe the specific action using active voice with a verb plus noun, such as "Create account" or "Save changes" instead of generic labels like "Submit" or "OK". Match the wording to the user's mental model of the task.

What makes UX copy unclear or confusing?

Common problems include jargon users don't understand, ambiguous phrasing, passive voice, excessive length, assumed knowledge, and missing context about what to do next. Tone mismatches with the user's emotional state also reduce clarity.

Should confirmation dialogs be used for every user action?

No, confirmations should be reserved for risky or destructive actions. State the specific action and consequences, such as "Delete 'Project Alpha'? This can't be undone," and use clear button labels like "Delete project" instead of "Yes".

When should placeholder text not be used as form labels?

Placeholders should never be the only label because they disappear when users type, leaving them without context. Use clear, specific labels above the field and reserve placeholders for showing format examples.