Ecommerce Detail Page Planner and Wireframe

Problem

Ecommerce detail pages often stop at feature lists, lacking a continuous narrative from browsing to understanding, trust, and purchase decision. Common issues include vague first-screen promises, selling points disconnected from buying reasons, and missing or inconsistent specs and assurance information. Teams also need a quick structural preview before design review.

How It Works

• Requirement alignment: collect product name, positioning, target audience, core scenarios, selling points, and key specs / materials / dimensions to avoid invented hard indicators.
• Screen-by-screen planning: produce copy for the value proposition, reinforced claim, selling-point-to-buying-reason, usage scenarios, product detail images, and product parameters; copy follows user language for buying reasons and product language for selling points, with each selling point on its own screen.
• Selling-point order: fixed as form → glaze/appearance → material → pairing, moving from exterior to essence and from visual to material.
• Wireframe delivery: read assets/wireframe.html, fill confirmed content into a 375px mobile long-image template, and save a new black-and-white low-fidelity HTML prototype.

Boundaries

Best for planning detail-page content and low-fidelity previews when product, audience, selling points, and specs are available. Typical output is a screen-by-screen copy draft and an HTML wireframe, useful for reviewing structure, narrative order, and placeholder content. It does not replace photography, visual design, UI polish, or compliance review. If Stage 1 lacks key parameters, ask for them first instead of leaving placeholders.