Dylan Field responds to Gal Shir’s ​“quitting design” post that made a splash in the design community this week and supports findings in Lenny’s survey. He points to the recurring psychological loop that plays out every time a new AI model drops: existential crisis, experimentation, recalibration, repeat. His standing argument is that the attention economy makes design more valuable, not less, because anyone can prompt their way to average, and average doesn’t stand out. ​“This is the moment to be more bold, to take more creative risk, to double down on the power of design.”

Meng To sits down with Ridd at Dive Club for a 35-minute screen-share walkthrough of his current Codex workflow. He’s no longer opening Figma to create anything new — all design exploration, prototyping, and iteration happens in Codex, starting from screenshots and referencing his own past work as context. A few specific tactics stand out: using GPT Image 2 to generate UI concepts that then get turned into HTML, feeding a video of an animation to the AI and asking it to describe the right prompt to recreate it, and using design​.md files as a portable style guide that encodes years of taste into something the model can actually read.

Luis Ouriach lays out a clear mental model for design systems at scale: before adding a component, ask whether you actually need a structural change or just a value override. The piece covers theming hierarchy across modes, Extended Collections, and direct token updates; when platform separation is worth the headcount cost (often it isn’t); and why you shouldn’t restructure your system for AI tooling until AI tooling can handle multi-file setups.

A short demo from Miggi on Riffs, now in beta on Figma Community. You can post up to five frames or export a motion frame as video straight from a file, add a description, and publish it to your profile. Figma Community becoming the new Dribbble wasn’t on my bingo card for this year!

Figma Community just got a new content type. Alicia Kranjc, Product Manager at Figma, walks through how to publish a Weave workflow to Community so anyone can find, copy, and run it. The demo workflow takes a single image and produces three video hero variations for different websites. Something that took its creator hours to build takes someone else a couple of minutes to use.

New weekly live show by Ridd and Tommy Geoco, focused on design, tools, and the people behind the software.

Kyle Shepherd turned the entire Dive Club archive into a searchable AI Q&A. Ask a question, get an answer pulled from auto-transcribed podcast and video content, with the source clip linked for verification. Handy if you remember a concept from an episode but can’t remember which one.

Joey Banks, founder of Baseline Design, joins Code & Pixels to talk about what it actually feels like to navigate AI tooling right now. His ​“You’re Not Behind” post came out of his own anxiety the weekend Claude Design launched, and this conversation unpacks it honestly. The most interesting moment: Joey spent 102 prompts vibe-coding a to-do app in Cursor and found himself checking Slack while the model ran, feeling further from the output than he ever does in Figma.

Nikolas Klein, PM on Figma Make, walks through how Code Layers work in practice. The mental model is deliberately familiar: duplicate a code layer to explore alternatives the same way you’d duplicate a frame. What’s new is that those alternatives are working experiences your team can interact with, comment on, and prompt against — all in the same file. The extract-to-design flow is the detail worth pausing on: you can pull any state or screen from the code layer back into editable Figma layers, make visual edits, then push the changes back to the code layer and to your repo. Code Layers are in closed beta with a signup for early access.

Meng To, founder of Design+Code, shares his first hands-on session with Figma Motion. The tutorial runs through basic animation, auto keyframes, and agent-prompted stagger animation, then pivots to shaders — which is where it gets interesting: he animates dither and lens distortion settings over the timeline, and builds a custom Matrix-style shader from scratch using the agent with a screenshot as input. A good complement to the official Figma tutorial below, which focuses on design systems and 3D transforms — this one is messier and more exploratory, which makes it easier to follow along.

Ridd digs into everything that launched at Config 2026 with Loredana Crisan, Figma’s Chief Design Officer. The key product philosophy she outlines: AI gets you to 70% — on shader effects, on motion — then you mold the rest. Weave, the node-based tool Figma acquired last year, is the clearest expression of this systems-over-screens direction: you build a workflow that produces a visual system, and the workflow is ​“the special sauce.” The big bet isn’t AI replacing the designer’s hand; it’s making AI a precision tool, which Loredana argues is still ahead of where the technology actually is.

