This walks you through the full error handling hierarchy from prevention to recovery, which is the right mental model. It pushes you toward inline validation, smart defaults, and constraint-based inputs before errors even happen, then covers detection patterns like real-time validation and network error handling. The communication guidelines are solid: human language, explain what happened and why, tell users what to do next. What I like is the practical breakdown by context (forms get inline plus summary, network errors get toasts with retry, permissions get explanations). It won't magically fix your error messages, but it gives you a checklist to avoid the worst mistakes like clearing forms on error or showing vague "something went wrong" messages.
npx skills add https://github.com/owl-listener/designer-skills --skill error-handling-ux