Code is a design material
For years our industry has argued about design versus code, as if you had to pick a side. Figma Config 2026 quietly ended that debate this week. The premise underneath every announcement was simple. Code is a design material, the same as vectors, type, and frames, and it belongs on the same canvas as everything else.
That reframe matters more than any single feature, but the features are worth knowing.
Code Layers lets you turn any design layer into an interactive, GitHub-linked code layer with a click or a prompt, iterate on it beside your team, then sync changes back to the codebase. Figma Motion brings a real animation timeline onto the canvas, with keyframes, presets, and export to CSS, React, and JSON, so motion finally lives inside your design system instead of a separate tool. Shaders, generative plugins, 3D transforms, and Weave image workflows round out the "new materials" story.
The part I am watching most closely is the agent. It now carries Skills, which package your team's conventions into reusable instructions, and Connectors, which let it reach into Notion, Slack, GitHub, Atlassian, and more, then send updates back. That is not a design feature. That is an integration architecture, and it looks a lot like the agentic patterns we have been building toward in the enterprise.
Here is the tension worth sitting with. Lowering the floor is easy, and AI has done it everywhere. Raising the ceiling is the hard part, and that still depends on judgment, taste, and the people doing the work. New materials do not make better products on their own. They make the gap between strong design thinking and weak design thinking more visible than ever.
If you design for regulated, high-stakes environments, that gap is the whole job.
What are you most curious to put through its paces first?
#config #Figma #figmaconfig2026