Draft and Publish States
Let users prepare changes privately before anyone else sees them.
What it adds
An explicit draft/published status with server-enforced access, a defined edit model, and cache invalidation on every transition.
What your agent is told to do
5
What your agent is told to do
5-
1
Add an explicit status to the content model and enforce it in the query layer. Public reads must be unable to return a draft even when the ID is guessed; a hidden link is not access control.
-
2
Decide and document one edit model: either edits to published content go live immediately, or edits create a separate draft revision that must be published. Pick one and apply it everywhere — a mixed model is where data gets lost.
-
3
Support the full set of transitions, not just publish: unpublish back to draft, republish, discard a draft without touching the live version, and delete.
-
4
Invalidate every cache the moment status changes — page cache, CDN, sitemap, feeds, search index. A published record that a stale cache still serves as missing is the most common bug here.
-
5
Allow a shareable preview to be pinned to a specific unpublished version, so a reviewer sees the version that was sent, not whatever the draft has become since. The token mechanics — expiry, revocation, unguessability, noindex — are owned by Signed Share Links; use that rather than minting your own tokens.
Edge cases it handles
6
Edge cases it handles
6- A published record that is unpublished must disappear from listings, search, sitemaps, and feeds — not just from its own page.
- A URL that was public and is now a draft needs a deliberate answer: 404, 410, or a signed-in-only view. Decide it, do not let the framework decide.
- Two editors working a draft at once must not silently overwrite each other; detect the conflict at save time.
- Publishing must validate that required fields are present. Draft state is exactly where incomplete records live.
- A draft revision of a deleted parent record must be cleaned up, not left readable.
- Scheduled transitions to a future time are owned by Scheduled Publishing; this feature owns only the status model those jobs act on.
Definition of done
8
Definition of done
8- Draft content is unreachable by unauthorised users even with a direct ID or URL.
- The edit model is one documented rule applied consistently across all content types.
- Unpublish, republish, and discard-draft all work and are reflected everywhere the content appeared.
- Every status change invalidates page, CDN, feed, sitemap, and search-index caches.
- Publishing enforces required-field validation.
- A preview can be pinned to a specific unpublished version, using the existing signed-link mechanism.
- 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.