Medusa — Product details

CommerceSee it livenext.medusajs.com

A product detail screen separates descriptive content, large photography, and the purchase action.

Medusa — Product details — captured interface — Viewport capture · opening screen

Public demo · 2026-09-05Open full image ↗

Commerce

Why this pattern works

Study a product layout that keeps photography prominent while separating explanation from purchase controls.

Design notes

Surface: Product details
Navigation: The store header retains account and cart; expandable information rows sit under the description.
Layout: Three columns place product information at left, the main image in the middle, and price with purchase controls at right.
Density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
Color: White space, dark text, black purchase action, and neutral product photography.
Type: A bold product heading and price anchor opposite sides of a quieter description.
Pattern: Study a product layout that keeps photography prominent while separating explanation from purchase controls.
States: A single product with its price and add-to-cart action; no order is placed.
Don't: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Make it your own

Turn this reference into a useful brief for your project. Copy it into the AI tool you already use.

Your project

Use withI want to

Tech stack

Add constraints

What should the tool respect?

Preview & edit prompt

Prompt text

# My project
[Describe the product, audience, and screen you want to improve]

Stack: Use the existing project stack
Task: Implement the interface and verify the result in the existing project.

## Tool guidance (Any AI tool)
Use available project tools to inspect, implement, and test. State any unavailable capabilities.

# Design reference: Medusa — Product details
Source: https://next.medusajs.com/us/products/hoodie
Swipefile reference: https://swipefile.design/ref/medusa-product/
Captured: 2026-09-05. This is a dated reference, not a claim about the current live product.
Capture scope: one viewport. Do not infer unseen page sections or a complete user flow.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

## Reference notes
- surface: Product details
- nav: The store header retains account and cart; expandable information rows sit under the description.
- layout: Three columns place product information at left, the main image in the middle, and price with purchase controls at right.
- density: Primary content has the most space; repeated rows and secondary navigation use a compact, consistent rhythm.
- color: White space, dark text, black purchase action, and neutral product photography.
- typography: A bold product heading and price anchor opposite sides of a quieter description.
- pattern: Study a product layout that keeps photography prominent while separating explanation from purchase controls.
- states: A single product with its price and add-to-cart action; no order is placed.
- dont: Adapt the interaction pattern to your own product. Do not copy brand assets, sample identities, proprietary text, or assume unseen states. Specify keyboard behavior, loading, empty, error, and narrow-screen layouts for your implementation.

Useful for: Study a product layout that keeps photography prominent while separating explanation from purchase controls.

## Acceptance criteria
- Existing project conventions, design tokens, working functionality, and unrelated changes are preserved.
- Two or three reference principles clearly support the user's task; conflicts are resolved in favor of usability and the existing product.
- Reusable components and semantic HTML express the interface. Available licensed assets are used; important UI text is never rendered as a bitmap.
- Every visible control has a defined behavior. Loading, empty, error, success, disabled, and long-content states are specified where relevant. Demo data is clearly labeled.
- Navigation and content adapt at 375px, 768px, and 1440px without horizontal page overflow. Keyboard use, visible focus, labeled inputs, at least 44px touch targets, readable contrast, and reduced motion are supported.
- Verification distinguishes rendered behavior from proposals and identifies anything still requiring a backend or external service.

## Quality bar
Clear hierarchy, consistent spacing, restrained surfaces, and purposeful motion. Avoid decorative gradients, excessive cards, placeholder buttons, and invented metrics unless the project calls for them. Do not claim a feature is connected or tested without evidence.

Assembled in your browser. No API key or AI request needed. Changing the fields refreshes the preview.

## Objective
Adapt the interaction and layout patterns below to my project. Use my own content and identity. Do not reproduce logos, proprietary copy, or brand assets.

Useful for: Study a product layout that keeps photography prominent while separating explanation from purchase controls.

Medusa — Product details

Make it your own

Keep exploring