clarify

Rewrites unclear UX copy, error messages, labels, and microcopy for interface clarity.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/WeWake1/BSOMS --skill clarify-wewake1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/WeWake1/BSOMS/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/WeWake1/BSOMS --skill clarify-wewake1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text causes user errors, frustration, and support tickets. This Skill identifies jargon, ambiguity, passive voice, and tone mismatches in your product copy and rewrites it so users immediately understand what happened and what to do next. ## Core Features & Use Cases - Copy Auditing: Systematically finds clarity problems across error messages, form labels, buttons, tooltips, empty states, loading states, confirmations, and navigation labels. - Before/After Rewrites: Applies concrete principles (be specific, active, human, helpful, consistent) with examples like turning "Error 403: Forbidden" into "You don't have permission to view this page." - Context-Aware Tone: Considers audience technical level and user mental state (stressed during errors vs. confident during success) before rewriting. - Use Case: Point it at your checkout flow and get rewritten error messages, button labels, and empty states that tell users exactly what went wrong and how to fix it. ## Quick Start Ask the assistant to review and improve the unclear copy in your checkout form's error messages and button labels.

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 when applicable.

What makes good UX microcopy for buttons and CTAs?▼

Good button copy 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 to write better empty state messages?▼

Explain why the state is empty when not obvious, show the next action clearly, and make it welcoming rather than a dead end. Replace "No items" with "No projects yet. Create your first project to get started."

Should confirmation dialogs be used for every action?▼

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

What are common UX writing mistakes to avoid?▼

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