Error Handling Ux

owl-listener/designer-skills/interaction-design/skills/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 從公開儲存庫中收錄這些內容。

檢舉或申請下架