Template galleries tend to be chosen by looks, so the layout often fights how buyers actually evaluate this kind of product. In this case, the immediate task is to choose a product-page structure suited to the product. The workflow should produce the recommended template together with the adjustments it needs, noting where that structure falls short.
First replace every [bracketed] placeholder with real store scope and constraints, then add any actual records or data you have, and paste it into your preferred AI assistant or Spark agent. Spark will follow this page's workflow to produce structured output and verification steps.
Act as a Shopify operations specialist.
Help me choose a product-page structure suited to the product.
My store context is [describe the business, products and target audience].
My scope is [specify the affected products, pages, customers or reporting period]. Use these inputs: [candidate templates, the product's specification count, image count, variant options, buyer decision steps from the audience notes, and each template's fixed and flexible sections]. Score each template against those decision steps by checking that every blocker question has a section answering it in order, and mark any template where key information would have to sit in a section buyers do not read.
Return the recommended template with the adjustments required, verified against the merchant's records for the specified task.
Show the relevant evidence or before-and-after examples and explain how I can verify the result.
If essential data is missing, ask for it and mark unsupported conclusions as unknown.
Do not invent metrics, product claims or customer facts.
For any publication, message, account or store change, use only connected tools within my explicitly authorized scope and report success only after verification; otherwise provide the draft or proposed steps.Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.
Gather the candidate templates together with the product's specification count, image count and variant options, and the buyer decision steps recorded in the audience notes, and note for each template which sections are fixed and which can be rearranged.
Score each template against those decision steps by checking that every blocker question has a section answering it in order, and mark any template where key information would have to sit in a section buyers do not read.
Deliver the recommended template with the adjustments it needs, the sections to add or remove and its known shortfalls, then verify the plan covers every specification and image in the product record.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Use one default where products share the same decision steps, but route products needing comparison tables, sizing detail or configuration to their own structure. The routing rule names the product attribute that triggers the alternate template, so assignment stays consistent as the catalog grows.
When a required piece of information has no dedicated slot, it gets pushed into a section buyers skip or buried below detail they never reach. The check is whether each blocker question has an answering section, in the order buyers actually ask it.
Yes. Rework it once page evidence such as scroll depth or support questions shows buyers missing a section, and record which purchase question the adjustment serves. Keeping that mapping documented prevents the next template choice from repeating the same gap.
Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.
Ciwi Spark builds Shopify-native AI tools and agents around the workflows merchants actually run: research, ads, translation, and customer support. Stop rewriting the same prompts by hand.