Duplicate Record
Start from something that already works instead of rebuilding it.
What it adds
A duplicate action on records that copies the content worth keeping and deliberately drops everything that must not be shared.
What your agent is told to do
6
What your agent is told to do
6-
1
Define the copy rules per record type explicitly. A blanket field copy will carry over ids, timestamps, audit trails, ownership, and secrets — all of which must be reset or excluded.
-
2
Never copy API keys, tokens, credentials, or anything encrypted at rest. A copy is a new secret or no secret; it is never the same secret.
-
3
Generate a non-conflicting name and slug, and show the user what it will be before they confirm.
-
4
State clearly in the confirmation what is and is not included — child records, attachments, comments, permissions, schedules. Ambiguity here produces support tickets.
-
5
Run the duplication in a single transaction. A half-copied record is worse than a failed copy.
-
6
Do not silently re-activate anything: a copy of a live, scheduled, or published record must start inactive and draft.
Edge cases it handles
6
Edge cases it handles
6- Deep hierarchies must have a documented depth limit, or one duplicate can clone half the database.
- Copying counters, view counts, analytics, and history is almost never wanted — reset them.
- Attachments should be referenced or re-uploaded by an explicit rule; deleting the original must not break the copy.
- The duplicate must respect quotas — if the plan limit is reached, refuse before writing anything.
- Cross-workspace duplication must re-map or drop references to users and objects that do not exist in the destination.
- A record the user may view but not create in that container must not be duplicable.
Definition of done
8
Definition of done
8- Ids, audit fields, ownership, and secrets are never carried into the copy.
- The generated name and slug do not collide with an existing record.
- The confirmation states exactly what is included and excluded.
- Duplication is atomic — a failure leaves nothing behind.
- Copies start in a draft or inactive state.
- Plan and permission limits are enforced before any write.
- 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.