clarify

Rewrite unclear UX copy into plain, actionable interface text.

1|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/ft-frank/UNIHACK --skill clarify-ft-frank
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/ft-frank/UNIHACK/tree/main/frontend/.agents/skills/clarify
Command: npx skills add https://github.com/ft-frank/UNIHACK --skill clarify-ft-frank

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses confusing, unclear, or poorly written interface text, making digital products more intuitive and user-friendly.

Core Features & Use Cases

  • Error Message Improvement: Rewrites technical or vague error messages into plain language with actionable advice.
  • Label & Instruction Refinement: Clarifies form labels, instructions, and button text for better user guidance.
  • Use Case: A user encounters an error message like "Invalid input." This Skill can transform it into "Email addresses need an @ symbol. Try: [email protected]," guiding the user to correct the input.

Quick Start

Use the clarify skill to improve the error message "Operation failed."

Frequently Asked Questions about clarify

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

FAQPage Schema
What is UX writing and how does it improve user interface text?

UX writing improves user interface text by analyzing jargon, ambiguity, and passive voice to enhance understandability. It systematically rewrites labels, instructions, and microcopy to ensure digital products remain intuitive and user-friendly.

How do I write better error messages for my application?

To write better error messages, rewrite technical or vague alerts into plain language with actionable advice. Transform messages like "Invalid input" into "Email addresses need an @ symbol" to guide users toward correcting their input.

How can I fix unclear microcopy and form labels in my UI?

Fix unclear microcopy and form labels by focusing on specificity, conciseness, and active voice. Refining button text and instructions with a human tone provides better user guidance and reduces input errors.

What is the best way to write copy for empty states and loading states?

The best way to write copy for empty states and loading states is to focus on helpfulness and consistency. Clear microcopy guides users through the interface, explaining the current context and what they can do next.

When should I review UX copy for clarity and consistency?

Review UX copy for clarity and consistency whenever users encounter confusing interface text, vague confirmation dialogs, or technical jargon. Systematic improvements ensure labels, success messages, and navigation remain understandable.

Why does passive voice make microcopy confusing for users?

Passive voice makes microcopy confusing because it obscures the subject performing the action, creating ambiguity. Replacing it with active voice ensures your user interface text is specific, concise, and direct.