From utopia-studio-cobuild-product
Improves unclear UX copy, error messages, microcopy, labels, and instructions for easier interface understanding. Useful when users mention confusing text or bad UX writing.
How this skill is triggered — by the user, by Claude, or both
Slash command
/utopia-studio-cobuild-product:clarifyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.
Identify and improve unclear, confusing, or poorly written interface text to make the product easier to understand and use.
Invoke /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.
Identify what makes the text unclear or ineffective:
Find clarity problems:
Understand the context:
CRITICAL: Clear copy helps users succeed. Unclear copy creates frustration, errors, and support tickets.
Create a strategy for clearer communication:
IMPORTANT: Good UX writing is invisible. Users should understand immediately without noticing the words.
Refine text across these common areas:
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: [email protected]"
Principles:
Bad: "DOB (MM/DD/YYYY)" Good: "Date of birth" (with placeholder showing format)
Bad: "Enter value here" Good: "Your email address" or "Company name"
Principles:
Bad: "Click here" | "Submit" | "OK" Good: "Create account" | "Save changes" | "Got it, thanks"
Principles:
Bad: "This is the username field" Good: "Choose a username. You can change this later in Settings."
Principles:
Bad: "No items" Good: "No projects yet. Create your first project to get started."
Principles:
Bad: "Success" Good: "Settings saved! Your changes will take effect immediately."
Principles:
Bad: "Loading..." (for 30+ seconds) Good: "Analyzing your data... this usually takes 30-60 seconds"
Principles:
Bad: "Are you sure?" Good: "Delete 'Project Alpha'? This can't be undone."
Principles:
Bad: Generic labels like "Items" | "Things" | "Stuff" Good: Specific labels like "Your projects" | "Team members" | "Settings"
Principles:
Every piece of copy should follow these rules:
NEVER:
Test that copy improvements work:
Remember: 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.
npx claudepluginhub the-utopia-studio/skills --plugin utopia-studio-cobuild-productWrites button labels, error messages, placeholder text, empty states, and tooltips that are specific, actionable, and honest. Helps reduce user friction and support contacts.
Writes and reviews UX copy for microcopy, error messages, empty states, CTAs, confirmations, tooltips, loading states, and onboarding. Use /ux-copy with context or auto-triggers on copy queries.
Writes clear UI copy for microcopy, error messages, empty states, CTAs, onboarding, and confirmations with voice, tone, and best practices.