Agent Skills
› Owl-Listener/designer-skills
› error-handling-ux
error-handling-ux
GitHub专注于设计产品的错误预防、检测与恢复体验，涵盖消息内容、位置及用户引导。适用于跨流程的复杂错误场景处理，旨在减少用户挫败感并提升成功率。
Trigger Scenarios
需要设计跨多个流程的错误处理机制
优化产品中的错误提示与用户恢复路径
Install
npx skills add Owl-Listener/designer-skills --skill error-handling-ux -g -y
SKILL.md
Frontmatter
{
"name": "error-handling-ux",
"description": "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`."
}
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
Version History
-
20e34c4
Current 2026-08-19 23:21
技能描述增加了使用触发条件和边界说明，以解决与其他技能（如表单设计）的重叠问题，确保在多技能环境下准确触发。
- acc3e57 2026-07-25 05:15
