Product Collection
Sticky filter sidebar, sort toolbar and product grid — with the facets dropped rather than stacked on mobile, so a shopping page does not open as a form.
Gallery, sticky buy box, details accordion and reviews — ordered by what a shopper needs before they can decide.
app/product-detail-page.tsxnpx hoverlab add product-detail-page
Or over MCP, from your editor's agent — no account needed.
Free to read, copy and install, for personal and non-commercial projects. Shipping it in client work or a paid product needs Pro ($79 once). The source lands in your repo and stops being ours — no attribution, nothing to upgrade.
Quantity
A midweight crew neck knitted from extra-fine merino, with a clean set-in sleeve and ribbed trims that hold their shape through a season of wear.
Cut slightly relaxed through the body so it layers over a shirt without pulling. Fully fashioned, which means the panels are knitted to shape rather than cut from a sheet — it costs more to make and it does not lose its line at the shoulder.
Knitted in Scotland from mulesing-free merino.
Standard delivery is free on orders over £50 and arrives in 2–4 working days. Next-day is £6.95 if you order before 2pm.
Thirty days from delivery, free, in any condition you would accept yourself. Print the label from your order page or hand it to any collection point.
Sale items included — we have never understood shops that exclude them.
4.5/5
218 reviews
94% would recommend
I bought this expecting to return it and it has become the thing I reach for three days a week. The knit is dense without being heavy, and after four washes there is no pilling at the cuffs where I would expect it first. Sizing is honest — I am usually a medium and the medium fits with room for a shirt underneath.
The stone reads much warmer in person than on screen — closer to a light camel. Lovely sweater, just not the colour I was picturing.
No complaints about the material at all. The body is about an inch longer than I expected, which is fine untucked but worth knowing if you are between sizes.
Two in stone, one in navy. They hold their shape better than anything else I own at twice the price.
The real page, rendered in your current theme — every section below is a live block, not a screenshot.
Only want one section? Open it and copy that block instead — browse Product Detail.
Want the whole project rather than this one screen? A template ships every route, the theme tokens and the layout.
/**
* A product detail screen.
*
* Ordered by what a shopper needs before they can decide: see it, choose a
* size and price it, then read the detail, then check whether other people
* regretted it.
*
* The gallery and buy box are a two-column grid on desktop with the buy box
* `sticky`, so the price and Add to bag stay on screen while the images and
* the description scroll. On a long product page that is the difference
* between a purchase and a scroll back to the top.
*
* In a real project this file lives at `app/products/[slug]/page.tsx` and
* takes `params` — fetch the product there and pass it down as props. Every
* block below already accepts the fields it needs.
*/
import * as React from 'react'
import { ProductGallery } from '@/components/product-gallery'
import { ProductBuyBox } from '@/components/product-buy-box'
import { ProductInfoAccordion } from '@/components/product-info-accordion'
import { ProductReviewSummary } from '@/components/product-review-summary'
import { ReviewList } from '@/components/review-list'
import { ProductRail } from '@/components/product-rail'
export default function ProductDetailPage() {
return (
<main className="min-h-screen bg-background text-foreground">
<div className="mx-auto w-full max-w-6xl px-4 py-10 sm:px-6 lg:px-8">
<nav aria-label="Breadcrumb" className="mb-6 text-sm text-muted-foreground">
<ol className="flex flex-wrap items-center gap-1.5">
<li>
<a href="/" className="transition-colors hover:text-foreground">
Shop
</a>
</li>
<li aria-hidden>/</li>
<li>
<a href="/knitwear" className="transition-colors hover:text-foreground">
Knitwear
</a>
</li>
<li aria-hidden>/</li>
<li aria-current="page" className="text-foreground">
Merino Crew Sweater
</li>
</ol>
</nav>
<div className="grid grid-cols-1 gap-10 lg:grid-cols-2 lg:gap-14">
<ProductGallery />
{/* Sticky, so price and Add to bag survive a long scroll. */}
<div className="min-w-0 lg:sticky lg:top-6 lg:self-start">
<ProductBuyBox />
</div>
</div>
<div className="mt-14">
<ProductInfoAccordion />
</div>
<div className="mt-14 space-y-8">
<ProductReviewSummary />
<ReviewList />
</div>
<div className="mt-16 border-t border-border/60 pt-10">
<ProductRail viewAllHref="/knitwear" />
</div>
</div>
</main>
)
}
components/ — each block page has its own copy button.app/product-detail-page.tsx. The imports already point at @/components/…, so they resolve with no edits.The component, its props, the design tokens it expects and the command that installs it — as one prompt. Paste it into Claude, Cursor, v0 or ChatGPT and what they build around it will match the rest of the catalog instead of inventing its own system.
Sticky filter sidebar, sort toolbar and product grid — with the facets dropped rather than stacked on mobile, so a shopping page does not open as a form.
Editable lines beside a sticky summary, so the total and the checkout button survive a scroll through four quantity changes.
Address and payment with the site navigation stripped and the order summary moved above the form on mobile — both aimed squarely at completion rate.
The post-purchase screen, with navigation restored and a rail that shows what to buy next rather than what was just bought.
Order history in the settings shell rather than a second sidebar layout — an account area and a settings area are the same shape.
The page between a listing and a product detail, with the two questions a comparison table alone cannot answer: will it fit, and can I actually have it.
Checkout for the buyer who will not fill in a form: wallet buttons above the fields, and the address a wallet returns shown and changeable before the charge rather than after it.
For the customer with an order number and no account — a lookup, an arrival range rather than a promised date, and the review form where the "how did we do" email actually lands.