Individual skill

errors

Use this skill whenever a design must accommodate the inevitability of human error — typos, wrong-button presses, misread instructions, mistimed actions, misunderstandings of system state. Trigger when designing form validation, input handling, destructive flows, complex multi-step procedures, alert systems, or any UI where users can do the wrong thing. Trigger when post-incident analyses reveal patterns of "human error" — most are design errors in disguise. Errors is one of the foundational principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003), grounded in Norman's and Reason's foundational human-error research.

plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/errors/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Errors

Most "accidents" attributed to human error are actually design errors. The user took the action the design invited; the action's consequence wasn't what the user intended. Reframing errors as a *design* property — rather than a *user* failing — opens the design space dramatically: errors can be prevented, made impossible, made obvious, or made recoverable. The right strategy depends on the kind of error.

## Definition (in our own words)

An error is any action (or omission) that produces an unintended result. Errors come in two distinct kinds, and they need different design responses. **Slips** are skill-based failures: the user knew what to do but their action didn't match their intent — a typo, a wrong-button click, a slip of attention. **Mistakes** are knowledge-based failures: the user did exactly what they intended, but the intent was wrong because their model of the situation was wrong — they misread an alarm, misunderstood a diagram, made a wrong choice based on incomplete information. The two kinds happen for different reasons; they're prevented by different design moves.

## Origins and research lineage

- **Donald Norman**, "Categorization of Action Slips" (*Psychological Review*, 1981, vol. 88) and *The Design of Everyday Things* (1988). Norman introduced the slip/mistake distinction to design vocabulary and argued that error is a property of design, not user.
- **James Reason**, *Human Error* (Cambridge University Press, 1990). The standard reference work in human-error research, originally from industrial-safety domains (aviation, nuclear, medical). Reason expanded Norman's framework with detailed taxonomies (skill-based / rule-based / knowledge-based errors) and the "Swiss cheese" model of cascading failures.
- **Lidwell, Holden & Butler** (2003) compactly distinguished slips (errors of execution, automatic/unconscious) from mistakes (errors of intention, conscious mental processes). The book identifies two slip subtypes (Action, Attention) and three mistake subtypes (Perception, Decision, Knowledge).
- **Charles Perrow**, *Normal Accidents* (1984). Argued that complex tightly-coupled systems produce errors as an emergent property of system design, not as failures of individual operators. Influential in industrial-safety and software-system design.