clarify

Rewrite unclear UX copy and labels across web and mobile interfaces.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/labohemez/kangnam-church-reservation --skill clarify-labohemez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/labohemez/kangnam-church-reservation/tree/main/.claude/skills/clarify
Command: npx skills add https://github.com/labohemez/kangnam-church-reservation --skill clarify-labohemez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unclear UX copy, confusing labels, and vague error messages slow user progress and increase support needs. This skill guides teams to identify and rewrite problematic UI text to improve clarity and usability.

Core Features & Use Cases

  • Identify clarity problems such as jargon, ambiguity, passive voice, excessive length, missing context, and tone mismatches.
  • Propose concrete copy improvements for error messages, form labels, placeholders, button text, help text, and empty/success/loading states.
  • Use case: rewrite a confusing error like "Invalid input" to "Please enter a valid value (e.g., [email protected])" and standardize terminology across screens.

Quick Start

Rewrite unclear UI text in the current screen to improve clarity and user comprehension.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I rewrite unclear UX copy and error messages for better clarity?

To rewrite unclear UX copy, identify issues like jargon, ambiguity, and passive voice, then replace vague text such as "Invalid input" with actionable examples like "Please enter a valid value (e.g., [email protected])". This structured approach improves user comprehension across web and mobile interfaces.

What makes confusing form labels and placeholders hard for users to understand?

Confusing form labels often contain jargon, ambiguity, missing context, or tone mismatches that slow user progress. Unclear placeholders and help text fail to guide users effectively, increasing support needs and causing input errors across application interfaces.

How do I improve UX writing for empty states and success messages?

Improving UX writing for empty states and success messages involves applying Copy Clarity Principles to plan, implement, and validate text changes. This ensures the copy provides clear context and guidance rather than leaving users confused about interface status.

Does this approach work for standardizing UI text terminology across multiple screens?

Yes, standardizing terminology across screens is a core use case. By identifying clarity problems and proposing concrete copy improvements for button text, help text, and error messages, you can standardize UI text consistently across both web and mobile interfaces.

When should I fix vague error messages to improve usability?

You should fix vague error messages whenever they slow user progress or increase support needs. Rewriting text like "Invalid input" to include specific examples and context directly improves usability and reduces user frustration during form completion.

What is the best way to identify clarity problems in mobile interface copy?

The best way to identify clarity problems in mobile interface copy is to evaluate text for excessive length, passive voice, jargon, and tone mismatches. This reveals problematic UI text in labels, buttons, and loading states that hinders user comprehension.