i-clarify

Rewrite unclear UX copy into concise, actionable user-facing language.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams rewrite confusing interface text so users can quickly understand what a screen means and what they should do next.

Core Features & Use Cases

  • Error message clarity: Turn vague failures into plain-language guidance with a fix.
  • Microcopy and labels: Improve button text, field labels, hints, and navigation copy for consistency.
  • Context-aware rewrites: Adapt tone and detail for first-time users, stressed users, or technical users.
  • Use case: A checkout flow with confusing validation and button labels can be rewritten into concise, actionable copy that reduces mistakes and support requests.

Quick Start

Use the i-clarify skill to rewrite the target text for clarity while keeping the original intent and audience in mind.

Frequently Asked Questions about i-clarify

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

FAQPage Schema
How do I rewrite confusing UX error messages into clear user guidance?

To rewrite confusing UX error messages, transform vague failure text into plain-language guidance that explains the problem and provides an actionable fix. This ensures users immediately understand what went wrong and how to proceed.

What is the best way to improve microcopy and form labels for better clarity?

Improving microcopy and form labels requires applying concise wording and consistent terminology tailored to your audience. Rewriting button text, field labels, and hints ensures consistent navigation copy across the interface.

How do I write clear empty states and loading text for first-time users?

Writing clear empty states and loading text for first-time users involves applying context-aware tone adjustments to your interface copy. This adapts the detail and wording to match the user's specific situation and technical familiarity.

Can I use plain-language rewriting to fix confusing checkout validation messages?

Yes, you can use plain-language rewriting to fix confusing checkout validation messages. Rewriting these instructions into concise, actionable copy reduces user mistakes and minimizes support requests during critical flows.

When should I adjust the tone of confirmation dialogs and success messages?

You should adjust the tone of confirmation dialogs and success messages when addressing different user contexts, such as stressed or technical users. Context-aware rewrites ensure the copy remains actionable and appropriate for the situation.