Give it a one-line brief. It builds every design the launch needs — banner, modal, card, email, social — from your design system. It picks the right visual for each surface, writes it for each discipline, and submits the set for review.
Your rules are the input. So the fastest way to ship is also the on-brand way.
Six real Figma launches. Pick one and watch it build.
⁘ tools menu · ▤ the rules · { } what's underneath · Live the company feed
Three steps, instead of a dozen requests.
Bring frames, code, copy, a prototype, or just a message. It reads all of them.
Every surface gets the one visual your system allows. An icon, a billboard, motion — or nothing, when the words should lead.
One verdict for the whole set. Most of it clears. Anything risky goes to the right team.
Five rule sets a design-system team already owns. Written once, read on every launch, shown here in full.
1 · Visual assets
2 · Eleven comms types
3 · Where it can appear
4 · What outranks what
Impression-capped, so nobody sees the same message twice.
5 · One asset system, five voices
Then: stable, or not yet?
Published components, every check passed, nothing downstream has to change.
New pattern, or a change other teams absorb. Not wrong. Just not proven.
Failed a spec check. It would ship broken.
Cadence recommends and says why. You decide where it goes.
Built on figma/sds — real tokens, not approximations. Which is the whole point: the rules were already published in a format a machine can read. They just needed wiring up.
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's a scramble. A banner here, an email there, a Community card someone remembers late. Each built by a different person. Each drifting a little.
The hard part of a design system was never writing it. It's getting teams to adopt it.
Adoption doesn't fail because teams disagree. It fails because following the system is slower than not following it. So make the rules an input, not a document. A team gets a complete, on-brand set in one pass — and the only way to get it that fast is to be on-system.
That matters most for the products moving fastest. They don't need a brand review. They need a sandbox with the rules already loaded, so they can build an idea and ship it the same day. Speed to execution, concept to code.
Comms is the pilot. The mechanism is the product.
Take the rules a company already has, make them machine-readable, let an agent resolve them into finished work. That generalises to every place a brand has to hold across many teams — which is what every enterprise design-system team is trying to solve.
Extends Julie's product-communications concept — julietorrisi.com/design-ai