Image Carousel
Let customers page through a set of images with arrows, dots, and swipe.
What it adds
A horizontally paged row of images with previous and next controls, position indicators, optional autoplay, and touch swiping.
What your agent is told to do
5
What your agent is told to do
5-
1
Reserve the slide dimensions before any image loads, using the app's existing aspect-ratio handling if it has one, so the page does not jump as each image arrives.
-
2
If the app already has an image lightbox, wire the carousel into it rather than building a second full-screen viewer. Tapping a slide should open the existing lightbox at the matching index.
-
3
Make the carousel operable without a pointer: arrow keys move between slides, the dots are real focusable controls, and the current position is announced rather than conveyed only by a filled dot.
-
4
Treat autoplay as an interruption the user is allowed to stop. Pause it on hover, on focus anywhere inside the carousel, when the tab is hidden, and permanently when reduced motion is preferred, and provide a visible pause control.
-
5
Do not load every slide upfront. Load the visible slide and the next one, defer the rest, and require alt text on each image rather than shipping a row of unlabelled pictures.
Edge cases it handles
8
Edge cases it handles
8- Autoplay that keeps moving while someone is reading or interacting is hostile. Pause on hover, on keyboard focus, and when a reduced-motion preference is set, and do not resume automatically after a manual interaction.
- Keyboard navigation and swiping must drive the same index and the same state. If arrow keys move a separate pointer from the touch gesture, the dots and the visible slide will disagree.
- A carousel of one image should not show arrows or dots at all. Detect the single-slide case and render a plain image, and handle the zero-slide case with the app's empty state rather than an empty frame.
- Wrapping from the last slide back to the first must not yank the page scroll position or animate through every slide in between. Move directly and keep the surrounding page still.
- Loading every slide on first paint wastes bandwidth on images most people never see. Defer offscreen slides but preload the immediate next one so paging forward is not a blank frame.
- Images that fail to load must leave the slide sized and labelled rather than collapsing the carousel height, and the alt text must still be available.
- Slides of differing aspect ratios will make the carousel resize on every page. Fix the frame and fit images inside it consistently.
- A horizontal swipe must not swallow vertical page scrolling. Only capture the gesture once horizontal intent is clear.
Definition of done
9
Definition of done
9- Slides are sized before images load and the page does not shift.
- Arrows, dots, keyboard, and swipe all move the same index consistently.
- Autoplay pauses on hover, focus, and hidden tabs, and is disabled under reduced motion.
- A single-slide carousel hides its arrows and dots.
- Offscreen slides are deferred while the next slide is preloaded.
- Every image has alt text and the current position is announced accessibly.
- Tapping a slide opens the app's existing lightbox rather than a second viewer.
- 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.