Give Cadence a one-line launch brief. A Design agent and a Content Design agent build every promotional design the launch needs — the Dev Mode banner, the in-canvas announcement, the Community card, the email, the social hero — from your real design system, library, Variables, and tone of voice, as one coherent bundle. Then it submits the whole bundle for review with a governance verdict and routes anything that needs a human.
Each item is a real Figma launch — Motion, Code Layers, Shaders, Agent, Generative Plugins, Weave — and a real thing a product team does: ship a feature and promote it everywhere. Cadence reads the brief, a Design agent and a Content Design agent generate the complete set of on-brand designs across every Figma surface, and it submits the bundle for review — one verdict, with anything risky routed to the right team. Flip Under the Hood to see the agents and infrastructure that produced it. It's wired to your Figma UI kit — real Banner, Card, and Modal components, and their rules (Warning · Informative · Upsell).
Three steps replace a scramble of tickets, handoffs, and one-off asset requests across half a dozen teams.
Paste the launch ask — a PM's message, a release note. Cadence extracts the audiences, the key message, and every surface the launch needs to cover.
A Design agent composes each asset from your library and Variables; a Content Design agent writes the copy from your tone of voice — banner, modal, card, email, social, coachmark — on-brand and on-spec, as one coherent set. No blank canvas, no six separate requests.
The whole bundle is governed at once: most assets clear, spec failures are flagged to fix, and brand, pricing, or privacy calls route to the owning team — with the bundle attached.
A launch isn't one design. It's a dozen — across a dozen surfaces, on a deadline, all supposed to feel like one thing.
Today that means a scramble: a banner request here, an email ask there, a Community card someone remembers late, each built by a different person, each drifting a little from the system and from each other. The design work is real, but the rollout — who sees what, where, how often, and whether it's even allowed to go live — has no owner and no system. Cadence gives every launch one standard way to draw on what you already have — your library, your Variables, your tone of voice — with a Design agent and a Content Design agent doing the production and a governance layer deciding what can ship. Brief in, a complete governed bundle out, submitted for review in one pass. The design system already holds the taste; this is what programs it into every launch.
And it isn't one message for everyone. Cadence knows each seat's discipline, so a designer, an engineer, and a PM each get the same launch in the voice that helps them use it — the old way was one blast for all, or a few broad target segments; this is uniquely talking to each seat so the product actually lands.
Extends Julie's product-communications concept — julietorrisi.com/design-ai