UI DESIGN LAB
  • Home
  • Community
  • Library
  • Knowledge
  • Docs
ZHLogin
Back to knowledge
Interaction Responsive Motion

Destructive Action Confirmation

Destructive Action Confirmation turns a frequent interface judgment into an executable constraint before generation.

dangerconfirmationsafety

Design Principle

Confirmation should protect irreversible or high-impact actions and explain object plus consequence.

Principle Confirmation should protect irreversible or high-impact actions and explain object plus consequence.

Design action Name the object, impact scope, and recovery path; use a specific destructive verb for the primary button and keep cancel safe.

Examples Positive example: Account deletion, rollback, bulk delete, permission change, and payment cancellation are high risk. Counterexample: 'Are you sure?' is the only explanation.

Apply when Account deletion, rollback, bulk delete, permission change, and payment cancellation are high risk. Users need to judge state, scope, risk, or next action quickly.

Source notes Source note: Synthesized from Apple HIG, Material Design, GOV.UK/Polaris/Atlassian component practices, and interaction accessibility principles.

Agent Directive

Name the object, impact scope, and recovery path; use a specific destructive verb for the primary button and keep cancel safe.

Apply When

  • Account deletion, rollback, bulk delete, permission change, and payment cancellation are high risk.
  • Users need to judge state, scope, risk, or next action quickly.

Avoid

  • 'Are you sure?' is the only explanation.
  • Irrelevant structure, copy, or decoration is added only to make the UI feel richer.

Knowledge Metadata

Category
Interaction Responsive Motion
Quality
86%
Version
v1
Published
6/6/2026