Safe Retry
Let people retry failed work without doing it twice.
What it adds
A retry control on failed operations that knows which failures are worth retrying and which are not.
What your agent is told to do
5
What your agent is told to do
5-
1
Find every operation that can fail mid-flight and currently leaves the user guessing: payments, invitations, uploads, exports, webhooks.
-
2
Classify each failure as transient or permanent, and only offer retry on the transient ones. Invalid input, revoked permissions, and rejected cards will fail identically forever; explain the fix instead of offering a button that cannot work.
-
3
Preserve the original input and the original error so a retry does not mean re-entering the form.
-
4
Reuse the same idempotency key for every retry of one attempt so the second try cannot duplicate the first. The key mechanism itself belongs to Idempotent Form Submission — wire into it rather than building a second one.
-
5
Do not retry automatically without telling the user. A silent background retry that eventually fails leaves them believing the work is still in progress.
Edge cases it handles
6
Edge cases it handles
6- A timeout is not a failure. The work may have succeeded, so the retry path must be idempotent or the user pays twice.
- The retry control must disable itself while an attempt is running, and stay disabled through the response.
- Automatic retries need exponential backoff with jitter, or a recovering server gets knocked over again.
- Cap the number of attempts and then say clearly that it has stopped trying.
- A retry after a partial success must resume, not restart from the beginning.
- A failure the user cannot act on still needs an exit: a way to abandon the operation and clear it out of their way.
Definition of done
8
Definition of done
8- Every retryable failure offers a retry, and every permanent one explains the fix instead.
- A retry reuses the original attempt's idempotency key rather than issuing a new one.
- Retry controls disable while an attempt is in flight.
- Permanent failures do not offer a retry.
- Original input and error context survive the retry.
- Automatic retries back off and stop at a defined limit.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Rate Limiting
Rate Limiting
Stop one client from ruining it for everyone.
What it does
Throttling on the endpoints that get abused: auth, search, exports, and public forms.
How it works
- 1 Identify the endpoints worth protecting: sign-in, sign-up, password reset, search, exports, and anything unauthenticated.
- 2 Limit by a stable identifier — user ID where signed in, IP otherwise. Be aware IP is shared behind NAT and proxies.
- 3 Return 429 with a Retry-After header. Do not silently drop the request.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/rate-limiting
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
Data Integrity Constraints
Data Integrity Constraints
Enforce your important rules in the database, not just in the form.
What it does
Database-level uniqueness, foreign key, check, and not-null constraints backing the business rules the application currently only validates in code.
How it works
- 1 Inventory the rules the app relies on — required fields, uniqueness, valid enum values, positive amounts, referential links — and note which exist only in application code.
- 2 Before adding each constraint, query for rows that already violate it and decide explicitly whether to fix, delete, or exclude them. Every mature database has violating legacy rows.
- 3 Add constraints in a way that does not hold a long exclusive lock: create indexes concurrently, add checks as NOT VALID and validate them in a second step.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/data-integrity-constraints
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.