Service Incident Banner
Warn users about outages and maintenance inside the app, without a deploy.
What it adds
An operator-controlled banner announcing degraded service, incidents, or planned maintenance to the right users.
What your agent is told to do
5
What your agent is told to do
5-
1
Give operators a way to create, schedule, and end a banner from an admin screen. Requiring a deploy to announce an outage means it goes out late or not at all.
-
2
Support severity levels with different treatments: informational, degraded, and outage.
-
3
Let a banner target a subset of users by plan, region, workspace, or affected feature, and default to nobody rather than everybody.
-
4
Support a scheduled start and an automatic expiry, so a maintenance notice does not linger for a week after the work is done.
-
5
Serve the banner from a path that does not depend on the main application API. A banner that goes down with the thing it is announcing is useless.
Edge cases it handles
6
Edge cases it handles
6- Informational banners may be dismissed; an active outage banner must stay until the incident ends.
- A dismissal must be remembered per user and per banner, and must reset if the message is edited.
- The banner must not cover fixed navigation or shift the layout when it appears.
- Two active incidents need a defined order; show the highest severity rather than stacking three bars.
- Copy must be written for customers, not for engineers. No internal service names, no ticket IDs.
- Link to a status page if one exists, and make sure that link works when the app does not.
Definition of done
8
Definition of done
8- Operators can publish, schedule, and expire a banner without a deploy.
- Banners can target specific plans, regions, or workspaces.
- Severity is reflected in the treatment, and critical banners cannot be dismissed.
- Dismissals persist per user and reset when the message changes.
- The banner renders even when the primary API is degraded.
- Expired and scheduled banners appear and disappear on time.
- 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
Maintenance Mode
Maintenance Mode
Pause the app on purpose instead of serving a generic 500.
What it does
An operator-controlled outage window that shows a real maintenance page, lets staff through, and tells API clients the truth.
How it works
- 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.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/maintenance-mode
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.