Micro Wordsmith
Generate button labels, error messages, tooltips, and empty states
Nobody budgets for UX writing but it makes or breaks usability. This recipe generates complete microcopy sets for your UI components — error messages that actually help, empty states that guide action, button labels that are clear, and tooltips that explain without patronizing.
PROMPT
Create a skill called "Micro Wordsmith". When I describe a UI component, screen, or flow (or share a screenshot), generate a complete microcopy set. Include: button labels (clear, action-oriented, consistent verb tense), form validation error messages (specific, with remediation steps — never "Invalid input"), empty state messages (with a call to action), loading state text, success confirmations (what happened + what's next), tooltip text, 404/error page copy, and onboarding hints. Let me choose a tone: friendly, professional, playful, or minimal. Follow UX writing best practices: be concise, use active voice, front-load the important info, and be specific about what went wrong and how to fix it. If I provide the product context (audience, industry), tailor the voice accordingly.
How It Works
Tell your Claw what component you're building (or share a screenshot), and
it generates a complete microcopy set covering every state and edge case.
Choose a tone — friendly, professional, playful, or minimal — and get copy
that sounds like a human wrote it.
What You Get
- Button labels: clear, action-oriented, consistent verb tense
- Form validation messages: specific errors with remediation steps (not just "Invalid input")
- Empty states: helpful messages with a clear call to action
- Loading states: contextual messages (not just a spinner)
- Success confirmations: what happened and what to do next
- Tooltip text: explain without patronizing
- 404 and error pages: helpful and on-brand
- Onboarding hints: guide first-time users without overwhelming
- Tone variants: friendly, professional, playful, minimal
Setup Steps
- Describe the component or share a screenshot
- Optionally specify the product context and audience
- Choose a tone (default: friendly)
- Your Claw generates the complete microcopy set
Tips
- The form validation messages are worth the price of admission alone — "Please enter a valid email" vs. "Email should look like name@example.com"
- Empty states are the most neglected UX surface — they're a chance to guide action, not just say "Nothing here"
- Run this for every new component and you'll never ship a "TODO: add error message" again
- The consistency in verb tense and terminology makes the UI feel more polished