Error handling
Skill Dragoon0x/everything-design-taste/skills/error-handling
A taste system for AI agents. 288 skills, 80 agents, 12 rules, and 8 hooks that turn generic AI output into work with genuine design quality. Anti-slop detection, typography craft, color systems, brand voice, product strategy, and 50+ specialized reviewers across UI, industry, platform, and content domains.
npx -y skills add Dragoon0x/everything-design-taste --skill error-handlingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Error states, error messages, recovery flows, error prevention, and graceful degradation.
SKILL.md
1.7 KB, as published. Nobody here has run it
Error Handling
Error Message Formula
What happened + Why (if useful) + What to do now
Bad
"Error 500: Internal server error"
Good
"We couldn't save your changes. Our servers are having trouble. Try again in a few minutes, or your changes will be saved automatically when we're back."
Error Types & Treatment
| Error | Show Where | Persist | User Action |
|---|---|---|---|
| Field validation | Inline next to field | Until fixed | Fix input |
| Form submission | Top of form + inline | Until fixed | Fix and resubmit |
| Network error | Banner or toast | Until resolved | Retry or wait |
| Auth error | Full page or modal | Until resolved | Log in again |
| Not found | Full page | N/A | Go back or search |
| Server error | Full page or banner | Until resolved | Retry later |
Prevention Over Recovery
- Inline validation catches errors before submission
- Confirmation dialogs prevent accidental destructive actions
- Autosave prevents data loss
- Undo is better than "Are you sure?"
- Smart defaults reduce wrong inputs
- Input masks format data as users type
Rules
- Never use technical jargon (error codes, stack traces)
- Never blame the user ("You entered an invalid...")
- Always provide a path forward
- Preserve user input on error (never clear the form)
- Use appropriate severity (red for errors, yellow for warnings, blue for info)
- Log errors for debugging even if users don't see details