Error Handling Ux
This walks you through the full error handling hierarchy from prevention to recovery, which is the right mental model. It pushes you toward inline validation, smart defaults, and constraint-based inputs before errors even happen, then covers detection patterns like real-time validation and network error handling. The communication guidelines are solid: human language, explain what happened and why, tell users what to do next. What I like is the practical breakdown by context (forms get inline plus summary, network errors get toasts with retry, permissions get explanations). It won't magically fix your error messages, but it gives you a checklist to avoid the worst mistakes like clearing forms on error or showing vague "something went wrong" messages.
- installs
- 2.2K
- GitHub stars
- 3.1K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add owl-listener/designer-skills --skill error-handling-ux --agent claude-codeInstalls into .claude/skills of the current project.
Files
Error 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
Sponsors
Details
- Repository
- github.com/owl-listener/designer-skills
- Categories
- Debugging, Design & UI/UX
- First seen
- Jun 3, 2026
