errors-slips
Use this skill when designing to prevent or recover from execution errors — actions that don't match the user's intent. Trigger when designing critical action confirmations, distinct affordances for similar-purpose elements, recovery from wrong-button presses, "I didn't mean to do that" flows. Sub-aspect of `errors`; read that first.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- errors-slips
- description
- Use this skill when designing to prevent or recover from execution errors — actions that don't match the user's intent. Trigger when designing critical action confirmations, distinct affordances for similar-purpose elements, recovery from wrong-button presses, "I didn't mean to do that" flows. Sub-aspect of `errors`; read that first.
02 资源文件 1
- 参考文档references/slip-prevention-patterns.md2.7 KB
03 SKILL.md 正文
Slips: errors of execution
A slip happens when the user knew what they wanted to do but their action didn't match. The intent was right; the execution was wrong. Slips are common in routine tasks where conscious attention has lapsed: the user types "definately" instead of "definitely," clicks Reply when they meant Reply All, deletes the file they meant to keep.
The design responses for slips don't increase the user's knowledge — the user already knew what to do. They make wrong actions structurally harder, give clear feedback when they happen, and provide easy recovery.
The two slip subtypes (from the book)
Action slips
Wrong action despite correct intent. Triggered by:
- Routine tasks performed automatically.
- Distractions or interruptions.
- Similar-looking controls.
- Auto-pilot button-pressing on confirmations.
Design responses:
- Distinctive affordances — make destructive actions visibly different from common ones (color, position, shape).
- Defensible space — separate destructive controls from frequent ones (the "Cancel" near "Save" and "Delete" elsewhere).
- Confirmation for critical tasks — explicit confirmation step (sparingly).
- Constraints — make wrong actions impossible (can't submit a form with required fields empty).
- Mappings — controls match the layout of what they affect (stovetop knobs match burner positions).
Attention slips
Steps missed during a procedure. Triggered by:
- Interruptions (a phone call mid-procedure).
- Long task sequences.
- Resuming a paused task.
Design responses:
- Status cues that survive interruption ("You're on Step 3 of 5").
- Orientation aids when resuming.
- Alarms or alerts for critical steps.
- Highlighting to focus attention on the current step.
Common slip-prevention patterns
Distinct destructive button styling
The destructive button differs from the safe button by color (typically red), position (typically right of the safe button in modal footers), and label (specific verb: "Delete" not "OK"). This triple-difference makes the slip harder.
<div class="dialog-actions">
<button>Cancel</button>
<button class="destructive">Delete project</button>
</div>
Type-to-confirm for irreversible actions
The user must type the resource name to enable the destructive button. Breaks autopilot Enter-pressing.
<p>To confirm, type <strong>Acme Inc</strong>:</p>
<input id="confirm" />
<button id="delete-btn" disabled>Delete Acme Inc</button>
Undo for routine destructive actions
Most slips are caught immediately. A 5–10 second undo window covers them.
async function archive(item) {
const previous = items.slice();
items = items.filter(i => i.id !== item.id);
render();
showToast('Archived', { undo: () => { items = previous; render(); } });
}
Forgot-attachment detection
Email clients scan body text for "attached," "attachment," etc. If found and no attachment exists, prompt before sending.
Step indicators in multi-step procedures
A visible stepper or progress indicator survives interruptions. Returning users see "you were on Step 3."
Read-only by default for sensitive views
Power-user surfaces (admin panels) start in read-only and require explicit "Edit mode" to change values. Reduces accidental edits.
Slip-prone contexts
Some contexts produce more slips than others:
- Routine tasks done many times — automatic execution is more likely to slip.
- Interrupted tasks — resuming at the wrong step.
- Similar-control clusters — adjacent buttons with similar appearance.
- Time pressure — fast typing, fast clicking.
- Modal dialogs users dismiss on autopilot.
Audit slip-prone contexts in your product; apply prevention.
Anti-patterns
- Identical-looking destructive and safe buttons. Slips are inevitable.
- Pre-selected destructive option. Default Enter triggers destruction.
- No undo for routine destructive actions. Each slip is permanent.
- Excessive confirmations for non-destructive actions. Confirmation fatigue; users dismiss real ones too.
Heuristics
- The "what slip is most likely here?" audit. For each high-frequency action, name the slip that would happen and design against it.
- The post-incident slip diagnosis. When users report mistakes, distinguish slips from mistakes. Different fixes.
- The undo-coverage check. What percentage of routine destructive actions have undo? If less than 90%, you have slip exposure.
Related sub-skills
errors(parent).errors-mistakes— the other half; intentional errors driven by wrong models.forgiveness— recovery from slips after they happen.affordance— distinct affordances prevent slip-type wrong-clicks.constraint— structural prevention of wrong actions.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.