Backup Verification
Prove your backups restore, instead of trusting that they exist.
What it adds
Automated checks that a backup is complete, encrypted, retained, and actually restorable — with a recorded test restore rather than an assumption.
What your agent is told to do
6
What your agent is told to do
6-
1
Inventory what must be backed up first: every database, every uploaded-file store, and any external state the app cannot rebuild. A backup covering only the primary database is a partial backup, and should be reported as one.
-
2
After every backup, verify it mechanically: the file exists, its checksum matches, its size is within a sane band of the previous run, it is encrypted, and it is where the retention policy expects it.
-
3
Restore on a schedule into a fully isolated environment and assert against the restored data — row counts within expected ranges, the newest record close to the backup time, and a handful of known invariants.
-
4
Neutralise all outbound side effects in the restore environment before the data loads. Disable mail, webhooks, payment calls, push notifications, and analytics at the configuration level, not by hoping the code paths are not reached.
-
5
Record recovery-point and recovery-time evidence for each test: how much data would have been lost, and how long the restore took. Trend both over time — a restore that gets slower each month is a future incident.
-
6
Do NOT treat a successful backup job as a successful backup. A zero-byte file uploaded without error passes every check that only looks at the exit code.
Edge cases it handles
7
Edge cases it handles
7- The restore environment must never be able to reach production credentials, queues, or third-party accounts. Verify the isolation as part of the test, not once at setup.
- Restored data is production data. It carries the same access controls, retention obligations, and deletion requests, and the environment must be destroyed after the test.
- A size band catches truncation but also fires on legitimate growth. Compare against a rolling baseline rather than a fixed number.
- Verify that the encryption key needed to restore is itself recoverable and stored separately from the backup. A backup you cannot decrypt is not a backup.
- Retention deletion must be checked in both directions: old backups actually removed, and recent backups not removed early.
- A failing verification must alert loudly. Silent verification failures produce a system that has looked healthy for months.
- Uploaded files and database rows can drift apart. Check that a sample of restored records still points at objects present in the restored file store.
Definition of done
9
Definition of done
9- Every data store requiring backup is inventoried, and partial coverage is reported as partial.
- Each backup is checked for existence, checksum, size band, encryption, and retention placement.
- A scheduled test restore runs into an isolated environment and asserts data invariants.
- Mail, webhooks, payments, and push are disabled by configuration in the restore environment.
- Recovery-point and recovery-time figures are recorded per test and trended.
- Restore environments are destroyed after verification.
- A failed verification raises an alert rather than being logged quietly.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Password Generator
Password Generator
Offer a strong password in one click wherever someone sets or changes credentials.
What it does
A generate control on password fields that produces a strong value, shows it, and hands it to the user safely.
How it works
- 1 Add the control to every place a password is set: sign-up, password change, password reset completion, and any admin screen that provisions credentials for someone else.
- 2 Generate the value in the browser using the platform's cryptographic random source. The value must never be produced on the server or sent anywhere.
- 3 Reveal the generated password by default so the user can record it, and offer a regenerate control beside it. A hidden generated password that the user cannot see is a password they will immediately reset.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/password-generator
Idempotent Form Submission
Idempotent Form Submission
Make one submit mean one result, even when the network retries.
What it does
Idempotency keys on high-impact writes so a double-click, a retry, or a refresh cannot create the same record twice.
How it works
- 1 Find the writes where a duplicate is expensive — payments, orders, invitations, provisioning, anything that sends money or email.
- 2 Generate an idempotency key when the form is rendered, send it with the submission, and persist it server-side alongside the result of the first successful attempt.
- 3 When the same key arrives again, return the stored result instead of doing the work a second time. When the same key arrives with a different payload, reject it — that is a client bug, not a retry.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/idempotent-form-submission
Client Version Compatibility
Client Version Compatibility
Handle the tab that has been open since two deploys ago.
What it does
The server tells the client which build it expects, and the client responds — quietly for an optional update, insistently when the old code can no longer talk to the API.
How it works
- 1 Stamp every build with a version identifier and return it on API responses, either in a header or a small metadata endpoint. The client compares it against the version it was built as.
- 2 Separate two cases and treat them differently. A newer build being available is an optional update — offer it and let the user finish what they are doing. An API contract the running client cannot satisfy is a hard incompatibility and must block further writes.
- 3 For an optional update, show an unobtrusive, dismissible prompt and apply the new version at the next natural navigation. Do not interrupt.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/client-version-compatibility
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.