E-Commerce Detail Page Content Wireframe

Problem

Product detail pages often become parameter dumps: titles read like specs, selling points repeat, and use cases are missing until design tries to fix it late. This skill treats the page as a content-planning problem: confirm what the product can promise, then structure why a user buys, when they need it, and how hesitation is reduced.

Workflow

It does not jump straight to HTML. It first asks for complete product information, then moves through fixed layers:
- Core value promise: produce a first-screen value definition.
- Pain-point anchoring: separate pain, itch, and pleasure points into one page-ready line.
- Selling-point strengthening: translate features, ingredients, processes, or standards into purchase reasons, with one core selling point per screen.
- Usage scenarios: select the Top 4 high-value scenarios instead of generic examples.
- Decision close: summarize reassurance, value, or low trial cost to reduce hesitation.

Each step returns multiple options. After the user selects, merges, or edits an option, the flow advances. The final deliverable starts as a complete copy document, then becomes a 375px mobile-scroll HTML wireframe with inline CSS: white background, black text, light-gray modules, thin black dividers, and no external fonts, images, CDNs, or third-party libraries.

Limits

It fits detail-page planning that can be handed to operations, design, or content teams. When key product facts are missing, it asks for them rather than inventing them. For children, food, or health products, parameters, efficacy, certifications, and claims must come from user-provided or verifiable sources.