The quiet work of keeping a system alive

The Story

Design systems rarely fail because teams lack a beautiful component library. They fail because the library drifts: names become inconsistent, documentation goes stale, and product work quietly starts inventing its own rules. Figma’s October update puts that maintenance problem at the centre. ([figma.com](https://www.figma.com/blog/figma-agent-and-design-systems/))

That distinction matters. The agent is most useful here not as a generator of finished interfaces, but as a patient reviewer that can find repetition, flag drift, and prepare documentation while a designer decides what the system should mean.

For Studio Wensday, this suggests a practical service opportunity: design-system care plans. A visual system could include monthly audits, usage notes, exception logs, and a small set of evolving principles—not just a handoff folder that goes stale.