Copilot can now push code back into Figma as layers
Published 13 September 2026 · Source dated 6 March 2026
GitHub confirmed Copilot can pull Figma design context into code via MCP, then send rendered UI back to Figma as editable frames — a two-way bridge with real implications for spotting design system drift.
GitHub's changelog confirmed Copilot connects to the Figma MCP server to pull design context into code and, newer, send rendered UI back to Figma as editable frames. That closes a loop design system maintainers have wanted for years: generate code from a design, then pull the as-built UI back into Figma to check it against your components.
It's live in VS Code, with Copilot CLI support 'coming soon.' Sending UI back to Figma needs the remote MCP server, available on all Figma seats. This is a genuinely useful drift-detection tool for design system work — not a replacement for a proper token pipeline, but a fast way to catch when shipped UI has quietly diverged from your components.
Coach
pick one shipped component, run it back through an MCP-connected AI tool into Figma, and note where it drifts from your design system spec.
Google's Material Design 3 popularised dynamic, token-based theming back in 2021, and it's still what most design-system setups get measured against. If you're building variables in Figma or tokens in Penpot, M3's structure is worth studying, not because it's new, but because it's proven.
open Material 3's token docs and compare their primitive-vs-role token split against your own Figma or Penpot library — note one gap you could fix this week.
Creative Market's 2026 trend forecast flags 'Glasscore' — blur, glow and translucent layers — as a rising visual style. For teams running token-based design systems, that means more theming flexibility, not just flat colour tokens.
Open your team's (or a starter) design system file and check whether blur/elevation tokens exist — if not, sketch one variant using Figma or Penpot's effect styles.
Some teams are wiring AI coding assistants into their design token workflow, using rules and MCP connections to keep components consistent. It's promising but still fragile in practice.
pick one component in your (or a practice) design system and check whether its tokens are named consistently enough that an AI tool could use them without guessing.
