Before and After Slider
Let people drag a handle to compare two versions of the same image.
What it adds
A pair of images stacked in one frame with a draggable divider that reveals more of one and less of the other.
What your agent is told to do
5
What your agent is told to do
5-
1
Fix the frame using the app's existing aspect-ratio handling and render both images inside it, so the layout never depends on when either image finishes loading.
-
2
Make the handle a real focusable control that moves with arrow keys in small steps and jumps to the ends with home and end, with the current position exposed as a value rather than only as a visual.
-
3
Hold the after image hidden until both images have decoded, then reveal them together. A comparison that shows one image alone for a moment reads as a broken layout.
-
4
Clamp the divider to the frame bounds and keep tracking the pointer after it leaves the frame, releasing cleanly when the button is released anywhere on the page.
-
5
Do not require the caller to supply pre-composited images. Accept two independent image references and let the component do the clipping, so the same pair can be reused elsewhere in the app.
Edge cases it handles
7
Edge cases it handles
7- Two images of different dimensions will not line up, and the comparison becomes meaningless. Either reject the mismatch at the point the pair is configured or letterbox both to a shared frame using one consistent rule.
- A handle that only responds to dragging excludes keyboard users entirely. Arrow keys must move the divider in fine steps, with larger jumps available, and the control must be reachable by tab.
- Dragging past the edge of the frame must clamp the divider at zero or one hundred percent rather than producing a negative offset or letting the images detach from the frame.
- If the second image loads after the first, it will flash into place under the divider. Wait for both to decode before revealing, and show a placeholder at the reserved size until then.
- A vertical finger movement that starts on the handle must let the page scroll instead of being captured as a drag. Only take over the gesture once horizontal movement dominates.
- Both images need their own alt text, and the labels for which side is before and which is after must be visible rather than assumed from left and right.
- On a narrow screen the handle must stay large enough to grab with a thumb, which usually means a wider hit area than the visible divider line.
Definition of done
9
Definition of done
9- The frame is sized before either image loads and never shifts.
- Mismatched dimensions are rejected or letterboxed by one consistent rule.
- The handle is keyboard operable and exposes its position accessibly.
- Dragging beyond the frame clamps cleanly and releases correctly.
- Neither image is visible alone before both have loaded.
- Vertical page scrolling still works when a touch gesture starts on the handle.
- Both images carry alt text and the sides are labelled.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Picture-in-Picture Mode
Picture-in-Picture Mode
Let viewers pop a video into a floating window and keep using the rest of the app.
What it does
A control on the video player that hands the video to the browser's floating always-on-top window.
How it works
- 1 Add the control to the app's existing video player rather than building a separate popped-out player. Two players competing over the same element is the main way this feature goes wrong.
- 2 Keep the app in sync with the floating window in both directions. Pausing, seeking, or changing volume from the floating window must update the in-page player, and closing the floating window must return playback to the page at the same position.
- 3 Decide explicitly what happens when the user navigates away from the page that owns the video. Either keep the floating window alive and reconnect when they return, or end it cleanly, but do not leave a floating window playing a video the app has forgotten about.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/picture-in-picture-mode
Audio Waveform Scrubber
Audio Waveform Scrubber
Show the shape of a track so listeners can see the quiet and loud parts and click to them.
What it does
A waveform rendered from precomputed amplitude data, doubling as the seek control on the audio player.
How it works
- 1 Compute the amplitude data on the server when the file is first stored, and serve it as a small dataset the page can draw. Do not decode the audio in the browser to build the waveform.
- 2 Replace the plain scrub bar in the app's existing Audio Player with this surface rather than adding a second seek control beside it.
- 3 Draw played and unplayed regions distinctly, and keep the playhead position exact under click, drag, and keyboard seeking on the same surface.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/audio-waveform-scrubber
Hover Video Preview
Hover Video Preview
Hovering a video card plays a short silent clip so people see what it is before clicking.
What it does
A silent, short-loop preview that plays inside a video card on deliberate hover and returns to the poster on exit.
How it works
- 1 Generate a short, low-resolution, silent preview clip during video processing and store it alongside the poster frame. Do not play the full source file behind the card.
- 2 Require a deliberate hover before doing anything. Wait several hundred milliseconds after the pointer settles, then load, so a cursor crossing a grid does not fire a dozen requests.
- 3 Give touch devices an explicit preview control on the card, since hover does not exist there. A long-press or a small preview button is fine; silently doing nothing on mobile is not.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/hover-video-preview
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.