clarify

Rewrite UI copy to be clear, concise, and user-focused.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/BilsoNyuMNAM/hypertrophy-project --skill clarify-bilsonyumnam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/BilsoNyuMNAM/hypertrophy-project/tree/main/.gemini/skills/clarify
Command: npx skills add https://github.com/BilsoNyuMNAM/hypertrophy-project --skill clarify-bilsonyumnam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Improve unclear UX copy, error messages, microcopy, labels, and instructions. Makes interfaces easier to understand and use.

Core Features & Use Cases

  • Identify clarity problems across copy: jargon, ambiguity, passive voice, length, missing context, and tone mismatches.
  • Plan and apply copy improvements: define the primary message, the required user action, tone, and constraints.
  • Improve copy across common areas: error messages, form labels, help text, empty states, and success messages.

Quick Start

Rewrite the given UI copy to be clear, concise, and user-focused.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I improve unclear UX copy and ambiguous error messages in my interface?

To improve unclear UX copy, you identify ambiguous wording, jargon, and passive voice, then rewrite error messages and labels for comprehension. This reduces user confusion by ensuring interface text is clear, concise, and action-focused.

What is the best way to rewrite form labels and tooltips for better usability?

The best way to rewrite form labels and tooltips for usability is to define the primary message and required user action first. You then adjust the tone and length to meet accessibility and localization guidelines while preserving critical actions.

Why does unclear microcopy increase support tickets and how can I fix it?

Unclear microcopy increases support tickets because missing context and tone mismatches confuse users. You fix it by identifying clarity problems across empty states and success messages, then rewriting the text to explicitly state the required user action.

Can I use UX writing guidelines to fix jargon and passive voice in empty states?

Yes, you can use UX writing guidelines to fix jargon and passive voice in empty states. The process involves identifying these specific clarity problems and rewriting the instructions to be user-focused, concise, and consistent with your interface tone.

Does rewriting UI copy for accessibility also support localization guidelines?

Rewriting UI copy for accessibility does support localization guidelines. By removing jargon and ambiguity from prompts and error messages, you simplify the text structure, making it significantly easier to translate while preserving the original intent.