v0 prompt for an ecommerce landing page

Build a single-product landing page for a project management SaaS, selling to engineering managers at startups. Compose it in v0 from discrete components — Gallery, BuyBox, BenefitBlocks, SpecsAccordion, ReviewWall, GuaranteeStrip, StickyBuyBar — using Tailwind and shadcn/ui, so each piece can be revised independently.

Layout, top to bottom:
1. Above the fold: Gallery on the left (main image with 4 thumbnails, becoming a shadcn Carousel on mobile) and BuyBox on the right — product name, one-line value claim, star rating with review count, price with any compare-at price, quantity select, the buy button, and directly beneath it a trust row: shipping time, free-returns window, secure-checkout note.
2. BenefitBlocks — 3 alternating media/text bands; every headline is written as an outcome the buyer gets, never a feature name, with 2 supporting sentences.
3. SpecsAccordion — a shadcn Accordion with 4 panels: specifications table, what's included, materials and care, shipping and returns detail.
4. ReviewWall — overall score, a star histogram, then 6 review cards (name, verified tag, rating, a 2–3 sentence quote), with a filter by star rating.
5. GuaranteeStrip — money-back period, warranty length, and support contact in one compact band.
6. StickyBuyBar — appears only after the BuyBox scrolls out of view: thumbnail, name, price, buy button; hides again when the footer is visible.

Visual direction:
Minimal dark style. Near-black canvas (#0A0A0B) with one elevated surface tone (#141416) for cards — never more than two surface steps. Hairline borders (1px, white at 8% opacity) instead of shadows; if a shadow is unavoidable use 0 1px 2px rgba(0,0,0,0.4) and nothing softer. Text in exactly three steps: white at 92% for headings, 60% for body, 40% for captions. Generous negative space — section padding at least 120px on desktop, 64px on mobile. The accent color appears only on interactive elements and one hero highlight, nowhere else.

Palette: a strict neutral ramp (white, #F5F5F5, #E5E5E5, #737373, #171717) carries the entire interface; pick one accent and use it only for primary CTAs, active states, and a single hero highlight. If the accent appears more than five times per viewport it stops being an accent. Keep semantic colors (success, error) desaturated so the accent stays in charge.
Typography: one geometric sans (a Futura/Poppins-class face) at three weights maximum (400/500/700). Scale: 64-88px hero, 32px section heads, 18px lede, 16px body, 13px caps labels with 0.08em tracking. Tight headline leading (1.05-1.1), relaxed body (1.6). Let the geometry carry the personality — no italics; weight and size do all hierarchy.
Motion: none. Zero scroll animations, zero entrance effects — the page is fully composed the instant it paints. Spend the motion budget on input feedback instead: 120-150ms ease-out color and transform transitions on hover and press states only. Hold this constraint absolutely; it is a statement, not an omission.

Spacing and mobile:
- Band padding 80px desktop, 48px mobile; the gallery-to-BuyBox gap fixed at 48px.
- On mobile the BuyBox follows the gallery, benefit bands stack text-first, and the sticky bar condenses to price plus button.

The buy action everywhere is "start a free trial" — the BuyBox button, the sticky bar, and once after the ReviewWall. Derive benefit headlines from what a project management SaaS changes for the buyer.

After building, check that: the sticky bar appears only after the BuyBox leaves the viewport; all three "start a free trial" buttons are present; the trust row sits directly under the primary button; all four accordion panels are populated; mobile renders the gallery as a swipeable carousel.