Back to topic
Spark playbook scenarios · Spark: AI Store Assistant

Create social posts tailored to the intended channel

A merchant needs posts for one channel this week, and the copy must fit its limits without saying more than the product data supports. In this case, the immediate task is to create social posts tailored to the intended channel. The workflow should produce captions ready to publish, each carrying one claim and an action call within the format limits.

Topic
Social Media Content Creation
Target keyword
shopify social media post generator
Copyable AI prompt

A prompt you can drop directly into Spark

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.

ai-prompt.txt
Act as a Shopify operations specialist.
Help me create social posts tailored to the intended channel.
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: [product facts from the supplied record with title, attributes, price and availability, the audience and campaign goal, brand voice rules, and the intended channel's caption length, media count and format limits].

Draft one post per chosen slot stating exactly one claim the supplied product record supports, place the action call the campaign goal requires at the end, and cut or rephrase anything asserting a benefit, comparison, price or availability the record does not state, shortening rather than trimming meaning when a caption exceeds the channel limit.
Return channel-ready posts with captions and a call to action 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.
Use in Spark
How to solve

A recommended resolution workflow

Split the work into input, judgment, and deliverable phases. Verify each step's output before moving to the next.

01

Step 1

Take the product facts from the supplied record, meaning title, key attributes, price and availability, the audience and campaign goal for this push, the brand voice rules, and the format limits of the intended channel including caption length, media count and characters that channel renders unreliably.

02

Step 2

Draft one post per chosen slot stating exactly one claim the supplied product record supports, place the action call the campaign goal requires at the end, and cut or rephrase anything asserting a benefit, comparison, price or availability the record does not state, shortening rather than trimming meaning when a caption exceeds the channel limit.

03

Step 3

Deliver publish-ready captions with the claim, the action call and the character count against the channel limit, note every claim softened because the record did not support the stronger wording, and check that no post promises a price, stock state or delivery timing absent from the supplied data.

FAQ

Common questions when running this scenario

Cover decision rules, frequent misunderstandings, and required inputs so the team aligns on prerequisites before execution.

Why not reuse one caption across every channel?

Each channel has its own length, media and audience conventions, so one caption is either truncated where it matters or padded where it does not. Adapting keeps the claim identical while fitting how the channel is read, and the claim itself never changes between versions.

What if a stronger claim would sell better?

It still cannot be used unless the product record states it, because a post promising a benefit the store cannot deliver turns into a support ticket and a refund. The stronger wording is listed as a data gap the merchant can fill instead of a claim the copy can make.

How is a post judged ready to publish?

When it carries one claim, one action call, sits inside the channel's character and media limits, and every factual statement traces to the supplied product record. Anything failing one of those four stays a draft rather than entering the calendar.

Related scenarios

Continue with adjacent or same-topic scenarios

Start with scenarios under the same topic, then expand into cross-topic matches suggested by similarity.

Next step

Want these AI scenarios embedded directly into daily operations?

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.