Cro Ux Writing

# UX Writing for Conversion

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "Cro Ux Writing" with this command: npx skills add wellyxy/cro-ux-writing

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 ElementFormula
Button labelsVerb + object ("Save changes")
Empty statesWhat's missing + what to do
Error messagesWhat happened + how to fix
Success statesWhat was completed + what's next
TooltipsWhy 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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Img2img

Generate images from text descriptions using DALL-E 3 while adhering to usage policies and avoiding realistic human faces.

Registry SourceRecently Updated
General

Habitat-GS-Navigator

Navigate and interact with photo-realistic 3DGS environments via the Habitat-GS Bridge. Use when: user asks to explore a 3D scene, perform embodied navigatio...

Registry SourceRecently Updated
General

Memory Palace

持久化记忆管理。Use when: 用户告诉你个人信息/偏好/习惯、需要记住项目状态/技术决策、完成任务后有可复用经验、用户说"记住""别忘了""下次注意"、需要回忆之前的对话内容。支持语义搜索和时间推理。

Registry SourceRecently Updated
General

Podcast Transcript Mining Authority Positioning

Extract guest appearances, speaking topics, and soundbites from podcast transcripts to build authority portfolios and generate podcast pitch templates. Use w...

Registry SourceRecently Updated