clarify

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Confusing interface text—jargon-filled error messages, vague button labels, and unhelpful empty states—frustrates users, causes errors, and generates 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 clarity problems including jargon, ambiguity, passive voice, wrong length, and tone mismatches based on audience and user mental state. - Systematic Rewriting Patterns: Provides before/after guidance for error messages, form labels, buttons, help text, empty states, success messages, loading states, confirmation dialogs, and navigation labels. - Clarity Principles Enforcement: Applies rules for specificity, conciseness, active voice, and consistent terminology while prohibiting user-blaming and vague messaging. - Use Case: A settings page shows "Error 403: Forbidden" when access fails. The Skill rewrites 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 on your checkout 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. For example, replace "Invalid input" with "Email addresses need an @ symbol. Try: name@example.com" and link to help resources when applicable.

How to improve confusing button and CTA text?▼

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 to users?▼

Common problems include jargon users don't understand, ambiguous phrasing with multiple interpretations, 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.

When should I use confirmation dialogs in UX writing?▼

Reserve confirmations for risky or destructive actions only. 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" rather than "Yes".

What are the limitations of automated UX copy review?▼

Copy improvements still require human verification for comprehension, actionability, brevity, consistency, and tone appropriateness. The guidance cannot replace usability testing with real users in your specific product context.