Admin Dashboard
The internal screen you'll need the day you have real users.
What it adds
An internal-only dashboard for the metrics and controls you need to actually run the product.
What your agent is told to do
4
What your agent is told to do
4-
1
Find the app's existing authorization system and add an admin role to it. Do not build a parallel admin auth system, and never gate admin behind a hardcoded email list.
-
2
Show the numbers that matter for THIS product: signups, active users, revenue if applicable, errors, queue health.
-
3
Add the operational controls you will actually reach for: find a user, view their state, fix their problem.
-
4
Keep it plain. This screen is for you, not for customers.
Edge cases it handles
4
Edge cases it handles
4- The admin area must be invisible AND inaccessible to non-admins — verify by requesting the URL directly as a normal user.
- Admin actions against user data must be logged: who did what, when.
- Aggregate queries must not table-scan production on every page load; cache them.
- Never expose passwords, tokens, or full payment details in the admin UI.
Definition of done
7
Definition of done
7- Admin is enforced by the app's real authorization system, server-side.
- A non-admin requesting any admin URL is refused.
- The dashboard shows the metrics that matter for this product.
- Admin actions against user data are audit-logged.
- No secrets or full payment details are exposed.
- 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.