The agent does the work — on a canvas, with your brand's memory loaded
You asked for a carousel in plain language. The agent opened the Social area, loaded what it already knows — your positioning, your facts, your rules — and produced right there. The module became a canvas it drives, not a screen you navigate. Everything it learns while working comes back as an approval-gated proposal.
Understand
Produce
3 Learn
Area · Social
You
Make a launch carousel for our enterprise-relocation push.
Assistant
Loaded your Social area: enterprise positioning, "30 countries", and your carousel rules (slide 1 = bold stat, flat-minimal look). Drafting 4…
First pass — 5-slide set. Slide 1 opens on the stat hook, closes on your standard CTA. Pick the cover to carry forward:
1 · "30 countries" stat cover
2 · One accountable partner
3 · Visas · goods · settle-in
5 · "Get a move plan" CTA
Flat-minimal illustration, indigo + pink on cream — pulled from your pinned image look.
Slide set drafted
The last one's too photoreal — we always want flat minimal for product shots.
Fixed — re-rendered slide 5 as flat-minimal illustration, no photoreal. The set on the right is updated. That sounds like a standing rule, not a one-off:
Remember this so future work stays consistent?
Product shots are always flat minimal illustration — never photoreal.
Applies to
This set
All image posts
Brand-wide
Scoped to surface: image in the Social area · reversible.
Also — a fact to saveapprove
Add "30 countries" to Company facts — I used it as this carousel's headline stat, but it isn't in your Knowledge Base yet. Saving it means every future post, page and proposal can rely on it.
Goes to Knowledge Base → Company facts. Source: this session. Nothing else changes.
New fact · 1 field
Rewrite slide 2 copy
Schedule for launch day
Export the set
The agent loads the area, produces, and captures what it learns — the rule and the fact are both proposals you approve. Nothing is remembered silently.
This is the whole product in one screen: the agent works with your brand's memory (never from scratch), the module UIs become canvases it drives, and every change — creative, factual, or a new rule — is proposed for your approval and folded back into memory.