Product Page Marketing Sections

The first purpose is to create beautiful, polished, persuasive marketing sections that bring the user's strategy to life on an existing product page. Design for the product, brand, and audience, with mobile quality first and a simple desktop adaptation. The bundled recipes are inspiration only: adapt, mix, or invent layouts and styles, including a coherent direction outside the library. Success means compelling, accessible sections with truthful claims and an intact buying flow, not an exact recipe match.

Defaults and inputs

Use the current repository and conversation first. Normally the user supplies a strategy and a product identifier, URL, or route. Accept a strategy in prose, bullets, a document, or a referenced local file.

Infer from the repository when available:

• Product facts, actual options, language, audience, existing media, price source, and policies.
• Framework, component conventions, styling system, image pipeline, test commands, and route structure.
• Suitable insertion point and the existing purchase/form anchor or action.

Automatically choose the number, order, composition, and placement of sections. Default to the smallest useful set, often 1–3 sections; this is not a fixed cap. Do not turn every strategy into a complete sales page or duplicate information already well covered. Explicit user placement or section-count instructions take precedence.

Proceed without an approval loop when the target and essential information are clear. Ask a focused question only for a real blocker: ambiguous target product, missing strategy with no actionable angle, or a critical fact/asset that cannot be recovered. If a desired proof section lacks evidence, select a useful factual demonstration instead when the strategy permits it; do not invent proof or stop all independent work.

Use the page's language unless the user specifies another. Treat the user's wording “desktop vue/view” as viewport design, not a request to migrate the app to Vue.