Individual skill

forgiveness

Use this skill whenever a design lets users do something they might regret — delete, send, publish, charge, transfer, archive, overwrite, irrecoverably commit. Trigger when designing destructive actions, undo systems, confirmation dialogs, soft-delete recovery, draft-saving, transaction reversal, "are you sure?" patterns, or any flow where a wrong move costs the user time, data, money, or trust. Trigger when the user mentions "users keep deleting things," "we get support tickets about lost data," "is this dangerous?", or when reviewing destructive UI. Forgiveness is one of the central principles in 'Universal Principles of Design' (Lidwell, Holden, Butler 2003) and one of Nielsen's 10 heuristics ("user control and freedom").

plugins/HDeibler/universal-design-principles/plugins/interaction-and-control-principles/skills/forgiveness/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,530
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

# Forgiveness

Forgiveness is the property of a design that helps users avoid mistakes and recover gracefully from the ones they make. The opposite — an unforgiving design — punishes errors with lost work, irreversible changes, or hostile error states. Since human error is inevitable, forgiving design is what determines whether the product is pleasant to use over time or a constant source of low-grade anxiety.

## Definition (in our own words)

A forgiving design recognizes that users will make mistakes — slips (correct intent, wrong action), mistakes (wrong intent because of wrong model), and accidents (the cat walked across the keyboard). It builds in mechanisms to *prevent* errors before they happen, *minimize their consequences* when they do happen, and *recover from them* when prevention and minimization both fail. The principle's central insight: error is a property of the *design*, not of the user. A design that produces lots of user error is a poorly-designed design, even if every user "could have been more careful."

## Origins and research lineage

- **Lidwell, Holden & Butler**, *Universal Principles of Design* (2003) compactly articulated the principle and identified six strategies for incorporating forgiveness: good affordances, reversibility of actions, safety nets, confirmation, warnings, and help. The book noted an inverse relationship: stronger affordances and reversibility reduce the need for confirmations, warnings, and help.
- **Donald Norman**, *The Design of Everyday Things* (1988, revised 2013) emphasized that "designing for error" is a core design responsibility, not an afterthought. Norman drew heavily on safety-engineering literature.
- **James Reason**, *Human Error* (Cambridge University Press, 1990). The standard reference work in human-error research, originally grounded in industrial-safety analysis (aviation, nuclear, medical). Reason's slip/mistake distinction (a slip is a wrong action despite correct intent; a mistake is a correct action of a wrong intent) shapes most modern error-recovery thinking.
- **Jakob Nielsen**, "10 Usability Heuristics" (1994 onward). Two of the ten heuristics directly concern forgiveness: "User control and freedom" (undo, escape) and "Help users recognize, diagnose, and recover from errors."