Skip to content
Skill

clarify

by pbakaus

AI Summary

Clarify helps developers improve confusing UX copy, error messages, and interface labels by identifying and fixing clarity problems like jargon, ambiguity, and wordiness. It's essential for anyone building user-facing products who wants to enhance usability through better microcopy.

Install

Copy this and paste it into Claude Code, Cursor, or any AI assistant:

I want to install the "clarify" skill in my project.

Please run this command in my terminal:
# Install skill into your project
mkdir -p .claude/skills/clarify && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/clarify/SKILL.md "https://raw.githubusercontent.com/pbakaus/impeccable/main/.claude/skills/clarify/SKILL.md"

Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.

Description

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

Assess Current Copy

Identify what makes the text unclear or ineffective: • Find clarity problems: • Jargon: Technical terms users won't understand • Ambiguity: Multiple interpretations possible • Passive voice: "Your file has been uploaded" vs "We uploaded your file" • Length: Too wordy or too terse • Assumptions: Assuming user knowledge they don't have • Missing context: Users don't know what to do or why • Tone mismatch: Too formal, too casual, or inappropriate for situation • Understand the context: • Who's the audience? (Technical? General? First-time users?) • What's the user's mental state? (Stressed during error? Confident during success?) • What's the action? (What do we want users to do?) • What's the constraint? (Character limits? Space limitations?) CRITICAL: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.

Plan Copy Improvements

Create a strategy for clearer communication: • Primary message: What's the ONE thing users need to know? • Action needed: What should users do next (if anything)? • Tone: How should this feel? (Helpful? Apologetic? Encouraging?) • Constraints: Length limits, brand voice, localization considerations IMPORTANT: Good UX writing is invisible. Users should understand immediately without noticing the words.

Improve Copy Systematically

Refine text across these common areas:

Error Messages

Bad: "Error 403: Forbidden" Good: "You don't have permission to view this page. Contact your admin for access." Bad: "Invalid input" Good: "Email addresses need an @ symbol. Try: name@example.com" Principles: • Explain what went wrong in plain language • Suggest how to fix it • Don't blame the user • Include examples when helpful • Link to help/support if applicable

Discussion

0/2000
Loading comments...

Health Signals

MaintenanceCommitted 1mo ago
Active
Adoption1K+ stars on GitHub
13.5k ★ · Popular
DocsREADME + description
Well-documented

GitHub Signals

Stars13.5k
Forks328
Issues5
Updated1mo ago
View on GitHub
Apache-2.0 License

My Fox Den

Community Rating

Sign in to rate this booster

Works With

Claude Code