← Back to the issue
01 Figma · September 2, 2026

The design system is now part of the prompt

Coinbase’s Code Connect experiment shows that better component context can make agent-built interfaces faster, cheaper, and more faithful.

Map
Connect production components to their design-system counterparts.
Guide
Give agents rules for tokens, accessibility, and deprecated patterns.
Evaluate
Measure adherence, implementation time, token use, and cost.

The Story

Coinbase tested Figma Code Connect with coding agents and reported lower token use, faster implementation, and stronger design-system adherence. The useful part is not the headline percentage; it is the underlying principle: agents perform better when they receive the same structural context a good designer or engineer would.

For Studio Wensday, this points toward treating the design system as an operational asset, not a static library. Components, naming, tokens, states, and usage guidance are becoming part of the creative brief that machines can actually understand.

The practical move is to document the decisions behind your system as carefully as the components themselves. A well-explained system can become a bridge between visual direction, product design, and production code. ([figma.com](https://www.figma.com/blog/how-coinbase-used-code-connect-to-shrink-token-costs/))

Studio Wensday Angle

Design-system documentation is becoming creative infrastructure.