Image gallery + variant selector + buy actions + tabbed detail — the canonical PDP.
Two-column product detail page. Image gallery on the left, product info + variant selector + add-to-cart on the right. Underneath, tabbed sections for description, specifications, and reviews. The canonical product detail surface for any catalog flow.
Each section pre-wired with the right CleenUI primitives. Swap, remove, or extend any of them — the template is a starting point, not a constraint.
Left column — primary image with thumbnail strip.
Right column — title, short description, price.
Size, color, quantity controls.
Primary Add-to-cart + secondary Wishlist or Compare.
Description / Specifications / Reviews — under the fold.
All of these are in the catalog — the Builder skill imports them automatically. Each chip links to that component's page.
When the Builder skill scaffolds this template for you, these are the fields it asks about — or infers from your prompt.
Ask your AI agent to scaffold this template in your project — the Builder skill knows the Product Details layout and the components it uses.
Two paths to your first component. Pick the one that fits how your team builds.
One prompt to your AI tool. The Setup skill handles dependencies, design tokens, build config, and component registration — all without leaving your editor.
The classic flow. Install the package, import the styles, drop in your first component. No agents required — same end result.