AI SummaryClarify 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
# Install all 18 skills from impeccable mkdir -p .cursor/skills/adapt && curl --retry 3 --retry-delay 2 --retry-all-errors -fsSL -o .cursor/skills/adapt/SKILL.md "https://raw.githubusercontent.com/pbakaus/impeccable/main/.claude/skills/adapt/SKILL.md" && \
Run in your IDE terminal (bash). On Windows, use Git Bash, WSL, or your IDE's built-in terminal. If curl fails with an SSL error, your network may block raw.githubusercontent.com — try using a VPN or download the files directly from the source repo.
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
Quality Score
Good
85/100
Trust & Transparency
Open Source — Apache-2.0
Source code publicly auditable
Verified Open Source
Hosted on GitHub — publicly auditable
Actively Maintained
Last commit Today
8.4k stars — Strong Community
328 forks
My Fox Den
Community Rating
Sign in to rate this booster