Undo & Optimistic Actions

What it does

Implements reversible actions and optimistic UI that stays honest about what the server actually confirmed.

When to use it

Use for undo-after-delete, optimistic create/update, or audits where fast UI feedback conceals a failed operation.

Problems it prevents

Stops an optimistic UI update sticking around after the server has actually rejected the change.

Typical workflow

1. Choose the right protection (undo vs confirm)
2. Model the mutation and rollback path
3. Implement the undo window
4. Reconcile with authoritative server state

Example output

A delete action with a real undo window that only becomes permanent once the server has actually confirmed it.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• FocusedConfirmation Modals

  Implements accessible confirmation dialogs for genuinely consequential actions, with correct focus trapping.

• FocusedAutosave & Draft Recovery

  Implements reliable autosave and crash recovery so a closed tab or crash never loses long-form input.

• FocusedOffline & Reconnection

  Implements resilient offline, retry and reconnection behaviour so a dropped connection never loses work.