E-commerce

WishlistPanel

Saved items panel with add-to-cart, remove, and out-of-stock states.

Quick Preview

Wishlist 4

👕

Classic Hoodie

฿1,290฿1,790

👟

Running Shoes

฿3,490

🎒

Canvas Backpack

฿890฿1,200

Out of stock

⌚

Minimal Watch

฿4,990

Installation

npm install lucide-react

// Copy component from
src/components/ecommerce/WishlistPanel.tsx

Usage

import WishlistPanel from '@/components/ecommerce/WishlistPanel'

// Self-contained panel — manages its own saved items state
<WishlistPanel />

Prompt Preview

Copy a prompt that recreates this UI

Paste this into your AI coding assistant to generate code that closely matches the reference, including color, size, shape, typography, spacing, and polish.

Copy-ready AI prompt

Starts from the current visual reference and project constraints.

Build a ecommerce component named WishlistPanel in React/Next.js.
Goal: recreate the same overall UI and behavior as the WishlistPanel reference from a component gallery.
What it needs to communicate: Saved items panel with add-to-cart, remove, and out-of-stock states..

Project constraints:
- Use Next.js 16.2.6 with the App Router, React 19, TypeScript strict mode, and Tailwind CSS v4.
- Do not create a tailwind.config.js file. Use Tailwind v4 utilities and CSS variables where design tokens are needed.
- If you are implementing this inside the same project, use the Prompt font via next/font/google. If not, use the closest equivalent typeface.
- Return production-ready code with imports, responsive behavior, keyboard accessibility, and polished empty, hover, focus, active, and disabled states where relevant.
- Match the reference closely: color palette, spacing scale, border radius, shadows, icon scale, typography hierarchy, and motion timing.

Component-specific expectations:
- Prioritize conversion-oriented hierarchy, product clarity, and strong CTA styling.
- Handle price, status, quantity, and selection states cleanly.
- Avoid unnecessary dependencies unless the behavior truly requires them.
- No explicit color literals were found in the examples. Match the live reference and the project accent color when appropriate.

Props to support:
- className: string — Additional CSS classes

Reference usage patterns:
- No examples were documented. Infer a sensible default presentation and one richer usage example.

Feature expectations:
- Remove items
- Add to cart
- Out-of-stock badge
- Empty state

Output requirements:
- Return complete code, not pseudocode.
- Include all necessary imports and helper types.
- Keep the implementation accessible, responsive, and visually finished.
- Match the reference for color, size, shape, typography, spacing, and interaction states as closely as possible.
- If multiple files are needed, organize them cleanly and explain the file structure briefly.

Tweak only product-specific copy or data after the first generation pass.

Props

Prop	Type	Default	Description
`className`	`string`	-	Additional CSS classes