Attachment Gallery
Make attached files browsable instead of a list of filenames.
What it adds
A gallery surface for the files attached to a record, with per-type previews, stable ordering, captions, and per-item permissions.
What your agent is told to do
6
What your agent is told to do
6-
1
Render every attachment as a tile with a type-appropriate preview: a thumbnail for images, a first-page or icon preview for documents, a duration badge for media.
-
2
Define a fallback for every type you do not preview, showing filename, size, and type. An unrecognised file must still be identifiable.
-
3
Only preview formats you have decided are safe to render inline. Do not inline arbitrary HTML or SVG from user uploads — it executes in your origin.
-
4
Give attachments an explicit order value rather than relying on creation time, and let the user reorder and caption them.
-
5
Check download permission per item at request time, not once for the whole record.
-
6
Do NOT build an upload control here — that is owned by File Upload. The fullscreen image viewer is owned by Image Lightbox, and authorized delivery of the file bytes is owned by Secure File Downloads. Extend those rather than duplicating them.
Edge cases it handles
7
Edge cases it handles
7- An attachment still processing must show a processing tile, not a broken thumbnail.
- A file deleted while the gallery is open must fail cleanly on click, not 500.
- A quarantined or scan-failed file must be visible as blocked and must not be previewable or downloadable.
- Two people reordering at once must not silently overwrite each other — resolve on the server and refresh the client's order.
- A caption is user text rendered next to a file; escape it.
- A gallery with two hundred attachments must paginate or lazy-load rather than requesting two hundred thumbnails at once.
- Thumbnail generation failure must degrade to the fallback tile, not an empty box.
Definition of done
8
Definition of done
8- Every attachment renders either a real preview or a labelled fallback.
- Processing, deleted, failed, and quarantined states each have their own visible treatment.
- Download permission is enforced per item, not per record.
- Order and captions survive concurrent edits without silent loss.
- No user-supplied file is rendered inline in a way that can execute script.
- Upload, fullscreen viewing, and file delivery are deferred to their owning features.
- 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.