npx skills add https://github.com/owl-listener/designer-skills
infrasity-labs/dev-gtm-claude-skills
error-handling-ux
Design error prevention, detection, and recovery experiences.
Installation
npx skills add infrasity-labs/dev-gtm-claude-skills --skill error-handling-ux
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Design error prevention, detection, and recovery across a product — message content, placement,…
1.5K installsGuidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsAlso in this package
Other skills from infrasity-labs/dev-gtm-claude-skills · top by installs.
npx skills add infrasity-labs/dev-gtm-claude-skills
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md1,802 B -
docs
SUMMARY.md86 B
History
- First seen on skills.sh
- First recorded snapshot · 53 installs
SKILL.md
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