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.”

Figma’s third annual AI survey, covering 8,403 product builders across 10 markets, lands on a deceptively simple conclusion: AI is most valuable when it’s a team sport. Two years ago, 7% said AI meaningfully changed how their teams collaborate – this year, that number is 41%. The most cited reason is the canvas — where teams can actually riff together rather than trading prompts solo. The cross-functional blurring numbers are striking too: designers participating in development jumped from 21% to 41%, developers doing design work from 44% to 60%. The role boundaries are dissolving faster than most teams have figured out what to do about it.

Contra Labs put four frontier AI models through a rigorous landing page benchmark: nine professional designers, 40 live HTML artifacts, 540 pairwise matchups across typography, layout, palette, and grid. Sol (GPT 5.6) dominated loosely-specified briefs with an 81–83% win rate, praised for capturing tone the brief ​“only gestured at.” Fable (Claude 5) flipped the result on structured briefs, jumping from 31% to 72% client-readiness when given detailed specs. The real finding is that these models have different philosophies: Sol fills ambiguity with its own taste, Fable waits for yours.

Alex Barashkov of Pixel Point explains why his team stopped wrestling with Figma for certain jobs — procedural art, custom animations, branded asset generators — and started shipping dedicated apps instead. Toolcraft sets up a React starter with opinionated canvas behavior, a font picker, Lightroom-style sliders, and built-in AI instructions that prevent the agent from quietly breaking things it wasn’t asked to touch.

Figma’s AI image editing now runs in parallel. You can kick off multiple edits from the toolbar and keep working while they process, with loading indicators for each. Small change, noticeable difference if you’re doing any volume of AI image work.

Weave Tools are pre-built AI actions that run directly inside Figma from a new Tools panel, sitting alongside plugins and widgets. Moran, Weave’s designer advocate, built the initial set of 30+ tools, covering things like aspect ratio changes, on-brand icon generation, and logo placement on products. The ​“add logo to product” demo is a good proxy for what makes this interesting: it’s not a one-shot prompt, but a multi-step chained workflow under the hood, which is why the output actually holds up — logo bending into the fabric wrinkles of a hoodie. All that complexity is hidden.

The team behind Bud (formerly Orchids), an AI-powered platform for building web apps and internal tools, is joining Figma. Bud was built around the idea that AI could ​“democratize the ability to build software,” and the acquisition fits neatly into Figma’s push into that same territory with Figma Make. The announcement doesn’t say what the team will work on, but the direction isn’t hard to guess.

A large survey of tech workers in 2026 finds the industry splitting into two groups: roughly half feel amplified by AI, while 14% feel destabilized and 12% are simply resentful. Designers and researchers are overrepresented in the fragile half. What’s striking is that the fear isn’t ​“AI will take my job” — only 22% name that. The bigger worry is unsustainable pace and doing more work for the same pay. Career optimism is down, burnout is up, and 53% would actively discourage someone from entering their field.

Carol, a designer at Mercury, walks through how she designed Mercury Command, the AI-powered interface being built into Mercury’s banking dashboard. The interesting part is her argument that agentic design fundamentally breaks the Figma-first workflow. Because the output is non-deterministic, she had to prototype in Cursor with a live system prompt to understand what the experience would actually feel like. ​“The system prompt in a way is the product,” she says.

Ryo Lu, Head of Design at Cursor, gave the standout talk at Cursor’s first conference, Compile. The title is ​“Closer to the Material,” and the core argument lands hard: as AI makes execution cheaper, the real risk is that humans become approvers rather than authors — people who accept or reject outputs without ever being inside the decision. He distinguishes between output (which ends the loop) and material (which invites you back in), and argues that the future he wants is tools that keep people close enough to the work to still have judgment. A sharp and honest take on the AI-design moment, and easy to connect to what Figma is navigating with its own agent features right now.

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.

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.

The Figma design agent can now search the web. Type ​“search the web”, add a URL, or use the plus menu in the agent chat to pull in live content, reference real design patterns, and replace placeholder text and images with actual material.

Meaghan Choi, lead designer on Claude Code, walks through her actual daily setup at a Dive Club talk in NYC: always in a worktree so parallel Claudes don’t overwrite each other, always in auto mode so the classifier handles permission prompts, and a custom /prototype skill that spins up five HTML variants of any feature and picks one with reasoning before she even looks. She demos it by asking Claude to add autocomplete to Excalidraw with no design spec, then has it open a PR with a screenshot recorded via Claude in Chrome. Her line that lands: she doesn’t review Claude’s terminal output anymore, she reviews the PR.

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.

Matt Colyer, Figma’s director of product management for developers, makes the case on Dan Shipper’s AI & I podcast that the SaaS apocalypse narrative has it exactly backwards. He’s been running his own agents for two years and is buying more software subscriptions than ever, because shipping and maintaining a personal agent teaches you fast why people pay for someone else to run it. The more interesting half is about design specifically: chat is linear, which makes it good at converging on a single direction but terrible at generating lots of options. Figma’s on-canvas agent is a first attempt at the divergent side — letting you branch frames in different directions, then bring in a convergent agent to cluster them. He also walks through how the MCP server closes the code-to-design loop, and why ​“review” has quietly become the biggest bottleneck in AI-assisted product work.

An official Figma walkthrough of the agent (currently in beta, rolling out since May 20) through three phases of a real design project: exploring directions, processing feedback, and automating repetitive updates. The most practical detail: the agent works with your connected design system from the first prompt, so generated screens use your actual components, variables, and styles rather than placeholders. Also worth trying a prompt like ​“what would a growth-focused PM say about these designs?” to simulate stakeholder pushback before the actual review.

Miggi compiles a thread of agent prompt examples paired with screen recordings of each one running.

Make can now connect to a local repo and edit your real production code, not just a sandboxed project. Designers point at an element, adjust properties or leave an annotation, and the agent finds the relevant code, commits the change, and opens a PR through standard GitHub flow (SSH for other providers). It also handles dependency installs and spins up the dev server for you. Closed beta on the Mac Beta desktop app and beta usage doesn’t burn credits.

The on-camera companion to the Make-on-Local-Code launch. The most interesting bits beyond the blog: a Figma editing panel inside Make for direct style changes, multi-element annotations pinned to the rendered screen (including voice mode), and MCP server support for resolving merge conflicts and CI failures. The pitch is that designers get agency to ship the change themselves while the engineer’s review workflow stays untouched – apple for early access.