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.

Stephen Haney announces QuiverAI’s SVG generation inside Paper – vector output from text or references, aimed at logos, illustrations, and animations. QuiverAI​’s models have been on my radar since Dann Petty joined the team as a Founding Product Designer.

Hannah Hearth runs a tooling Show and Tell with her team at Vercel and writes up the results: Codex + Claude pair programming, Conductor for parallel agent threads, UI Fork for in-browser variant exploration, and Cleanshot’s Pin tool still earning its place.

Kris Puckett, Design Manager at Stripe, spent months building Epilogue, a real iOS app with 14,000 lines of Swift, entirely through conversation with Claude. This essay is a specific and honest account of what the designer-building-with-AI experience actually looks like: what broke, what he learned about asking precise questions, what ​“vague frustration keeps you stuck, specific confusion gets you answers” actually looks like in practice. ​“I realized the bottleneck was never coding ability. It was articulation. The ability to describe what I wanted clearly enough that something else could build it.”

“Designers have always (and will always) answer the question ​‘What’s worth making?’ ” Joel Lewenstein, Head of Design at Anthropic, argues that as the cost of software drops, the most important decisions shift from ​“can we make this?” to ​“should we?” Design, in his framing, is what narrows the possibility space fast enough to keep up with the speed of delivery. He describes Claude Design as a tool for getting ideas ​“good enough to move discussion forward,” cutting idea-to-internal-feedback time from days to hours.

“A state-of-the-art image model that can take on complex visual tasks and produce precise, immediately usable visuals, with sharper editing, richer layouts, and thinking-level intelligence.” OpenAI’s second-generation image model promises a step change in instruction following, precise object placement, dense text rendering, and cross-aspect-ratio generation.

Jacob Miller left the PM role at Figma to build Diffui, a new way to approach the design to dev process with AI. In this thread, he compares designs generated by his tool and Claude Design. One is more expressive and diverse, another is more polished and organized. The point is not that one is better than another, but how can we combine different approaches and tools to get to the most interesting result.

Paul Stamatiou with the first impression most experienced designers will relate to: Claude Design didn’t land on first try, but the trajectory outlined by Sam Henri Gold is unmistakable. Lately, I’ve been working in pretty much the same way: ​“So much of my iteration happens directly in the code, Figma is where the direction gets sorted out, then it gets a million iterations and refinements in code. The last thing a designer on a team moving at hyperspeed wants to do is backport designs in code back to Figma to maintain a single source of truth.”

Sam Henri Gold argues that Figma’s decade of components, variables, and tokens has become an overgrown, pre‑agentic system that no one would design from scratch now that LLMs work directly with code. He frames Claude Design as ​“truth to materials”: HTML/JS-first, tightly coupled to Claude Code, and better aligned with a future where the source of truth moves back into repositories instead of opaque design files. The interesting provocation is his prediction that tooling will split in two—agentic, code-native tools like Claude Design on one side and pure, system-free exploration playgrounds on the other—leaving Figma facing its own ​“Sketch moment” unless it radically rethinks what it’s for.

Ben Blumenrose offers a useful counterpoint to the critical takes: ​“What if it’s not a Claude Design vs. Canva vs. Figma vs. xxx but a ​‘yes and’ as millions more people are exposed to design and use this accessible tool to begin a journey into being better at type, color, composition, effective communication, building great experiences, etc?”

Soleio (designer, angel investor) draws a three-way taxonomy to cut through the noise: production design gets automated on economic grounds; strategic design expands its medium set to include live production experiments iterated by agents; and exploratory design actually grows in importance because humans and machines together can traverse a far larger combinatorial space of novel forms. The real competitive edge, he argues, shifts to ​“problem-finders” who build new systems for channeling desire: ​“The inputs and systems we create to find opportunities will reward the most intrepid problem-finders. Design stops being a method of sitting and ruminating on possible forms or solution spaces. Design becomes active, research-based, and built around speed of discovery and expression.”

Anthropic launches Claude Design, a new product that lets you collaborate with Claude to create designs, prototypes, slides, and more. Powered by Claude Opus 4.7, it reads your codebase and design files during onboarding to build your team’s design system automatically, then applies it to every project. This release kicked off many interesting conversations in the community, some of which I gathered below.

Rasmus Andersson, creator of Inter and former principal designer at Figma, draws the sharpest distinction in the launch coverage: ​“This is really neat but it’s not a design tool as much as it’s a design production tool. The practice of design is mostly about what comes before production.”

Karri Saarinen, CEO of Linear, makes a similar point that AI design tools conflate producing interfaces with designing them, leaning on Christopher Alexander’s ​“Notes on the Synthesis of Form” to make the case that real design is the search for fit between form and context, not the generation of form itself. He points to a visible symptom: AI-assisted products that look polished but unravel under use, full of decisions that were never genuinely worked through.

Figma and Anthropic demonstrate the Claude Code roundtrip in both directions. Write to Canvas lets Claude Code create and modify designs directly in Figma; Code to Canvas brings live browser UI back in as editable frames. Worth watching alongside the Agents on Canvas blog post and Figma Skills page for the full picture of what this workflow ecosystem looks like.

Ed Bayes leads design on Codex at OpenAI; Gui Seiz leads AI product design at Figma. Together with Aakash Gupta, they give a rare behind-the-scenes look at what the Codex-to-Figma MCP integration actually changed inside their teams. The workflow is genuinely bidirectional, code and canvas reading from each other directly. The most concrete signal that something shifted: designers are working directly in staging.

Brad Frost and Chromatic cofounder Dominic Nguyen walk through how Storybook’s new MCP exposes design systems for agents to use reliably. The key insight: AI doesn’t invent states your components don’t have — it amplifies what’s documented. Coverage, completeness, and constraints are now load-bearing.

Steve Schoger from Tailwind Labs recorded a step-by-step walkthrough on taking an AI-designed dashboard and turning it into something that looks like it was designed by a pro.

Steve Schoger is a design cofounder of Tailwind CSS and a recent Claude Code convert. In this walkthrough, he is using Claude Code as his main design tool to turn a generic AI-generated marketing page into a polished Tailwind UI, with lots of concrete tweaks to typography, spacing, borders, and layout.

Jenny Wen, who brought FigJam from concept to launch at Figma and is now design lead at Anthropic, talks at the Double Diamond podcast about designing Claude itself. The key difference from traditional software: ​“When you are designing now with these LLMs, you basically can’t map out all those flows. You basically just have these core primitives and these specific states that you want the model to get to, but the possibilities in which the user can actually interact with the model are just basically endless.”