Skip to content
cccskills
FreePublished on GitHub

error-handling-ux

Design error prevention, detection, and recovery across a product — message content, placement, and escape routes. Use when errors span multiple flows. For validation inside a single form, use `form-design`.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

The English summary is being prepared. Showing the original description.

Owl-Listener/designer-skills3KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill