What do the Config 2026 announcements mean for design systems?

Luke Murphy
Written by Luke Murphy
Jun 25, 2026

The annual feature-fest that is Config happened today, with a slew of updated and new features coming out to everyone’s favorite design tool. The overall narrative definitely sits in a ‘maker’ space, with a lot of it focusing on what they call ‘materials’. However, if you’re looking for the design systems goodness, we’ve had to look a little deeper into the keynote big-ticket items. We thought we’d do a rundown of what it all means for design systems folks, and how it might improve, change, or mess up your current processes.

Agents, Skills, and Connectors

What was announced

The Figma agent rolled out to everyone, and the more important news is what now sits behind and around it. Skills package your workflows and conventions into reusable instructions that the agent follows. Connectors let it reach into the tools already in your stack, like zeroheight, Notion, Slack, Granola, Hex, GitHub, and Atlassian, and send updates back. Attachments let you drop in briefs, research, or any artifact for context. They’ve also integrated agents in the multiplayer aspect of Figma, so everything is shared, visible, and able to be collaborated on. Soon, this will be across Figma products, like Design, Figjam, and Slides, too.

What it means for design systems folks

For design systems folks, there’s a lot that agents can do to shortcut tedious, repetitive, or manual tasks within the design process. However, being able to do this with skills and connectors allows you to automate creation, audit, and iterate while remaining on system. Using connectors to pull in live content from complex sources, hooking variables up to a quickly made design, componentizing snowflakes to get ready for contribution… There are endless flows that can massively save time.

What still needs answering

One of the biggest, obvious open questions with agents is token usage. At the moment, usage is unlimited, but as soon as it comes out of public beta, there’s a real chance that tokens are going to get expensive. That means that we probably need to really figure out where the real savings are with using agents, and which are better to still do manually or via other avenues. There will come a time when the cost of automating might outpace the value.

Code Layers on the Canvas

What was announced

You can turn any design layer into an interactive code layer with a single click or a prompt, duplicate it to explore directions side by side, and collaborate on it in the same file like any other frame. You can extract code back into editable design layers, and one click pushes design changes back into the code layer. It’s about to be in closed beta, so there’s less detail around what is possible with code layers, but from what we know, there’s some interesting use cases for this.

What it means for design systems folks

It feels like this is a major step towards the gap between design and development getting practically narrower. Because the code is real code, pulled directly from your repo with git-style functionality for managing it, the components on the canvas are your components and tokens. Translating between code and design modes stops being a handoff and becomes a round trip. Combine it with the agent and the connectors, and you can start imagining real auditing in-canvas: is this layer using the system's variables, is it on the current component version, does it match what's documented?

Why I think this matters so much to design systems folks is that this allows for more frictionless iteration on code for folks who think visually. Being able to pull from the repo, switch it to design to make tweaks, iterate, or explore, then push that back is great for a lot of designers.

What still needs answering

The big if for this that will be answered as soon as we get access to it is the quality of output. On the code to design side, whether the design generation uses components and variables from the design library will be important to minimize drift. On the design-to-code side, again, getting Figma to generate code that is on-system and follows your coding conventions is a big if when it comes to how useful this will be to production teams.

Generative plugins

What was announced

Up until now, plugins were the domain of engineers. Recently, we’ve been able to create Figma plugins using things like Claude Code or Cursor. Now, you can create them directly in-file using agents. The cool thing is that the generative plugins within Figma natively use the Figma controls and package them up without needing to host them. So, if you have an idea of something you want Figma to do, you can just prompt it into creation in a way that is reusable and sharable with your team. At the moment, those plugins exist within the file they’re created in. Soon, you’ll be able to share across teams and orgs. Later, you’ll be able to publish these generated plugins to the Community for wider use.

What it means for design systems folks

This isn't design-system-specific, but is still something pretty powerful for design systems teams. Design systems and ops people are already the ones building bespoke tooling, and we usually pay a real engineering and maintenance tax to do it. Generative plugins significantly reduce that tax. The repetitive, system-maintenance work that never quite justifies a sprint can now be a five-minute tool. When it arrives, the publishing path is what turns it from a personal convenience into a system-wide capability, so I'd watch that closely.

What still needs answering

I don’t think there were many open issues from a technical point of view on generative plugins. I think the biggest thing will be a governance and maintenance layer, and how they’re especially handled at an organizational level. The concept of 500 different designers and PMs creating small, single-use plugins could lead to chaos.

Figma Motion

What was announced

Motion has just entered the chat. Keyframes, easing, transforms, presets, build-from-scratch, or agent-generated starting points directly in Figma Design. It’s basically Flash reincarnated, but with a great-looking user interface, can be tied to variables and componentized, and exports to loads of formats, including accessible web-based formats (and being surfaced in the MCP and Make). I genuinely think this is one of the most exciting announcements Figma has made in the last few years.

What it means for design systems folks

For me, this is one of the sleeper giants for design systems as an industry. Until now, we haven’t had good ways to hand off motion between design, creation, and code. The fact that almost everything can be tied to variables, and motion and interaction can be baked directly into components, finally makes motion systems a first-class citizen. We’ll now have a way to define and test interaction and motion on both the design and code side, with easy handoff.

What still needs answering

The two big open questions are: the inclusion of styles for motion so it can be easily packaged, and how standards-compliant the output of things like easing curves is. There are also some more export options that I’d like, but the ones out of the box cover most aspects. There’s also an existential question for design system folks around ‘just because we can have motion, should we?’ that will likely come up. Creating motion has become easy; we need to make sure we don’t saturate what we do with constant movement just for its own sake.

The rest of the goodies

Shader fills and effects. Describe what you want (or hand it a reference image), and the agent builds a shader to create some pretty stunning visual effects. Effects transform a layer, and fills act as a new layer. The design-systems-relevant detail is that they're parameterized by default; parameters surface as on-canvas controls, stack with other effects, and convert to code and common formats. That parameterization is a tokenization question waiting to happen. If these become part of brand expression, can they be governed like the rest of the system, or do they become a new source of untracked visual variance? Interactive shaders are also coming once performance is sorted. However, one important thing to remember is that most of the shader effects are things that just aren’t particularly standard when it comes to the web, so implementation in code will likely require heavy JavaScript.

Figma Weave tools. Figma acquired Weave last year, which provides a way to create node-based workflows for working with generative AI tools. Weave now connects directly into the Figma canvas. You can build workflows and publish them as templates to remix, with team/org/community publishing coming. More relevant to content and brand/marketing creative than to component systems, but the same "build a reusable workflow and share it" pattern as plugins and shaders, so worth knowing it exists.

Worth noting the through-line across plugins, shaders, and Weave: Figma is betting on everyone building and publishing their own tools. For a design system team that's both an opportunity (faster bespoke tooling) and a governance problem (tool sprawl), and it's the same tension in three different wrappers.

The final word

The unifying theme of Config 2026, read through a design-systems lens, is that the canvas is becoming context-aware. Code, motion, agents, and custom tools all now live in the same file and can all, in principle, draw on your system. The upside is enormous: less translation loss between design and code, motion that finally behaves like a system primitive, and AI that explores within guardrails instead of around them. But almost every one of these wins is conditional on the same thing: the quality and machine-readability of the system underneath.

Similarly, because so many of these new tools lean heavily on agents, token usage is going to become a real talking point over the next 12 months. For now, it’s time to dive into the tools and see what they can do to make our work easier.

Luke Murphy
Luke Murphy
Luke (they/them) is Lead Design Advocate @ zeroheight. When they’re not enthusing about DesignOps, they are playing in bands, drawing silly things or writing academic articles about Josie and the Pussycats.
Figma x zeroheight
Want to explore zeroheight's connection with Figma?
Try today for free
Share this post