1---
  2name: clarify
  3description: Improve unclear UX copy, error messages, microcopy, labels, and instructions to make interfaces easier to understand. Use when the user mentions confusing text, unclear labels, bad error messages, hard-to-follow instructions, or wanting better UX writing.
  4version: 2.1.1
  5user-invocable: true
  6argument-hint: "[target]"
  7---
  8
  9Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.
 10
 11## MANDATORY PREPARATION
 12
 13Invoke /impeccable — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run /impeccable teach first. Additionally gather: audience technical level and users' mental state in context.
 14
 15---
 16
 17## Assess Current Copy
 18
 19Identify what makes the text unclear or ineffective:
 20
 211. **Find clarity problems**:
 22   - **Jargon**: Technical terms users won't understand
 23   - **Ambiguity**: Multiple interpretations possible
 24   - **Passive voice**: "Your file has been uploaded" vs "We uploaded your file"
 25   - **Length**: Too wordy or too terse
 26   - **Assumptions**: Assuming user knowledge they don't have
 27   - **Missing context**: Users don't know what to do or why
 28   - **Tone mismatch**: Too formal, too casual, or inappropriate for situation
 29
 302. **Understand the context**:
 31   - Who's the audience? (Technical? General? First-time users?)
 32   - What's the user's mental state? (Stressed during error? Confident during success?)
 33   - What's the action? (What do we want users to do?)
 34   - What's the constraint? (Character limits? Space limitations?)
 35
 36**CRITICAL**: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.
 37
 38## Plan Copy Improvements
 39
 40Create a strategy for clearer communication:
 41
 42- **Primary message**: What's the ONE thing users need to know?
 43- **Action needed**: What should users do next (if anything)?
 44- **Tone**: How should this feel? (Helpful? Apologetic? Encouraging?)
 45- **Constraints**: Length limits, brand voice, localization considerations
 46
 47**IMPORTANT**: Good UX writing is invisible. Users should understand immediately without noticing the words.
 48
 49## Improve Copy Systematically
 50
 51Refine text across these common areas:
 52
 53### Error Messages
 54**Bad**: "Error 403: Forbidden"
 55**Good**: "You don't have permission to view this page. Contact your admin for access."
 56
 57**Bad**: "Invalid input"
 58**Good**: "Email addresses need an @ symbol. Try: name@example.com"
 59
 60**Principles**:
 61- Explain what went wrong in plain language
 62- Suggest how to fix it
 63- Don't blame the user
 64- Include examples when helpful
 65- Link to help/support if applicable
 66
 67### Form Labels & Instructions
 68**Bad**: "DOB (MM/DD/YYYY)"
 69**Good**: "Date of birth" (with placeholder showing format)
 70
 71**Bad**: "Enter value here"
 72**Good**: "Your email address" or "Company name"
 73
 74**Principles**:
 75- Use clear, specific labels (not generic placeholders)
 76- Show format expectations with examples
 77- Explain why you're asking (when not obvious)
 78- Put instructions before the field, not after
 79- Keep required field indicators clear
 80
 81### Button & CTA Text
 82**Bad**: "Click here" | "Submit" | "OK"
 83**Good**: "Create account" | "Save changes" | "Got it, thanks"
 84
 85**Principles**:
 86- Describe the action specifically
 87- Use active voice (verb + noun)
 88- Match user's mental model
 89- Be specific ("Save" is better than "OK")
 90
 91### Help Text & Tooltips
 92**Bad**: "This is the username field"
 93**Good**: "Choose a username. You can change this later in Settings."
 94
 95**Principles**:
 96- Add value (don't just repeat the label)
 97- Answer the implicit question ("What is this?" or "Why do you need this?")
 98- Keep it brief but complete
 99- Link to detailed docs if needed
100
101### Empty States
102**Bad**: "No items"
103**Good**: "No projects yet. Create your first project to get started."
104
105**Principles**:
106- Explain why it's empty (if not obvious)
107- Show next action clearly
108- Make it welcoming, not dead-end
109
110### Success Messages
111**Bad**: "Success"
112**Good**: "Settings saved! Your changes will take effect immediately."
113
114**Principles**:
115- Confirm what happened
116- Explain what happens next (if relevant)
117- Be brief but complete
118- Match the user's emotional moment (celebrate big wins)
119
120### Loading States
121**Bad**: "Loading..." (for 30+ seconds)
122**Good**: "Analyzing your data... this usually takes 30-60 seconds"
123
124**Principles**:
125- Set expectations (how long?)
126- Explain what's happening (when it's not obvious)
127- Show progress when possible
128- Offer escape hatch if appropriate ("Cancel")
129
130### Confirmation Dialogs
131**Bad**: "Are you sure?"
132**Good**: "Delete 'Project Alpha'? This can't be undone."
133
134**Principles**:
135- State the specific action
136- Explain consequences (especially for destructive actions)
137- Use clear button labels ("Delete project" not "Yes")
138- Don't overuse confirmations (only for risky actions)
139
140### Navigation & Wayfinding
141**Bad**: Generic labels like "Items" | "Things" | "Stuff"
142**Good**: Specific labels like "Your projects" | "Team members" | "Settings"
143
144**Principles**:
145- Be specific and descriptive
146- Use language users understand (not internal jargon)
147- Make hierarchy clear
148- Consider information scent (breadcrumbs, current location)
149
150## Apply Clarity Principles
151
152Every piece of copy should follow these rules:
153
1541. **Be specific**: "Enter email" not "Enter value"
1552. **Be concise**: Cut unnecessary words (but don't sacrifice clarity)
1563. **Be active**: "Save changes" not "Changes will be saved"
1574. **Be human**: "Oops, something went wrong" not "System error encountered"
1585. **Be helpful**: Tell users what to do, not just what happened
1596. **Be consistent**: Use same terms throughout (don't vary for variety)
160
161**NEVER**:
162- Use jargon without explanation
163- Blame users ("You made an error" → "This field is required")
164- Be vague ("Something went wrong" without explanation)
165- Use passive voice unnecessarily
166- Write overly long explanations (be concise)
167- Use humor for errors (be empathetic instead)
168- Assume technical knowledge
169- Vary terminology (pick one term and stick with it)
170- Repeat information (headers restating intros, redundant explanations)
171- Use placeholders as the only labels (they disappear when users type)
172
173## Verify Improvements
174
175Test that copy improvements work:
176
177- **Comprehension**: Can users understand without context?
178- **Actionability**: Do users know what to do next?
179- **Brevity**: Is it as short as possible while remaining clear?
180- **Consistency**: Does it match terminology elsewhere?
181- **Tone**: Is it appropriate for the situation?
182
183Remember: You're a clarity expert with excellent communication skills. Write like you're explaining to a smart friend who's unfamiliar with the product. Be clear, be helpful, be human.