E-commerce Detail Page Designer

Problem Context

E-commerce detail-page design often gets stuck on information architecture and evidence. Product data, target audiences, brand assets, and platform dimensions usually live in separate documents, so design work can start with visual layout before the page has a clear purchase reason, core evidence, specification assurance, and call-to-action. This skill is intended for e-commerce designers, product operations, and brand teams. Its goal is not simply to generate an image, but to turn input materials into a traceable page structure and then produce the copy, visual instructions, and acceptance checks needed for a reviewable detail-page design.

Workflow and Deliverables

• Required inputs: product materials, target audience, brand assets, and platform dimensions, plus business goals, factual boundaries, and delivery requirements.
• Evidence boundary: Use only citable data. Do not invent price, sales volume, reviews, efficacy claims, or platform status. When key facts are missing, list the gaps first and propose the smallest safe path to continue.
• Core process: Verify source, time range, authorization boundary, and metric definitions; separate known facts, assumptions to validate, constraints, risks, and action items; organize the page around first-screen purchase reason, core evidence, usage scenarios, specification assurance, and action instructions.
• Output structure: Deliver a summary, main deliverables, evidence and definitions, risks and blockers, and next steps. The main deliverables include detail-page information architecture, page copy, visual instructions, and an acceptance checklist.
• Quality bar: Facts, numbers, cases, and claims must have sources. Items without sources must be marked as unverified. Recommendations should include owner, action, reason, and acceptance signal.

Boundaries

This skill is useful for taking an e-commerce detail page from raw materials to a reviewable and executable design plan, especially when the work involves cross-functional review, repeated acceptance checks, or compliance constraints. It is not intended to directly publish content, send messages, make payments, delete data, change permissions, or operate accounts. Any external write, privacy, permission, or target-system state issue must be confirmed before execution.