skills.rest
LinCie
LinCieCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

clarify

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

Updated Mar 20, 2026
Search Tags:#clarity#microcopy#copywriting#usability#ux writing#error messages#interface text
One-click install
npx skills add https://github.com/LinCie/bearuang --skill clarify-lincie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/LinCie/bearuang/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/LinCie/bearuang --skill clarify-lincie

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 product copy and rewrites it so users immediately understand what happened and what to do next. ## Core Features & Use Cases - Copy Assessment: Diagnoses clarity problems including jargon, ambiguity, excessive length, wrong assumptions, and tone mismatches 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 patterns. - Use Case: A settings page shows "Error 403: Forbidden" to users. The Skill rewrites it as "You don't have permission to view this page. Contact your admin for access," explaining the problem and the fix in plain language. ## Quick Start Ask the AI to review and improve the unclear 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 write better error messages for my app?▼

Explain what went wrong in plain language, suggest how to fix it, and avoid blaming the user. Replace codes like "Error 403" with actionable text such as "You don't have permission to view this page. Contact your admin for access."

How to improve button and CTA text in a user interface?▼

Describe the specific action using active voice, like "Save changes" or "Create account" instead of generic labels like "OK" or "Submit." 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 action?▼

No, reserve confirmations for risky or destructive actions. State the specific action and its 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 no context. Use clear, specific labels above the field and reserve placeholders for showing format examples like name@example.com.

Related Skills

Explore More Design & Creative Skills→
shuretokkishuretokki

clarify

Rewrite unclear interface text into concise, actionable microcopy.

Community
Intermediate
phazurlabsphazurlabs
35

UX Metrics & Measurement

Define and operationalize UX measurement frameworks like HEART, SUS, and UEQ.

Community
Advanced
riffluvriffluv

polish

Fix alignment, spacing, typography, and copy issues in UI designs.

Community
Advanced
Prorise-coolProrise-cool
24

usability-testing

Design usability tests with tasks, scripts, and metrics.

Community
Intermediate