Variable Sync to Repo, from Luis Ouriach, pushes and pulls variable collections between Figma and Git in both directions. Worth pairing with his ​“Adoption is a Red Herring” essay above — both are arguments for treating the design system as infrastructure that has to meet people where they are, including the engineers consuming tokens through a package manager.

The May edition is mostly a demo of Figma’s MCP server, with Amy Lima and Anthony DiSpezio walking through three workflows: code-to-canvas import of a vibe-coded prototype, round-tripping a dark mode so variables stay in sync between code and Figma, and using the pre-installed figma-use-scale skill to generate first-pass directions on a production dashboard. The closing update reel includes vector editing up to 10x faster, memory warnings down 92%, macOS eyedropper now samples anywhere on screen, FigJam MCP can read and write boards (ERDs, architecture diagrams), Make Kit packages your design system’s code for Figma Make, and Weave gets a timeline for video.

Brian Lovin shows the Notion design team’s Prototype Playground, a single Next.js repo on Vercel where every designer gets a namespaced folder and a small set of shared Notion-flavored components. The interesting parts are not the scaffolding but the slash commands and skills layered on top: /figma runs a three-phase loop with the Figma MCP and Chrome DevTools MCP until the build matches the source (~80% on the first try), and a find-icon skill writes its own TypeScript search script after the team got tired of Claude hallucinating ​“search-icon.” See also the Stripe and Vercel pieces below for the same pattern at other companies, as well as another interview with Brian at Dive Club.

Owen Williams, design manager at Stripe, walks Claire Vo through Protodash, the internal prototyping platform he’s been building for 18 months. The V1 was a bundle of Cursor rules plus an MCP server wired to Sail, Stripe’s design system, so any designer can open the repo and build a page without ever touching React or routing. V2 wraps the whole thing in a browser UI running on internal dev boxes, with embedded LLM chat, click-to-annotate feedback, a design review mode, and fidelity toggles (monospace, grayscale) to signal work-in-progress. The same pattern as the Notion and Vercel pieces in this section: production design system plus a thin internal harness, calibrated to one team’s review culture in a way no off-the-shelf tool can be.

Three desktop wins shipped together: search across open and recently closed tabs, content pre-loads so files open faster, and Figma links now open directly in desktop tabs instead of bouncing through the browser. The third one alone removes a daily papercut for anyone who lives in the desktop app.

Server-to-server auth that doesn’t break when someone leaves the company. PLANTs are scoped to the plan, audited centrally, and come with higher rate limits for automation workloads. Important if you maintain Figma integrations as part of internal tooling on an Org or Enterprise plan.

Figma ships a meaningful performance update across the board: 10x faster vector editing, 4x smoother Make frame rates, faster load times, 92% fewer memory warnings. Just the memory side of this update was six months in the making!

Makes now run natively on the Figma mobile app for on-device testing and touch interaction previews. Mobile creation and editing is coming soon.

Pica is a native macOS font manager from Josh Puckett, built for designers who want proper font organization. ​“Organize into collections, test color themes and logos, watch folders, manage what’s installed, and much more.”

Hugo Raymond breaks down Swap Instance vs. Slots as two ends of a control–composability spectrum: Swap Instance hard-locks a single nested component in a fixed position, while Slots act like open containers that accept almost anything and can be freely rearranged. For design system teams, his key point is that the ​“right” choice isn’t about which feature is more powerful, but about how much you trust consumers of your components and whether you fear incorrect composition more than full detachment from the library.

The updated eyedropper is no longer limited to the Figma canvas. On the macOS desktop app, it now samples from anywhere on screen — browsers, design references, anything open.

Gavin Potenza built a Figma plugin that automatically lays out moodboards.

No more jumping to prototype mode just to check a video. Figma now surfaces playback controls on video files directly in Design and Draw — play, pause, fullscreen, and speed controls all on canvas.

Font choices for dense developer tool UIs require different thinking than consumer UI. Anton Lovchikov covers what actually matters — having both sans and mono fonts in the same family, vertical metrics, text rendering, variability — in an article worth saving if you work on data-heavy or developer-facing products.

Yep! Type Foundry introduces Unifora, a uniwidth variable sans-serif superfamily. If you aren’t familiar with uniwidth typefaces, it’s worth checking out details of this project. Two years dedicated to a single constraint: every weight, every width, every slant — same character widths. This solves a real problem for interface designers: text that doesn’t reflow when you switch from regular to bold.

The spring survey from UX Tools shows how fragmented AI adoption actually is in design: a third of designers do no AI-generated code work, a third say it’s almost all of their building, and a third fall somewhere in between. The split is sharpest by role — design engineers are 80.9% AI-assisted; researchers express the most anxiety.

Pair the Emil Kowalski skill with the Jakub Krehel skill above, and you’ve got a solid baseline of design engineering taste baked into your AI coding workflow. Emil’s focus is specifically on animations — spring physics, performance, and interruptibility.

Figma Community now includes Apps, a new category that connects Figma to external tools, including AI systems and third-party products. Find them in Extensions alongside plugins and widgets.

Admins can now purchase additional AI credits in Figma, either as a subscription with volume-based pricing or pay-as-you-go for variable usage. Available now for Organization and Enterprise plans, coming to Professional in May.

Patrick Morgan makes a clean distinction that vibe-coding discourse keeps blurring: prototype code is for exploration, production code is for endurance. He is building a protected prototyping environment using Claude Code, a place where his team can move fast and then deliberately port the right assets across the boundary into production.

There is a clear parallel with how the design team at Notion works. In the recent episode of How I AI, Brian Lovin showed their collaborative ​“prototype playground,” where the entire team can create, share, and iterate on functional prototypes.

That also reminded me of how my team worked a decade ago, back when front-end development was a tad simpler. We had a separate ​“mockups” directory inside the Rails monorepo, where designers prepared static HTML mockups with production-ready CSS and JS. By the time designs were handed off to engineers in a feature branch, all polish and design details were already baked in. The design team must be fairly technical, but there is no going back to handing off Figma files after working this way.