Error Handling Ux

作者 owl-listener9a6930cf84a8无许可证2.8K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库4周前更新

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`.

仅含说明Design & Creative
AI 生成的概览

为产品设计错误的预防、检测、沟通与恢复体验。

功能
该技能指导智能体为产品设计错误体验,涵盖预防、检测、沟通和恢复四个层面。它给出错误处理层级、三段式错误消息格式(发生了什么、为什么、该怎么做),以及表单、页面、网络、空结果和权限等场景下的错误状态。还列出最佳实践,例如不归咎用户、表述具体、保留用户输入、记录错误日志并像测试正常路径一样测试错误路径。
适用场景
当错误处理跨越产品的多个流程或页面、需要统一做法时使用。它面向更广泛的错误体验设计,而非单个表单内的校验;后者该技能建议使用单独的 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

来源与署名

来源:owl-listener/designer-skills位于interaction-design/skills/error-handling-ux提交9a6930c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架