← Back to the issue
01 Figma Blog · 26 August 2026

Your design system is becoming an AI interface

Figma’s latest workflow shows how components, tokens and documented states can give coding agents enough context to produce more faithful product work.

Document intent
Write the behaviour, states and transitions before prompting.
Feed the system
Give the agent approved components, tokens and production mappings.
Review for drift
Compare design variables with code before the mismatch becomes expensive.

The Story

Figma’s new Workflow Lab frames the design system as more than a library for humans: it becomes the vocabulary an agent needs to work responsibly. Screenshots alone leave too much room for invention; components, tokens and states carry the decisions that make an interface feel intentional. ([figma.com](https://www.figma.com/blog/workflow-lab-moving-between-design-and-code-with-agents/))

The useful shift is from prompting for pixels to supplying context. Figma’s example connects FigJam diagrams, MCP, Code Connect and an existing component library so the agent can reuse patterns instead of rebuilding approximations.

For Studio Wensday, this is a strong case for documenting the invisible parts of a visual system: not only colour and type, but behaviour, edge cases, naming and rationale. The better the system, the more useful AI becomes—and the less it flattens your point of view.

Studio Wensday Angle

Treat design-system documentation as creative infrastructure for both people and agents.