Staff Shift Schedule
Show who is working when for the week, with coverage gaps visible at a glance.
What it adds
A weekly grid of staff shifts with draft and published states and coverage warnings.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Reuse the app's Recurring Schedule Builder for repeating shift patterns rather than adding a second recurrence engine, and reuse the existing notification channels for change notices instead of introducing a new one.
-
5
Do not store a shift as a day plus two clock times. Store real start and end instants with a zone, or overnight shifts and clock-change weeks will be wrong in ways nobody notices until someone is not there.
Edge cases it handles
8
Edge cases it handles
8- Two shifts overlapping for the same person must be flagged at the moment of the edit, with both shifts named. Discovering the clash on the day means one of them goes uncovered.
- Hours below the required coverage level must be marked clearly on the grid, and the required level should be settable per day part rather than as a single number for the whole week.
- An overnight shift belongs to the day it started on and must be drawn as one continuous block spanning midnight, not as two fragments on separate days.
- Published shifts stay exactly as staff last saw them while a draft of the same week is edited, including through a partial or abandoned editing session.
- On publish, notify only the people whose own shifts actually changed, and tell them what changed. A broadcast to the whole team on every publish gets muted, including the week it mattered.
- A week that crosses a daylight-saving change contains a day of twenty-three or twenty-five hours. The grid must render it and shift durations must be computed from instants.
- Deleting or deactivating a staff member must not silently erase their published shifts; surface the resulting coverage gap instead.
- The grid must remain usable on a phone for someone checking their own shifts, even if editing stays a desktop task.
Definition of done
9
Definition of done
9- A weekly grid shows every staff member's shifts with draft and published states kept separate.
- Overlapping shifts for one person are flagged during editing.
- Coverage below the required level is visible on the grid without opening each shift.
- Overnight shifts render as one continuous block on their starting day.
- Publishing notifies only the staff whose own shifts changed, and says what changed.
- Shift times are stored as instants with a zone and survive daylight-saving weeks.
- Repeating shift patterns use the app's existing recurrence builder.
- 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
Cache Invalidation Controls
Cache Invalidation Controls
Clear stale cached data without flushing everything or restarting.
What it does
An operator control that invalidates cache entries by namespace, tenant, or resource — scoped, propagated across processes, and recorded.
How it works
- 1 Define named invalidation scopes rather than free-text key entry. An operator picks a namespace, a tenant, or a specific resource; they do not type raw cache keys.
- 2 Enforce tenancy on every scope. One workspace's operator must be structurally incapable of clearing another workspace's entries — check the scope against their permissions before building the key pattern, not after.
- 3 Propagate invalidation to every process and region that holds a copy. In-process and edge caches will not hear about a change made in a shared store unless you tell them, and a clear that only affects one server is worse than no clear because it looks like it worked.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/cache-invalidation-controls
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.