Dylan Field on the newest addition to Figma’s product line: ​“Figma has acquired Weavy, a platform that brings generative AI and professional editing tools into the open canvas. As Figma Weave, the company will help build out image, video, animation, motion design, and VFX media generation and editing capability on the Figma platform.”

In A Match Made in Heaven, Weavy’s early investor, Ben Blumenrose from Designer Fund, shared three key features of their product approach that make for a very powerful tool — being model agnostic, exposing process, and working as an aggregator.

I’ve been waiting for this video and kept thinking about it long after watching. To kick off his new series This is taste, Tommy Geoco flew to Kalamazoo, MI, to spend two days with Ridd. His Dive Club interviews show where the puck is going to be for the design industry and have been my most recommended resource for a long time. Tommy did a great job showing the actual person behind the online persona through his environment, family, motivation, and process of building the Inflight and Dive Club. Can’t wait for the future episodes of the series!

Earlier this year, Grammarly acquired collaborative workspace Coda and email app Superhuman, with the CEO from Coda stepping into the role of CEO for Grammarly and the entire company later changing its name to Superhuman. Smith & Diction developed an interactive identity with motion design at its core, while the brand architecture of the new company was evolving every day. The new icon system by Helena Zhang and custom pattern generators made in Figma Make show an incredible attention to detail from this team.

Ridd led a panel about how AI is shifting design workflows, where Nick Pattison from Primary, Pranathi Peri from v0 (Vercel), and Henry Modisett from Perplexity were sharing how they use AI for prototyping and exploring ideas. One pattern that stood out to me between this panel and the above Superhuman rebrand case study is how designers now create specialized one-off tools for generating patterns, brand assets, or special effects. Personal software will only get more and more common.

The new all-in-one Affinity app, combining Pixel, Vector, and Layout, is now completely free. Only AI tools are locked behind the Canva premium plans — I’m wary of free tools, but this is an interesting strategy.

Tom Johnson has an in-depth thread on how dithering works, how it breaks, and some tools to get it to look best.

A summary of everything Figma announced at Schema to help teams design for the AI era. Extended collections are a new way to manage multi-brand design systems, where authors can release a simple whitelabeled version of their design system that designers across the company can extend with their own themes, publish, and reuse. Slots let you add your own layers within instances and easily specify which instances a slot accepts, allowing for both increased usability and compliance with your design system. Check designs linter matches your raw values with their corresponding variables. Finally, the team completed a massive rewrite of the architecture for massive performance gains.

In addition to new design features, Figma has been working hard to bring context from your codebase into your design system. With the new Code Connect UI, users can connect Figma directly to their GitHub repositories and use the new AI suggestions feature to quickly find the right code file to map to Figma components — no coding necessary. The MCP server is out of beta and generally available — now you can add guidelines for how AI models should adhere to your design system. Make kits let you generate React code components and CSS files for your styles and variables, then package those outputs for use in Figma Make. Additionally, Figma announced NPM package imports, native importing and exporting of variables, simplifying authoring experience for collection, and increased variable modes.

Watch the Schema keynote to see demos and learn more about all the features Figma just launched.

It’s wild how long it takes to build some of these larger features. Jacob Miller, a Product Manager for the Design Systems and AI team at Figma, shares an early exploration for slots from 3 years ago! I’ve been begging Jacob for slots at this year’s Config and got a feeling that they’re already working on it, but still it will be launched only next year.

If you wonder why it’s taking so long, Jacob wrote an insightful reply on how his team approaches these changes: ​“With design systems features, we have to plan them years in advance. Things like components, variables, and styles are used on the order of billions — one wrong move will result in breaking files and ruining critical design work. We have to be methodical. […] With DS features, I’m usually planning them around 3 years in advance.”

If you’re curious how slots and other new features will work, check out Jacob’s AMA.

With variables now supporting extended collections, Luis Ouriach put together structure recommendations for multi-brand systems.

Also fun to see how Figma uses extended collection for its own multi-brand system.

More Variable modes for people on Pro and Org plans. Instead of 4 modes, Pro plans now offer 10 and Org plans 20.

“Code Connect UI lets you map design components in your Figma libraries to the corresponding code components in your repository. These mappings enhance the Figma MCP server by giving AI agents direct references to your code, enabling more accurate implementation guidance.”

A smart technique for debugging design system usage that will nicely complement the new Check designs linter: ​“I wanted to see which parts of my designs were using tokens and components from my design system, just by looking at the canvas. The solution: an additional variable mode paired with an outline component. Toggle it on, and everything using the system lights up: tokens in bright cyan, components with dashed outlines. Everything else stays unchanged.”

Luis explores a few approaches for handling components used in multiple design files but not yet ready for the main library. Delaying the creation of components until later doesn’t scale. Using naming conventions and canvas organization to separate local components doesn’t help with bringing them to another file. The best solution is to create Staging Libraries, ​“where your specific team, feature, squad, whatever can create what is in effect an extension of the system for your specific piece of work.” When the component needs to be used across multiple files, it can be pushed from the local level to the Staging library, and once it’s ready to become a part of the design system, it can be moved to the Global library.