i-clarify

Rewrite unclear UX copy and error messages for web and mobile interfaces.

Updated May 17, 2026
One-click install
npx skills add https://github.com/cenjie/skills --skill i-clarify-cenjie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-clarify
Source: https://github.com/cenjie/skills/tree/main/skills/i-clarify
Command: npx skills add https://github.com/cenjie/skills --skill i-clarify-cenjie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear, confusing, or unhelpful interface text so users understand what happened and what to do next, reducing errors, frustration, and support requests. The Skill targets microcopy that breaks task flows: error messages, form labels, CTAs, help text, empty and loading states, and confirmations.

Core Features & Use Cases

  • Clarity analysis: Identify jargon, ambiguity, passive voice, missing context, and tone mismatches in existing copy.
  • Targeted rewrites: Produce concise, action-oriented alternatives for error messages, form labels, buttons, and help text that include suggested fixes or next steps.
  • Validation & testing guidance: Recommend phrasing tests, readability checks, and contextual constraints (character limits, localization notes) to verify improvements.
  • Use case: Turn a terse error like "Invalid input" into "Invalid email address. Use this format: [email protected]" and provide tone and audience adjustments.

Quick Start

Revise the error message "Error 403: Forbidden" into a clear, user-friendly message that explains why access is blocked and what the user can do next.

Frequently Asked Questions about i-clarify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve unclear UX microcopy and error messages?

Improve unclear UX microcopy by identifying jargon, ambiguity, and passive voice, then rewriting error messages into concise, action-oriented text with suggested fixes to reduce user frustration.

What is the best way to rewrite confusing form labels and CTAs?

The best way to rewrite confusing form labels and CTAs is to apply an assess-plan-improve-verify workflow, adjusting tone and context to produce clear, actionable alternatives for web and mobile UI elements.

How do I fix an error message when users report task failure?

Fix an error message after task failure by replacing terse codes like "Error 403" with clear explanations of what happened and specific next steps the user can take to resolve the access block.

Can I use UX writing principles to improve empty and loading states?

Yes, you can use UX writing principles to improve empty and loading states by evaluating the audience's technical level and mental state to ensure the copy provides necessary context and guidance.

How do I validate rewritten UI text for readability and localization?

Validate rewritten UI text by applying recommended phrasing tests, checking readability, and reviewing contextual constraints like character limits and localization notes to verify the microcopy improvements.