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

Yuhki Yamashita, Figma’s CPO, lays out the company’s worldview behind the Design Agent, Make, and Weave launches. When generating a working app is cheap, the bottleneck moves upstream: choosing the right direction and shaping it with care. He proposes a ​“go broad and deep at the same time” workflow, where Make spins up parallel prototypes and Weave becomes the room where teams compare, argue, and refine. A tidy thesis for a launch week, and the tools clearly exist to enact it.

TBPN’s 20-minute interview with Dylan Field on the day of the Design Agent launch.

Dan Hollick (design engineer at Cursor, formerly Tailwind and Raycast) shares a video walkthrough of the custom tooling he built to produce the illustrations for his book Making Software. This is what ​“designing the tool that designs the work” looks like in practice.

Luis Ouriach makes the case against single-number design system adoption metrics. His argument: one number collapses three things that should stay separate, across artifacts (a brand token and a complex data table component need different definitions of ​“used well”), surfaces (a logged-in dashboard component has no business on a sign-up screen), and people (a marketer, a senior product designer, and a front-end engineer all want different things from the same system). The throughline is that compliance with a benchmark is not the same as value, and most design system dashboards are quietly measuring the wrong one.

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

“The first casualty won’t be design. It’s the deliverable.” Tommy Geoco backs it with numbers: a recent State of Prototyping survey of 1,478 design engineers finds 80.9% spending most of their week vibe coding, and 59% having shipped their own internal tool in the last six months. ​“The design function isn’t being eliminated. It’s absorbing engineering.”

“The role of someone who figures out what needs to exist, why, how it should work, how it should be positioned, differentiated and made memorable has never been more in demand.” Josh Puckett (also the maker of Pica included below) separates the deliverable from the practice: he agrees the mockup-maker role is going away, but argues the ​“what should this be and why?” role is more in demand than ever.

A useful companion to Google’s announcement above. Meng To shares 15 takeaways from actually using the format: when to Remix vs. Iterate, how to treat DESIGN​.md as ​“reusable project memory,” and why curation is part of the design process. The most actionable takeaway: ​“Start with DESIGN​.md, generate the first design, remix and expand it, create section variations, move into a builder, then assemble the full site.” Don’t miss his video tutorial on turning a DESIGN​.md into landing pages, mobile screens, and motion design.

Karri Saarinen, CEO of Linear, writes one of the more grounded takes on AI’s current state. Linear’s cloud agent now fixes more than 1,000 issues per month, but Karri is clear that hard problems remain hard and design tools are still challenging to use. On having a design tool operate directly on the production codebase: ​“A lot of the design work I do is not production design. I am not trying to implement the final version or test every edge case. Most design work is about making decisions, understanding the problem, and finding the fit. That process generates many variations and messy ideas.”

The expertise paradox section is the most useful: ​“AI often feels most impressive in domains where you know the least.” Expertise makes AI harder to use but also more valuable, because experts know how to steer, constrain, and evaluate the output.

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

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.

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.

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.

Dylan Field in an interview with Peter Yang argues that AI will massively expand what’s possible in design, but the enduring edge for humans is judgment: taste, craft, and point of view, plus the ability to use AI as an iterative partner rather than a one-shot generator.

A thorough, practical guide from Christine Vallaure on what design systems need to work well with agents. Five things most systems are missing: semantic tokens, full state coverage, slot-based composition, exact Figma-to-code property matching, and token-based auto layout. Pairs well with the Brad Frost video — both cover the same design system moment from different angles.

Christine Vallaure built a five-person AI editorial team from one text file and seven lines. Five named agents: Rachel brings reader feedback, Joan brings numbers, Caitlin flags voice problems, Miranda raises buyer concerns, and Elke runs the room as editor in chief. Technically one model shifting between personas inside a single Claude conversation, but behaviorally a team critique. The most concrete personal account I’ve read of what agentic AI actually feels like to operate as a solo creator.

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

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.