Scheduled Publishing
Publish or unpublish content automatically at a chosen future time.
What it adds
Durable, idempotent scheduled transitions that survive worker downtime and stay correct when the content or the author's permissions change.
What your agent is told to do
5
What your agent is told to do
5-
1
Persist the schedule on the record itself, not only in a job queue. A queue that is drained, migrated, or lost must be recoverable by re-reading the pending schedules from the database.
-
2
Make the transition job idempotent and keyed to the intended run. Running it twice, or late, must produce the same result as running it once on time.
-
3
On worker recovery, process overdue schedules rather than skipping them — but cap how far back you will reach, and report anything published significantly late instead of doing it silently.
-
4
Define what happens when the content is edited after being scheduled: publish whatever is current at the moment of firing, or publish the version that was scheduled. Say which, and show the user that rule in the scheduling UI.
-
5
Do not build your own status model or your own time-zone picker. The draft/published states and their access rules are owned by Draft and Publish States; time-zone selection and DST handling are owned by Time Zone-Aware Scheduling. Extend both rather than adding a second one.
Edge cases it handles
6
Edge cases it handles
6- A schedule must be cancellable, and cancelling must remove the pending job as well as the field on the record.
- If the author loses permission to publish before the fire time, the schedule must not run on their behalf — fail it and notify someone.
- Manually publishing before the scheduled time must clear the schedule, not leave a job that republishes later.
- Deleting or archiving the record must cancel every schedule attached to it.
- A scheduled unpublish and a scheduled publish on the same record must resolve in a defined order, not by whichever job wins.
- Show the pending time in the user's own zone alongside the stored intent, and warn when a scheduled time has already passed.
Definition of done
8
Definition of done
8- Pending schedules are stored on the record and can be rebuilt after a queue loss.
- Running the transition job twice produces the same result as running it once.
- Overdue schedules are processed on recovery within a defined window and reported when late.
- The changed-content rule is documented and visible where users schedule.
- Cancellation, manual publish, permission loss, and deletion all invalidate the schedule.
- Status model and time-zone handling reuse the existing features rather than duplicating them.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Weather Widget
Weather Widget
Show current conditions and a short forecast for a place your users care about.
What it does
A compact widget showing current conditions and a few days of forecast for a chosen location.
How it works
- 1 Add this as a tile in the app's existing Customizable Dashboard Widgets rather than as a fixed element bolted into a layout, so users who do not want it can remove it.
- 2 Fetch the forecast on the server on a schedule and serve the widget from the app's own cache. Calling the weather source from every visitor's browser leaks the credential and multiplies the request count by your traffic.
- 3 Show the observation time alongside the reading, and reuse the app's Stale Data Indicator conventions so ageing weather looks the same as any other ageing data in the product.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/weather-widget
Location Map Block
Location Map Block
Put an interactive map on a page showing one location or a whole list of them.
What it does
A reusable map block rendering one or many pinned locations, with a static fallback and a text address alternative.
How it works
- 1 The app already has Mapbox Geocoding and Google Places Address Lookup. Turn addresses into coordinates through the existing integration and store the result on the record; do not add a second geocoding path for this block.
- 2 Make the block take either a single location or a collection, and render the same component for both. A one-pin map is a collection of one, not a separate feature.
- 3 Reserve the block's height before the map initialises so the surrounding page does not jump when tiles arrive. The placeholder should occupy exactly the space the map will fill.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/location-map-block
Record Merge
Record Merge
Combine two duplicate records into one without losing anything attached.
What it does
A merge flow that picks a surviving value per field, reparents all related data, redirects old references, and can be audited afterwards.
How it works
- 1 Show the two records side by side, field by field, and require an explicit survivor for every field where they differ. Do not default to 'newest wins' silently; the user is merging because they know which one is right.
- 2 Reparent every related object — children, comments, attachments, activity, links, memberships — onto the survivor in a single transaction. A half-finished merge is worse than two duplicates.
- 3 Detect relationships that would become duplicates after reparenting (the same person as a member of both records, the same tag applied twice) and collapse them rather than violating a uniqueness constraint mid-merge.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/record-merge
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.