When an advertorial, ad or landing page gives you a useful model, analyze why it works before adapting it to your Product.This keeps the source’s reusable structure separate from its offer-specific wording and details.
Break down its section order and persuasion flow, then reuse the framework
for your Product.
Find the structure behind an ad
Attach an ad image or screenshot and analyze its hook, visual hierarchy,
proof, product visibility and CTA before creating variations.
Compare Meta creative patterns
Use the Meta connector to compare current ads and investigate the hooks and
formats behind the results.
Turn a CSV into a decision
Attach an export, name the metrics and date range, and ask which patterns
deserve the next test.
Continue useful work in a new Chat
Carry the selected direction, source facts, and next task into a fresh
conversation without rebuilding the brief from scattered messages.
You normally do not need to select a tool. Describe the result you want and
let StefanBrain choose the useful capabilities. Select a tool only when you
need its rigid controls or output.
Use the smallest relevant context set. Do not attach 300 pages because they
might help. Start with the source, Product and files that can change this
result, then add more only when something is missing.
The model provides the structure. Your Product provides the facts and direction for the new work.
1
Add the model
Paste the public URL, attach the file, or add a screenshot. Name the item
StefanBrain should treat as the model.
2
Ask StefanBrain to break down the structure
Analyze the model before asking for a new draft.
Here's an advertorial I want to learn from. Analyze why it works and break its structure into a reusable framework and outline we can use for @Product.Separate the reusable structure from the source offer's wording and product details.
The first pass uses the source only as a model and separates its reusable section structure from source-specific wording, facts, and claims.
Review the framework before adapting it.
3
Correct the breakdown before adapting it
If StefanBrain misunderstood a section, explain what it does and ask for a revised framework.
The testimonial is proof after the mechanism section, not the mechanism itself. Update the framework around that distinction.
4
Add the correct Product or offer context
Type @ and choose the Product for the new work. Start inside the correct
Project when the job also needs its files or campaign direction.
5
Adapt the model to your offer
Keep the same Chat so StefanBrain can use the framework you approved.
Now turn that framework into an advertorial outline for @Product.Keep the structure and persuasion flow. Use this Product's audience, mechanism, proof, and objections. For each section, include its purpose, key message, and evidence needed.
After the structure is approved, the same Chat adds the selected Product and adapts the model into a practical outline.
Review the outline before asking for a complete draft.
For an ad image or screenshot, analyze the visible structure before asking for variations.For a complete worked example, follow Create native ad concepts from a
winning ad.
Analyze this ad as a model. Break down the hook, visual hierarchy, product visibility, proof, CTA, and the order a viewer is likely to notice each element.Return the reusable creative structure and the product-specific details we should replace for @Product.
Then add or confirm the correct Product context and ask StefanBrain to adapt the structure to a defined audience, message, and format.In that focused workflow:
Attach the reference ad, its copy, and the image you want to keep.
Ask StefanBrain to explain the ad’s reusable structure before requesting new ideas.
Request several distinct concept families that preserve the useful image but change the angle, setting, or story.
Remove generic ideas, explain what the response is overusing, and run a narrower follow-up.
Use the enabled Meta account to compare ads from [start date] through [end date].Show which hooks and formats deserve deeper investigation using [the metrics that matter to this decision]. Return the observed patterns, supporting data, and three next tests.
If the connector is unavailable, attach a CSV and use the same request. Name the file, date range and metrics.
Stay in the current Chat when you are still refining the same result. Start a
new one when the next job needs its own conversation, such as turning research
into a script or preparing a separate client deliverable.Bring a short handoff with you. Name the selected version and include the
decisions that affect the next task, rather than pasting the entire conversation.
Ask for a brief you can inspect before the next Chat starts drafting:
Create a handoff I can paste into a new Chat to continue this work.Include the goal and audience, the Product facts we used, the direction we chose, the exact latest copy or outline, and the constraints that still apply. Separate final decisions from open questions. Include the source names and anything I need to attach again.Leave out rejected drafts. End with the next task: [what I want to do next]. Return the handoff here in the Chat.
Read the handoff against the version you chose. Replace stale details and add
any missing source before copying it.
For a fictional desk lamp, a useful handoff might look like this:
Next task: Write one email introducing the lamp to people setting up a small home desk.Product facts: USB-C powered; three brightness settings. Use the attached Product brief for the remaining details.Chosen direction: A focused workspace in a small room. Start with the reader clearing a spot to work, then introduce the lamp.Keep: Plain, conversational wording and one CTA to view the lamp. Do not add a discount or a deadline.Sources to attach: Product brief and the two selected brand-voice examples.Open question: Which product-page link should the CTA use? Ask before inserting it.
The next Chat has a job to do, a chosen direction, and a clear distinction
between known facts and missing information.
Open a new Chat in the intended Project if the work belongs there. Paste the
brief, select the correct Product, and attach the source files the next task needs.Use the first response to catch missing inputs before generating another draft:
Use this handoff to continue the work. First confirm the selected direction and which attached sources support it. Ask for anything essential that is missing, then complete the next task. Don't restart the research or bring back rejected directions.
Pasting a handoff does not attach the original files or give another person
access to them. Add the relevant files to the new Chat instead of assuming they
travel with the summary.For instructions you want to reuse across several Chats, see
Manage multiple clients with Projects.
