Duplicate File Detection
Stop storing the same file over and over.
What it adds
Content-hash deduplication of uploads within an ownership boundary, so identical bytes are stored once but tracked per record.
What your agent is told to do
6
What your agent is told to do
6-
1
Hash the stored bytes on the server with a strong content hash, streaming rather than loading the whole file into memory.
-
2
Never trust a filename, a size, or a client-supplied checksum as evidence of sameness. A client that can assert a hash can claim someone else's file.
-
3
Deduplicate only within an explicit boundary — the tenant, the workspace, or the single owner. Sharing bytes across tenants leaks the fact that another tenant holds an identical file.
-
4
Keep metadata separate from storage: filename, caption, uploader, timestamps, and permissions belong to each reference, not to the shared object.
-
5
Reference-count the stored object and only delete the bytes when the last reference goes.
-
6
Do NOT tell an uploader 'this file already exists' when the existing copy belongs to someone they cannot see. Deduplicate silently instead.
Edge cases it handles
7
Edge cases it handles
7- Two uploads of the same file arriving at once must not both create the object — make the write conditional or unique-indexed.
- A hash collision check that compares only hashes is fine for a modern hash; a check that compares only file size is not.
- Deleting one record's copy must not remove the bytes another record still points at.
- Files that are transformed after upload (compressed, watermarked) change hash — decide whether you dedupe the original, the derivative, or both.
- Retention and legal-hold rules apply per reference; one tenant's deletion request cannot be satisfied by leaving shared bytes in place unless the boundary makes that lawful.
- Encrypted-at-rest storage with per-tenant keys makes cross-record deduplication impossible; check before assuming it works.
- Re-uploading a file the user deleted must work normally, not resurrect the old record's metadata.
Definition of done
8
Definition of done
8- Hashes are computed server-side from the stored bytes, streamed.
- Client-supplied hashes are never trusted for deduplication decisions.
- Deduplication never crosses the defined ownership boundary.
- Each reference keeps its own filename, metadata, and permissions.
- Stored bytes are removed only when the last reference is deleted.
- Concurrent identical uploads produce exactly one stored object.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
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.