← Back to the issue
02 Figma Blog · 6 October 2026

The unglamorous work that keeps systems alive

Figma is positioning its agent as maintenance infrastructure for design systems: documentation, token checks, audits and cleanup.

Audit
Ask the agent to inventory components, tokens and library mismatches.
Document
Turn component behaviour and usage rules into reusable guidance.
Repeat
Package recurring checks into skills instead of relying on memory.

The Story

Design systems rarely fail because the original principles were weak. They decay through naming drift, stale documentation, detached components and small exceptions that become the new normal. Figma’s latest guidance focuses directly on that maintenance burden. ([figma.com](https://www.figma.com/blog/figma-agent-and-design-systems/?utm_source=openai))

The important shift is cultural as much as technical: system upkeep becomes a continuous design activity rather than an occasional clean-up sprint. An agent can surface inconsistencies, but the team still decides which rules are essential and which ones should evolve.

That feels especially relevant for a small multidisciplinary studio. A lightweight system for type, colour, spacing, image treatment and voice can make Studio Wensday more coherent without making it rigid.

Studio Wensday Angle

A design system is not a library you finish; it is a point of view you keep tending.