Product Quick View
Let shoppers preview a product and add it to the cart without leaving the listing.
What it adds
An overlay panel opened from a product card showing images, variants, price, and an add-to-cart control.
What your agent is told to do
5
What your agent is told to do
5-
1
Show only what decides a purchase: images, price, variant choices, stock status, and the add-to-cart control. Everything longer belongs on the full product page, and a link to it must always be present.
-
2
Build the panel on the app's existing modal or drawer behaviour rather than introducing a second overlay implementation. Focus trapping, escape handling, and scroll locking are already solved there.
-
3
Fetch the product detail when the panel opens and show a skeleton matching the panel's real layout, so the overlay never appears empty.
-
4
Reuse the app's existing Image Lightbox for full-size image viewing instead of nesting a second image viewer inside the panel.
-
5
Do not make quick view the only path to the product. Every card must still link to the real page, and that page must remain crawlable and shareable.
Edge cases it handles
8
Edge cases it handles
8- Closing the panel must return focus to the card that opened it and leave the listing at the same scroll position. Dumping the shopper at the top of the page after a close is the failure people notice most.
- The listing behind the panel must not scroll underneath it, and locking that scroll must not shift the layout when the scrollbar disappears.
- Details load lazily, so a slow request needs a skeleton with reserved dimensions and a failure needs a message with a link to the full page rather than an empty panel that stays empty.
- On small screens an overlay squeezing a gallery, variant picker, and buy button into a phone viewport is worse than the real thing. Navigate to the full product page instead of opening the panel.
- A variant chosen in the preview must carry through when the shopper opens the full product page, otherwise the selection is silently lost and they choose again.
- Adding to cart from the panel must update the cart indicator and either confirm in place or close deliberately. Doing nothing visible reads as a failed click and produces duplicate additions.
- Out-of-stock and unavailable variants must be reflected in the panel with the add control disabled, not discovered at checkout.
- Opening a quick view must not push a history entry that makes the back button close the panel and the second press leave the site unpredictably. Decide the behaviour and apply it consistently.
Definition of done
9
Definition of done
9- The panel opens from a card with product images, price, variants, and add to cart.
- Closing restores focus to the originating card and the listing's scroll position.
- The page behind the panel does not scroll or shift while it is open.
- A loading panel shows a shape-matched skeleton and a failed load offers the full product page.
- Small screens go to the full product page instead of opening the overlay.
- A variant selected in the preview is preselected on the full product page.
- The panel reuses the app's existing modal and lightbox behaviour rather than duplicating it.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Beautiful Empty States
Beautiful Empty States
Replace blank screens with useful, contextual empty states.
What it does
Every list, table, and dashboard in your app has a "nothing here yet" state. Most
apps ship a blank rectangle — and it is often the very first thing a new user sees.
An empty state should say what belongs here, why it is empty, and what to do next.
How it works
- 1 Inventory the empty cases first. List every collection view in the app and
- 2 Distinguish the three kinds of empty. They are not the same, and must not
- 3 Build one reusable empty-state component from the existing design system,
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/beautiful-empty-states
Opening Hours Display
Opening Hours Display
Say whether you are open right now and when you next open.
What it does
A live open or closed state alongside the weekly hours, with holiday closures folded in.
How it works
- 1 Lead with the current state in plain words and follow it with the next transition: open until a time, or closed until a day and time. The weekly table is supporting detail, not the headline.
- 2 Store hours as intervals against the business's own zone, and keep holiday and one-off closures as overrides that win over the regular week rather than as edits to it.
- 3 Compute the state on the server for the first render so the page does not briefly claim the wrong thing, then let the page update itself as the clock crosses a boundary without a reload.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/opening-hours-display
Dark Mode
Dark Mode
Add a dark theme that respects the system preference and the user's choice.
What it does
A complete dark theme, defaulting to the operating system preference and overridable by the user.
How it works
- 1 Audit every colour in the app first and report where they are defined. If colours are hardcoded throughout, extract them into tokens before anything else — that refactor is the bulk of this work.
- 2 Define a dark palette against those tokens. Do not simply invert the light theme.
- 3 Default to the system preference via prefers-color-scheme, and let the user override it.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/dark-mode
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.