/ux-writing-skill

name: ux-writing
description: Create user-centered, accessible interface copy (microcopy) for digital products including buttons, labels, error messages, notifications, forms, onboarding, empty states, success messages, and help text. Use when writing or editing any text that appears in apps, websites, or software interfaces, designing conversational flows, establishing voice and tone guidelines, auditing product content for consistency and usability, reviewing UI strings, or improving existing interface copy. Applies UX writing best practices based on four quality standards — purposeful, concise, conversational, and clear. Includes accessibility guidelines, research-backed benchmarks (sentence length, comprehension rates, reading levels), expanded error patterns, tone adaptation frameworks, and comprehensive reference materials.

UX Writing

Write clear, concise, user-centered interface copy (UX text/microcopy) for digital products and experiences. This skill provides frameworks, patterns, and best practices for creating text that helps users accomplish their goals.

**Compatible with:** Claude, Codex, Cursor, and other agents that support the agent skills specification.

**Note:** This skill works with Codex CLI/IDE, not ChatGPT. ChatGPT cannot install or use skills.

When to Use This Skill

Use this skill when:

• Writing interface copy (buttons, labels, titles, messages, forms)
• Editing existing UX text for clarity and effectiveness
• Creating error messages, notifications, or success messages
• Designing conversational flows or onboarding experiences
• Establishing voice and tone for a product
• Auditing product content for consistency and usability

Core UX Writing Principles

The Four Quality Standards

Every piece of UX text should be:

1. **Purposeful** — Helps users or the business achieve goals 2. **Concise** — Uses the fewest words possible without losing meaning 3. **Conversational** — Sounds natural and human, not robotic 4. **Clear** — Unambiguous, accurate, and easy to understand

Key Best Practices

**Conciseness**

• Use 40-60 characters per line maximum
• Every word must have a job
• Break dense text into scannable chunks
• Front-load important information

**Clarity**

• Use plain language (7th grade reading level for general, 10th for professional)
• Avoid jargon, idioms, and technical terms
• Use consistent terminology throughout
• Choose meaningful, specific verbs

**Conversational Tone**

• Write how you speak
• Use active voice 85% of the time
• Include prepositions and articles
• Avoid robotic phrasing

**User-Centered**

• Focus on user benefits, not features
• Anticipate and answer user questions
• Use second-person ("you") language
• Match user's language and mental models

UX Text Patterns

Apply these common patterns for interface elements.

Titles

• **Purpose**: Orient users to where they are
• **Format**: Noun phrases, sentence case
• **Types**: Brand titles, content titles, category titles, task titles
• **Examples**: "Account settings", "Your library", "Create new post"

Buttons and Links

• **Purpose**: Enable users to take action
• **Format**: Active imperative verbs, sentence case
• **Pattern**: `[Verb] [object]`
• **Examples**: "Save changes", "Delete account", "View details"
• **Avoid**: Generic labels like "OK", "Submit", "Click here"

Error Messages

• **Purpose**: Explain problem and provide solution
• **Format**: Empathetic, clear, actionable
• **Pattern**: `[What failed]. [Why/context]. [What to do].`

**Error Message Types**

**Validation Errors (Inline)**

• Show as user completes field or on blur
• Brief, specific guidance to correct input
• Pattern: `[Field] [specific requirement]`
• Examples:
• "Email must include @"
• "Password must be at least 8 characters"
• "Choose a date in the future"
• Timing: Real-time or on field exit
• Location: Below or beside the field

**System Errors (Modal/Banner)**

• Show when backend operations fail
• Explain what happened and why
• Pattern: `[Action failed]. [Likely cause]. [Recovery step].`
• Examples:
• "Payment failed. Your card was declined. Try a different payment method."
• "Couldn't save changes. Connection lost. Reconnect and try again."
• "Upload failed. File is too large. Choose a file under 10MB."
• Timing: Immediately after failure
• Location: Modal dialog or prominent banner

**Blocking Errors (Full-screen)**

• Prevent continued use until resolved
• Clear explanation of blocker and resolution
• Pattern: `[What's blocked]. [Why]. [Specific action needed].`
• Examples:
• "Update required. This version is no longer supported. Update now to continue."
• "Subscription expired. Your account is paused. Renew subscription to restore access."
• "Verification needed. Confirm your email to access features. Check your inbox."
• Timing: On app launch or feature access
• Location: Full screen or large modal

**Permission Errors**

• Explain benefit before requesting permission
• Pattern: `[User benefit]. [Permission needed].`
• Examples:
• "Get notified when orders ship. Enable notifications."
• "Find nearby stores. Allow location access."
• "Back up your photos. Grant storage permission."
• Timing: When feature is first used
• Location: In context of the feature

**What to Avoid**

• Technical codes without explanation ("Error 403")
• Blame language ("invalid input", "illegal character")
• Robotic tone ("An error has occurred")
• Dead ends (error with no recovery path)
• Vague causes ("Something went wrong")

Success Messages

• **Purpose**: Confirm action completion
• **Format**: Past tense, specific, encouraging
• **Pattern**: `[Action] [result/benefit]`
• **Examples**: "Changes saved", "Email sent", "Profile updated"

Empty States

• **Purpose**: Guide users when content is absent
• **Types**: First-use, user-cleared, error/no results
• **Format**: Explanation + CTA to populate
• **Example**: "No messages yet. Start a conversation to connect