Maintenance Mode
Pause the app on purpose instead of serving a generic 500.
What it adds
An operator-controlled outage window that shows a real maintenance page, lets staff through, and tells API clients the truth.
What your agent is told to do
5
What your agent is told to do
5-
1
Make the mode a runtime flag an operator can flip without a deploy, and store it somewhere that stays reachable when the database is the thing being maintained.
-
2
Allowlist bypass for authenticated staff and for the health check endpoint, so the people fixing the problem can still use the app and the load balancer does not remove every instance.
-
3
Return 503 with a Retry-After header for API and crawler requests, and render the maintenance page for browsers. A 200 on a maintenance page tells search engines your content is now an apology.
-
4
Support a read-only variant where GETs continue to work and writes are refused with a clear message, since most maintenance only needs writes stopped.
-
5
Do NOT let background jobs, webhook receivers, and scheduled tasks keep mutating data while the UI is blocked. Pause or queue them explicitly, or the maintenance did nothing.
Edge cases it handles
6
Edge cases it handles
6- The maintenance page must render without hitting the database or any service that might be down — static assets, inline styles, no dynamic content.
- Let the operator set an expected end time and a short message; a page with no information generates more support load than the outage.
- In-flight requests when the flag flips should be allowed to finish rather than cut off mid-write.
- Webhook senders that get a 503 will retry; make sure the retry window is compatible with Retry-After or you will lose events.
- Turning maintenance off must take effect immediately across every instance, not on the next cache expiry or restart.
- Staff bypass must be identity-based, not a shared query-string token that leaks into logs and chat.
Definition of done
8
Definition of done
8- An operator can enable and disable maintenance without deploying.
- Browsers get a maintenance page; API and crawler requests get 503 with Retry-After.
- Staff and health checks bypass the block.
- The page renders with the database unavailable.
- Background jobs and webhook processing are paused or queued during the window.
- Read-only mode is available and blocks writes with a clear message.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Content Reporting
Content Reporting
Let users flag content that needs a human to look at it.
What it does
A reporting flow that captures a reason, a snapshot of context, and enough signal for a moderator — without exposing the reporter.
How it works
- 1 Add a report action to every user-generated surface: posts, comments, profiles, files, messages. Offer a short list of concrete reasons plus an optional free-text field.
- 2 Capture the context a moderator needs at the moment of reporting — the content ID, its current body, the author, and a timestamp — so the review is not dependent on the content still existing.
- 3 Give the reporter an immediate self-serve action alongside the report: hide this item, mute this author, or both. A report that takes hours to review leaves the user staring at the thing they reported.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/content-reporting
Scheduled Job Monitor
Scheduled Job Monitor
Find out a nightly task stopped running before your users do.
What it does
A record of every recurring schedule, the runs it was expected to make, and alerts when a run is missed or late.
How it works
- 1 Register every recurring task with its schedule expression, its time zone, and an expected maximum duration. A schedule that is not registered cannot be monitored.
- 2 Record the start and the completion of each run separately. A task that started and never finished is a different failure from one that never started, and they need different alerts.
- 3 Compute the expected run times forward from the schedule and compare them against actual starts. Alert on a missed run, and alert separately when a run starts on time but overruns its expected duration.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/scheduled-job-monitor
Notification Delivery Failures
Notification Delivery Failures
Know when a message failed to arrive and stop sending to addresses that cannot receive it.
What it does
Bounce and complaint handling with a suppression list, plus telling the affected user their address is failing.
How it works
- 1 Consume the delivery provider's webhooks for bounces, complaints, and deferrals, verify their signatures, and deduplicate repeated events by provider event ID.
- 2 Separate hard bounces and spam complaints, which suppress the address permanently, from transient failures, which retry with backoff and only suppress after a threshold.
- 3 Keep the suppression list per channel and per address, and check it before every send. Extend the existing notification preference model with delivery health rather than building a second gate beside it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/notification-delivery-failures
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.