Image Compression
Shrink uploaded images before they slow down every page that shows them.
What it adds
Automatic resizing and re-encoding of uploaded images, with orientation, transparency, and metadata handled correctly.
What your agent is told to do
6
What your agent is told to do
6-
1
Decide the maximum stored dimensions and target quality once, and apply them to every upload path in the app.
-
2
Read orientation metadata and rotate the pixels before resizing, then drop the orientation tag. Resizing first bakes in a sideways image.
-
3
Choose the output format by content: keep transparency where the source has it, and do not convert a transparent PNG to JPEG.
-
4
Compress from the original bytes every time. Never re-compress an already-compressed derivative — each pass loses quality permanently.
-
5
Strip EXIF by default, including GPS coordinates. A holiday photo uploaded as an avatar should not publish someone's home address.
-
6
Do NOT compress on the client only. A client-side pass is a bandwidth optimisation; the server must still enforce the limits because the client can be bypassed.
Edge cases it handles
7
Edge cases it handles
7- Animated GIFs and animated WebP must keep their frames or be rejected explicitly — a silent first-frame-only conversion looks like a bug.
- A file claiming to be an image must be validated by its actual content, not its extension or declared type.
- Enormous dimensions can exhaust memory during decode even when the file is small. Cap decoded pixel count, not just file size.
- An image already smaller than the target must be left alone rather than re-encoded larger.
- Colour profiles matter: dropping an embedded profile shifts colours visibly on wide-gamut screens.
- Some uploads must keep their originals — proof-of-purchase photos, design source files. Define which, and store the original alongside.
- A failed compression must not lose the upload; fall back to storing the original and log it.
Definition of done
8
Definition of done
8- Uploaded images are stored within the defined dimension and size limits.
- Rotated photos display upright without client-side correction.
- Transparency is preserved where the source had it.
- Re-uploading a processed image does not degrade it further.
- GPS and other EXIF metadata is removed from images served publicly.
- Server-side limits hold even when the client-side pass is skipped.
- 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.