Autosave & Draft Recovery

What it does

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

When to use it

Use for editors, long forms, multi-tab editing, or bugs that lose work or falsely report a saved state.

Problems it prevents

Stops a 'saved' indicator showing when the draft actually failed to persist.

Typical workflow

1. Choose the save model and timing
2. Detect and resolve version conflicts
3. Recover drafts after a crash or reload
4. Verify the save indicator is honest

Example output

A long form that recovers its exact draft state after an accidental tab close, with a save indicator that's never wrong.

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

• FocusedUndo & Optimistic Actions

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

• FocusedOffline & Reconnection

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

• FocusedForm Error States

  Designs accessible, recoverable validation and submission errors that never discard what the visitor typed.