Cro Ux Writing
Write clear, actionable interface copy at a Grade 8 level that guides users, ensures consistency, and provides helpful, problem-solving error messages.
Like a lobster shell, security has layers — review code before you run it.
License
SKILL.md
UX Writing for Conversion
When to Use
Use this skill when writing or reviewing interface copy — labels, instructions, confirmations, error messages — to improve usability and conversion.
Core Rules
1. Write for Action, Not Description
Interface copy should prompt action, not describe features. "Analyze my landing page" on a button converts better than "Analysis Tool." "See where users drop off" beats "View Analytics." Every piece of copy should answer: what will the user do or get?
2. Use Plain Language at All Literacy Levels
Your product's interface will be used by people with varying technical literacy. Write at a Grade 8 reading level: short sentences, common words, no jargon. If a 14-year-old couldn't understand your interface copy, rewrite it.
3. Front-Load Important Information
Users scan interfaces rather than reading them linearly. Put the most important word or concept at the beginning of labels, headings, and instructions. "Free plan: 5 tests per month" is more scannable than "With the free plan, you can run up to 5 tests per month."
4. Be Consistent With Terminology
Using "workspace," "project," and "account" interchangeably to mean the same thing creates confusion. Establish a glossary of terms for your product and use them consistently across every surface: UI, emails, help docs, and marketing.
5. Write Error Messages That Solve Problems
Error messages are the most important UX copy in your product and the most neglected. A good error message explains what went wrong, why it happened, and exactly what the user should do next. Bad error messages blame users or provide no actionable path forward.
Quick Reference
| Copy Element | Formula |
|---|---|
| Button labels | Verb + object ("Save changes") |
| Empty states | What's missing + what to do |
| Error messages | What happened + how to fix |
| Success states | What was completed + what's next |
| Tooltips | Why this matters + how to use it |
Common Mistakes to Avoid
- Using technical or database language in user-facing copy
- Writing placeholder text that doubles as a field label — it disappears on focus
- Inconsistent capitalization and punctuation — creates a perception of low quality
Test Your Product with Racoonn
After applying these practices, validate with real AI-simulated user testing.
Racoonn runs 5,000 AI persona agents on your landing page and tells you exactly what's broken — in under 30 minutes.
→ API coming soon — Join the waitlist for early access: racoonn.me
Files
1 totalComments
Loading comments…
