Background Job Progress
Show people what a long import, export, or report is actually doing.
What it adds
Durable progress for long-running work, with distinct states, live updates, and a real failure path.
What your agent is told to do
5
What your agent is told to do
5-
1
Persist job state server-side: status, progress, counts, started and finished times, and the requesting user.
-
2
Model the states explicitly — queued, running, stalled, cancelled, failed, completed — and give each its own copy. A single spinner cannot express any of that.
-
3
Push updates to the client where you can, and fall back to polling with a widening interval. Progress must survive a refresh, a closed tab, and a different device.
-
4
Let the user cancel a running job, and make cancellation actually stop the work rather than just hiding the row.
-
5
Do NOT show a percentage you cannot compute. An honest 'processed 4,120 of 50,000 rows' beats a fabricated bar that sits at 90 percent.
Edge cases it handles
7
Edge cases it handles
7- A job with no heartbeat for a defined period is stalled, not running. Say so and offer retry.
- Launching the same job twice must be blocked while one is in flight, with a clear reason.
- A job that completes after the user lost access to the source data must not deliver its output.
- Retry must be safe to press twice. Partial work already committed should not be duplicated.
- Error details must be actionable for the user — which row, which field — without exposing stack traces or internal identifiers.
- Completed job artefacts need a retention policy and expiring download links.
- A queue backlog must be visible as queued, not as a running job stuck at zero percent.
Definition of done
9
Definition of done
9- Job state is persisted and reloads correctly after a refresh or on another device.
- Queued, running, stalled, cancelled, failed, and completed are distinguishable in the UI.
- Progress reflects real measured work, or shows counts instead of a fake percentage.
- Duplicate submissions of the same job are prevented while one is in flight.
- Cancellation stops the work, not just the display.
- Failures offer retry and user-readable error detail with no stack traces.
- Generated files expire on a defined schedule.
- 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
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
Staff Shift Schedule
Staff Shift Schedule
Show who is working when for the week, with coverage gaps visible at a glance.
What it does
A weekly grid of staff shifts with draft and published states and coverage warnings.
How it works
- 1 Build the minimum coherent version first: a week grid, shifts you can create and move, a draft state, and a publish action. Leave shift swapping, time-off requests, and labour-cost forecasting out until the grid is in daily use.
- 2 Keep an editable draft separate from what staff currently see, and change nothing for them until the week is published. A schedule that shifts under people as the manager thinks aloud is worse than a printed sheet.
- 3 Show coverage as a strip along the grid, comparing the people scheduled in each hour against a required level, so a gap is visible without reading every row.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/staff-shift-schedule
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.