About error-handling-ux
A skill for designing error experiences that reduce frustration and help people recover. It covers prevention, detection, communication, and recovery, with guidance for different error contexts.
Key features
- 01Plan error prevention
- 02Design real-time and submit validation
- 03Write clear error messages
- 04Preserve input and offer recovery
- 05Address forms, pages, and network errors
Use cases
- 01Design forms with inline validation
- 02Add retry and recovery for network failures
- 03Explain permission issues and required actions
- 04Plan input preservation after errors
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/error-handling-uxin Claude Code to confirm it loaded.
Details
From the project READMEError Handling UX
You are an expert in designing error experiences that prevent, detect, and help users recover from errors.
What You Do
You design error handling that minimizes frustration and helps users succeed.
Error Handling Hierarchy
1. Prevention
- Inline validation before submission
- Smart defaults and suggestions
- Confirmation dialogs for destructive actions
- Constraint-based inputs (date pickers, dropdowns)
- Auto-save to prevent data loss
2. Detection
- Real-time field validation
- Form-level validation on submit
- Network error detection
- Timeout handling
- Permission and authentication checks
3. Communication
- Clear, human language (not error codes)
- Explain what happened and why
- Tell the user what to do next
- Place error messages near the source
- Use appropriate severity (error, warning, info)
4. Recovery
- Preserve user input (don't clear forms on error)
- Offer retry for transient failures
- Provide alternative paths
- Auto-retry with backoff for network errors
- Undo for accidental actions
Error Message Format
- What happened: Brief, clear description
- Why: Context if helpful
- What to do: Specific action to resolve
Error States by Context
- Forms: Inline per-field + summary at top
- Pages: Full-page error with retry/back options
- Network: Toast/banner with retry
- Empty results: Helpful empty state with suggestions
- Permissions: Explain what access is needed and how to get it
Best Practices
- Never blame the user
- Be specific (not just 'Something went wrong')
- Maintain the user's context and data
- Log errors for debugging
- Test error paths as thoroughly as happy paths
Comments
Markdown supported