Offline & Reconnection

What it does

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

When to use it

Use for offline banners, service workers, queued writes, or bugs where connectivity changes misstate server status.

Problems it prevents

Stops a page claiming a save succeeded when the connection actually dropped mid-request.

Typical workflow

1. Define the capability model (what works offline)
2. Handle connectivity state honestly
3. Queue and retry with backoff
4. Verify sync-conflict handling

Example output

A queued write that survives a dropped connection and syncs correctly once the network returns, with no duplicate submit.

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

• FocusedAutosave & Draft Recovery

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

• FocusedUndo & Optimistic Actions

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

• SystemBackground Jobs & Queues

  Designs reliable background jobs and queues: retries, idempotency, ordering, dead-letter handling, recovery.