Everything needed for the page exists in the store's records, but spread across exports nobody has reconciled. In this case, the immediate task is to build a complete product page from verified product data. The workflow should produce a page specification with its asset list, leaving unsupported fields blank instead of filling them with plausible text.
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 build a complete product page from verified product data.
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: [verified product data covering variant attributes, pricing and availability, the approved image set, current policy text, and the conflict list between exports]. Fill each page section from that verified data, resolve recorded conflicts against the merchant's confirmed authoritative source, and leave any field without support empty and marked pending rather than filling it with plausible text.
Return the completed page specification with its asset list, every field checked against the supplied 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.
Assemble the verified product data covering variant attributes, pricing and availability, the approved image set, and the current policy text from the merchant's records, listing every field where two exports disagree for resolution before use.
Fill each page section from that verified data, resolve recorded conflicts against the merchant's confirmed authoritative source, and leave any field without support empty and marked pending rather than filling it with plausible text.
Deliver the page specification with its asset list and the count of pending fields, then check every populated field back against the supplied records so nothing reaches the publish step unverified.
Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.
Each disagreement is listed at collection and resolved against the source the merchant confirms as authoritative, with the ruling recorded; a page is never built on an unresolved conflict, because whichever value loses creates an order the store cannot fulfil as described.
Because plausible placeholder text reads as a claim the record cannot back and reaches buyers as if verified; blank pending fields with a named need keep the publish step honest and show exactly what must be sourced before launch.
Every populated field is checked back against the supplied records, the asset list is matched to the images actually referenced in the specification, and the pending-field count is stated so the merchant knows the page's completeness before publishing.
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.