Stale Data Indicator
Tell people when the screen is out of date, and give them a safe way to refresh.
What it adds
A visible marker of data age on cached or background-refreshed screens, with a manual refresh.
What your agent is told to do
6
What your agent is told to do
6-
1
Find the screens serving cached or polled data and record when each was last successfully fetched.
-
2
Show the age only once it matters. A freshness label on data that is two seconds old is noise.
-
3
Distinguish three states clearly: cached and ageing, refresh failed, and offline. They call for different copy and different actions.
-
4
Give the user a manual refresh that re-runs the fetch for that view rather than reloading the page.
-
5
Do not silently replace what is on screen while the user is reading or editing it. Fetch, then offer the update.
-
6
Do not auto-refresh a background tab on a timer; refresh when it becomes visible again.
Edge cases it handles
6
Edge cases it handles
6- A refresh must never discard unsaved local edits. Hold the new data until the form is clean or the user chooses.
- Repeated clicks on refresh must not spawn parallel requests; disable the control while one is in flight.
- Timestamps must render in the user's locale and time zone, not the server's.
- A failed refresh must keep showing the old data with a warning, not blank the view.
- Do not mark data stale purely because a websocket dropped, if the underlying record has not changed.
- A device with a badly wrong clock must not produce ages in the future.
Definition of done
8
Definition of done
8- Cached screens show when the data was last fetched.
- Stale, failed, and offline are visually and textually distinct.
- Manual refresh re-fetches the view without a full page reload.
- Unsaved edits survive a refresh.
- Concurrent refresh requests are prevented.
- Timestamps respect the user's locale and time zone.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Upload Malware Scanning
Upload Malware Scanning
Quarantine uploaded files until they are known safe.
What it does
A quarantine lifecycle for uploads: every new file is unreachable until scanned, with defined handling for scanner failures and infected results.
How it works
- 1 Give every upload an explicit scan state — pending, clean, infected, or error — and default it to pending the moment the bytes land.
- 2 Make pending and infected files unreachable from every access path in the app, including admin views, previews, thumbnails, and any signed URL. A quarantine with one exception is not a quarantine.
- 3 Scan asynchronously and update the state; do not block the upload request on the scanner.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/upload-malware-scanning
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
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.