mcpField
E
error-handling-ux

error-handling-ux

github.com/owl-listenerDesign & UI3.1k2.2k installsUpdated 8w ago
Repository

About error-handling-ux

A UX design skill for planning error experiences that help users avoid, understand, and recover from problems. It covers prevention, detection, clear messaging, and recovery patterns across common interface contexts.

Key features

  1. 01Error prevention patterns
  2. 02Validation and failure detection
  3. 03Clear, actionable error messages
  4. 04Recovery and retry options
  5. 05Context-specific error states
  6. 06Error-path testing guidance

Use cases

  1. 01Designing form validation and feedback
  2. 02Handling network or timeout failures
  3. 03Creating recovery paths for destructive actions

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/owl-listener/designer-skills --skill error-handling-ux

After installing, type/error-handling-uxin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported