
Error & Notification Copy Optimizer
Create empathetic error messages and notifications that guide users to resolution
What You Can Do
This skill helps you craft error messages and notifications that prioritize clarity and actionability over cleverness. You'll generate empathetic microcopy for error states, in-app notifications, empty states, and edge cases—then test variations against different user personas to minimize cognitive load and maximize task completion rates. It bridges UX research insights with production-ready copy that reduces support tickets and builds user trust.
Features
Creates copy for forms, transactions, system failures, and edge cases with user-centric language that explains what happened and how to fix it
Prioritizes error severity and determines which messages require immediate user action versus informational notifications
Tests message variations across different user personas (novice, power users, accessibility needs) to identify which versions reduce friction most effectively
Ensures error copy maintains your tone guidelines while prioritizing user empathy and clarity over personality
Generates copy for timeout messages, permission denials, rate limits, quota exceeded, and connectivity issues
Systematically improves existing error messages using UX writing best practices and user mental models
Creates error message guidelines and tone documentation for scalable, consistent messaging across your product
Reviews copy for clear next steps, avoiding passive language and technical jargon that confuses users
Example Output
Example 1: Form Validation Error
Poor: "Invalid input"
Optimized: "Password must be at least 12 characters and include a number"
Example 2: Network Failure Notification
Poor: "Connection timeout error 504"
Optimized: "We're having trouble connecting. Check your internet, then try again—your changes will be saved automatically."
Example 3: Persona-Based Variations (Payment Declined)
- Novice: "Your payment wasn't processed. Contact your bank or use a different card."
- Power User: "Card declined (code: 2015). Update payment method in settings or retry with alternate card."
- Accessibility: "Your payment wasn't processed. Here are your options: [Clear links to contact bank / update card / use alternate payment]"
What's Included
- SKILL.md instruction file with error messaging framework and best practices:
- Error Message Template: Fill-in-the-blank structure for problem, impact, action, and tone
- Persona Worksheet: Define user segments and test copy variations by user type
- Notification Hierarchy Matrix: Categorize errors by severity and required user action
- Copy Testing Checklist: Evaluate messages for clarity, actionability, brand alignment, and accessibility
Who It's For
- UX Writers — Craft empathetic microcopy that reduces user friction and support costs
- Product Managers — Define error messaging strategy and prioritize which edge cases need copy optimization
- UX/UI Designers — Generate and refine error states and notification designs with tested, user-friendly copy
- Design Systems Managers — Build scalable error message guidelines and tone documentation for multi-product organizations
- Customer Support Leaders — Reduce ticket volume by improving clarity and actionability in user-facing error messages
Best For
- Designing error states for forms, transactions, and system failures
- Creating in-app notifications (warnings, confirmations, success states, empty states)
- Testing message variations across user personas to optimize for clarity and task completion
- Building notification hierarchies for complex or regulated products (fintech, healthcare, operations tools)
- Establishing error messaging standards and tone guides for design systems







