The pairing that works takes discipline. You own problem framing, brand judgment, UX calls, governance, stakeholder trust.
The agent owns layer hygiene, token binding, boilerplate, migrations, doc drafts, inventories.
Hackathon proof, not hype
At the Into Design Systems AI Hackathon 2026, our team built SwapWizard, a Figma plugin that smart-matches and swaps components even when names don't align. We took 1st place. The lesson wasn't "AI is magic." It was: point AI at tedious, high-volume work humans hate, and you free senior people for judgment calls.
I still decided what belongs in the library. The agent handled the swaps.
How I run the studio
One principal paired with coding agents, not a principal replaced by AI. Client work still needs someone who speaks to Heads of Product, who can say "use the system" when a PM wants a gray button by Friday, who prices outcomes not hours.
Agents protect time for relationships and taste. That's the craft layer on top of systems thinking.
Audit your Monday cleanup
Who on your team is still doing structural work an agent should own? Detached instances, rogue spacing, token rename propagation, changelog drafts from merged PRs, that's agent territory.
Save your designers for the work only humans should do. The rest is entropy management you can automate.