i-clarify

Analyze UX copy for jargon, ambiguity, and tone mismatch.

1|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/hi-yuki-922/accounting-assistant --skill i-clarify-hi-yuki-922
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i-clarify
Source: https://github.com/hi-yuki-922/accounting-assistant/tree/main/.claude/skills/i-clarify
Command: npx skills add https://github.com/hi-yuki-922/accounting-assistant --skill i-clarify-hi-yuki-922

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses confusing, unclear, or poorly written interface text, making software interfaces easier for users to understand and navigate.

Core Features & Use Cases

  • Clarity Assessment: Identifies jargon, ambiguity, passive voice, and other clarity issues in UX copy.
  • Contextual Improvement: Tailors copy suggestions based on audience, user state, and action.
  • Systematic Refinement: Provides specific examples and principles for improving error messages, labels, buttons, and more.
  • Use Case: A product manager notices users struggling with a new feature's instructions. They use this Skill to rewrite the confusing on-screen text, leading to a smoother user experience and fewer support requests.

Quick Start

Use the i-clarify skill to improve the clarity of the error message "An unexpected error occurred."

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 copy and error messages in my user interface?

To improve unclear UX copy, analyze text for jargon, ambiguity, passive voice, and tone mismatch, then rewrite using active voice, specificity, and conciseness to make user interfaces easier to understand and navigate.

What is the best way to rewrite confusing microcopy for non-technical users?

The best way to rewrite confusing microcopy is to assess the target audience and user state, then tailor the text with a human tone, helpfulness, and consistency while removing assumptions and missing context.

Why do users struggle with interface labels and instructions, and how can I fix them?

Users struggle with interface labels and instructions when they contain jargon, ambiguity, or passive voice. Fix them by applying principles of specificity, conciseness, and active voice to ensure clarity and guide desired actions.

Can I use this to refine error messages for specific user states and desired actions?

Yes, you can refine error messages by evaluating the specific audience, context, and desired action, then systematically generating improvements that replace vague language with helpful, clear, and active instructions.

Does this approach work for both long instructions and short button labels?

Yes, this approach works for both by systematically analyzing text length, jargon, and consistency across all interface elements, ensuring both short button labels and long instructions are clear, actionable, and appropriately toned.

What are common clarity issues to look for when auditing UX writing?

Common clarity issues in UX writing include jargon, ambiguity, passive voice, excessive length, unstated assumptions, missing context, and tone mismatch, all of which hinder user comprehension and task completion.