Dylan Field’s own Config 2026 recap, covering all six announcements at once: Code Layers, Figma Motion, Shader fills and effects, Generative Plugins, Weave Tools, and the Figma Agent. His framing: ​“AI has lowered the floor, but it has not raised the ceiling. Designers, creatives, builders: You will raise the ceiling.” A deliberate pushback against the narrative that AI replaces creative work.

Dylan Field opens Config 2026 by settling the design-vs-code debate once and for all: ​“Code is not the opposite of design. Code is material for design.” The keynote’s headline feature, Code Layers, puts live interactive code directly on the canvas alongside design layers, with a shared agent chat so teams can explore and riff together rather than each going a hundred prompts deep alone. From the same team: Figma Motion in beta, a full timeline-based motion tool with shader effects, 3D transforms, and export to MP4, GIF, and animated SVG. Worth watching in full: the Weave AI tools and custom shader section is genuinely impressive, and the generative plugin demos near the end show where the platform is heading.

“AI tends to pull us in deep before we’ve gone wide, and I think that’s a mistake.” Joey Banks’s recap of Config 2026 is a good summary of the features, but the reason to read it is this thread running underneath: the entire Figma canvas strategy this year is really an argument for staying in the messy middle rather than reaching for the polished AI output too fast.

Christine Vallaure walks through how A2UI, a Google-initiated open protocol, turns a designer’s component catalog into the sole source of truth for AI-generated interfaces. The AI assembles screens fresh for each user request, but it can only name components that already exist in the catalog — so the quality of every screen traces directly back to design decisions made upstream. The interesting flip: the careful work designers often do invisibly, states, tokens, semantic naming, accessibility, stops being a tax and becomes the engine.

Jake Albaugh, Developer Advocate at Figma, walks through setting up Code Connect from scratch — the NPM package, the config file, and mapping design properties to production code properties. The real payoff comes when he shows the before/​after through the MCP server: without Code Connect, an agent sees a flood of raw style data; with it, it sees clean, minimal component code it can actually act on. Unfortunately, Code Connect is still not available on the Pro plan.

Marcin Wichary, Design Architect at Figma, made this interactive essay about fingers, latency, and why our interfaces still fail the hands using them. Starting with 1890s typists who routinely hit 70 wpm when scientists said 40 was the ceiling, he traces a direct line from terminal echo buffers and UI blocking to Notes on a Mac that can’t keep up with your typing in 2026. The embedded demos — where you feel the difference between a blocked UI and a parallel thread — do more to explain debouncing and latency than any amount of text could. This essay is a fantastic companion to Marcin’s Unsung blog on software craft and quality.

Christine Vallaure walks through what ​“agentic design” actually means once an agent is reading your Figma file instead of a developer. The key shift: all the design-system hygiene we used to wave off as optional — primitives, semantic naming, modes, slots, props, and especially the long-neglected component Description field — now becomes load-bearing, because agents read literally and never ask you over coffee what you meant. A solid 10-minute orientation before diving into the more hands-on MCP pieces.

The Community profile redesign adds role, experience, tech stack, pinned work with images and links, and social channels. Combined with the FigPal customization, it reads less like a profile page and more like a creator landing page. Figma clearly wants Community to function as a discovery layer for designers, not just for resources.

Soleio’s guest is Rasmus Andersson: founding designer of Spotify, one of Figma’s first designers, co-creator of GraphQL, and creator of Inter. The part that stayed with me is his description of how Figma operated: one person on one problem for a year, sometimes binned at the end, while shipping something visible every month. He also makes a case that the production side of design — the part AI is eating fastest — was never actually the hard part. What’s left is the intention. The other link in this section is Soleio’s talk on the geometry of luck, making this pair worth watching together.