Password Reset
Let people back in without opening a hole for everyone else.
What it adds
A request-and-reset flow with expiring single-use tokens, identical public responses regardless of whether the account exists, and session cleanup afterwards.
What your agent is told to do
5
What your agent is told to do
5-
1
Return the same message and the same rough response time whether or not the address has an account. The reset form is the most common account-enumeration oracle in any app.
-
2
Store tokens hashed, expire them within an hour or so, and consume them on use.
-
3
After a successful reset, revoke all other sessions and notify the account by email that the password changed.
-
4
Rate-limit both the request step and the token-submission step, per address and per IP.
-
5
Do not sign the user in automatically from the reset link alone unless the app has decided that link possession equals authentication. Say which you chose and be consistent.
Edge cases it handles
6
Edge cases it handles
6- Requesting several resets must leave exactly one usable token — invalidate the earlier ones and say so in the email.
- A reset link opened after the password already changed must show a neutral expired state, not an error mentioning the account.
- Return-to URLs carried through the flow must be validated against an allowlist; an open redirect here hands over the session.
- Reset tokens must never appear in query strings that get logged, sent as referrers, or captured by analytics.
- If 2FA is enabled, resetting the password must not bypass it.
- The reset must reject the current password if the app forbids reuse, without confirming what the old one was.
Definition of done
8
Definition of done
8- Request responses are identical for existing and non-existing addresses.
- Tokens are hashed, expiring, and single-use, with older tokens invalidated on reissue.
- A successful reset revokes other sessions and emails the account.
- Return destinations are validated against an allowlist.
- Both request and submission steps are rate-limited.
- Reset does not bypass two-factor authentication.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
User Roles
User Roles
Not everyone should be able to do everything.
What it does
Role-based permissions, enforced on the server, with a UI that reflects them.
How it works
-
1
Define roles and their permissions in ONE place. Scattering
if user.admin?through the codebase is how authorization bugs happen. - 2 Enforce every permission server-side, at the controller or service layer.
- 3 Hide UI the user can't use — but never rely on hiding as the enforcement.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/user-roles
Workspace Deletion Workflow
Workspace Deletion Workflow
Close a whole workspace without one click erasing everyone's work.
What it does
An owner-only deletion flow with an explicit inventory, a recovery window, and cascading cleanup across internal and external systems.
How it works
- 1 Restrict deletion to owners and require recent re-authentication plus typing the workspace name. This is the most destructive action in the product and should feel like it.
- 2 Show an inventory before confirming: how many members lose access, what happens to billing, how many files and records are affected, which integrations disconnect, and which shared links die.
- 3 Schedule the deletion rather than executing it. Mark the workspace as pending deletion, block access to it, notify every member and admin, and only purge after a stated recovery window.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/workspace-deletion-workflow
Domain Verification
Domain Verification
Prove an organization controls a domain before unlocking domain-wide powers.
What it does
A DNS or file-based challenge that verifies domain ownership and gates features like enforced SSO and domain-wide join.
How it works
- 1 Generate a unique, unguessable token per organization and domain, and verify it via a DNS TXT record or a file served over HTTPS at a fixed path.
- 2 Check the challenge server-side from the app's own infrastructure. A verification the browser performs can be faked.
- 3 Re-check verified domains on a schedule and mark a domain unverified when the evidence disappears, rather than trusting a one-time pass forever.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/domain-verification
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.