errors

Diagnose slip and mistake types to select prevention and recovery patterns.

6|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/HDeibler/universal-design-principles --skill errors-hdeibler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: errors
Source: https://github.com/HDeibler/universal-design-principles/tree/main/plugins/interaction-and-control-principles/skills/errors
Command: npx skills add https://github.com/HDeibler/universal-design-principles --skill errors-hdeibler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you design for the inevitability of human error so users don’t end up with unintended outcomes from slips or mistaken intentions.

Core Features & Use Cases

  • Slip vs. mistake framing: distinguishes execution/attention failures from intention/model failures to choose the right prevention strategy.
  • Subtype-based design responses: applies targeted fixes for action slips, attention slips, perception mistakes, decision mistakes, and knowledge mistakes.
  • Worked design patterns: provides concrete examples for confirmation, affordances, feedback loops, undo flows, checklists, and guided recovery.
  • When to apply: covers validation, destructive flows, high-stakes systems, complex multi-step procedures, alerts, and post-incident “human error” reviews.

Quick Start

Use the errors skill when reviewing a flow where users can do the wrong thing so you can classify the likely error type and apply prevention plus recovery (e.g., undo, clearer state cues, or better information) before shipping.

Frequently Asked Questions about errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design UX error prevention for destructive actions and form validation?

You can choose the right error prevention strategy by diagnosing whether a user error is an execution slip or an intention mistake. Slips require constraints and feedback loops, while mistakes need clearer state cues, better information, and guided recovery patterns.

What is the difference between a slip and a mistake in UX error design?

In UX error design, a slip is an execution or attention failure where the user's intention is correct but the action is wrong, whereas a mistake is an intention or model failure where the user chooses the wrong goal. This distinction dictates whether you apply prevention or recovery patterns.

How do I add undo recovery and confirmation patterns to high-stakes user flows?

Adding undo recovery and confirmation patterns to high-stakes flows involves applying targeted design responses for action slips and decision mistakes. You implement undo flows, checklists, and guided recovery mechanisms to enable users to reverse unintended outcomes after performing destructive actions.

When should I use confirmation design versus undo recovery in destructive flows?

You should use confirmation design when users are making decision mistakes that require clearer information, and use undo recovery when users commit action slips that need reversible outcomes. Destructive flows often combine both patterns to prevent errors and enable post-incident recovery.

Can I use human error frameworks for post-incident analysis of complex multi-step procedures?

Yes, you can use human error frameworks for post-incident analysis of complex multi-step procedures by classifying the failure as a perception mistake, attention slip, or knowledge mistake. This diagnosis reveals whether the system needs better affordances, feedback loops, or trend-aware information.