clarify

Rewrites unclear UX copy, error messages, labels, and microcopy for clearer interfaces.

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

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, excessive length, missing context, and tone mismatch based on audience and user mental state. - Systematic Rewriting: Improves error messages, form labels, button text, help text, empty states, success messages, loading states, confirmation dialogs, and navigation labels with concrete before/after patterns. - Clarity Principles: Enforces rules like being specific, concise, active, human, helpful, and consistent while avoiding blame, vague errors, and jargon. - Use Case: Your app shows "Error 403: Forbidden" to users. 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 error messages and button labels in your settings page using the clarify skill.

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 "Error 403: Forbidden" with "You don't have permission to view this page. Contact your admin for access."

How to improve confusing form labels and instructions?

Use clear, specific labels instead of generic placeholders, show format expectations with examples, and explain why you are asking when it is not obvious. Put instructions before the field and keep required indicators clear.

What makes good button and CTA text?

Describe the action specifically using active voice, like "Create account" or "Save changes" instead of "Submit" or "OK". Match the user's mental model so the label states exactly what happens next.

Should confirmation dialogs be used for every action?

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

When should humor be avoided in UX writing?

Avoid humor in error messages where users may be stressed or frustrated; be empathetic instead. Humor can fit celebratory success moments, but clarity and helpfulness always take priority over personality.