Pattern 28 · Complete

Destructive
Confirmation

Prevents accidental irreversible actions through explicit targets, concrete consequences, deliberate verification, and safe focus.

Functional demo

Name the target and consequence

The demonstration requires the project name because deletion includes all project content. It changes only this local catalog example.

Design system

Aurora

  • 12 members
  • 48 files
  • Updated today
Permanent action

Decision levels

Add friction in proportion to risk

Reversible removal uses Undo. Limited permanent loss uses a two-action Dialog. Broad irreversible loss adds typed verification.

ReversibleAction + Undo
PermanentConfirm Dialog
High impactTyped verification

Submission lifecycle

Keep request state unambiguous

Disable duplicate submission while pending. Keep the Dialog and context on failure; close, update, and announce only after success.

Initial focusSafe action
Pendingaria-busy="true"
SuccessUpdate + announce

Usage guidance

Use confirmation for meaningful risk.

Routine friction teaches people to dismiss warnings. Reserve this pattern for consequences that deserve a deliberate pause.

Next component: Button

Delete Aurora?

This permanently removes the project and its content.

Aurora12 members · 48 filesPermanent
  • Members lose access immediately.
  • Files and project history cannot be recovered.