Backup Restore Design

Use this skill to design data durability as a product feature and operational system.

Workflow

1. Identify data classes: user content, settings, purchases, game progress, files, account state, audit records, analytics, secrets.
2. Read references/backup-restore-patterns.md.
3. Define RPO/RTO, retention, encryption, ownership, export, deletion, and support visibility.
4. Design backup, restore, conflict resolution, migration, and recovery drills.
5. Prove restore works with procedural runbooks, checksum/manifest verification, evidence retention, owners, alerting, and cost/capacity guardrails.
6. For E2EE products, keep plaintext and master keys client-owned; support may verify encrypted snapshot integrity and guide recovery, but must not hold or unwrap user content keys unless the product explicitly has an enterprise escrow model.
7. Produce event schema and failure modes.

When not to use

• Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails