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

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.

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

Stefan went through every Dive Club episode and pulled out everything about portfolios, hiring, and what makes candidates stand out, then distilled it into a skill that audits any product design portfolio.

Yep! Type Foundry introduces Unifora, a uniwidth variable sans-serif superfamily. If you aren’t familiar with uniwidth typefaces, it’s worth checking out details of this project. Two years dedicated to a single constraint: every weight, every width, every slant — same character widths. This solves a real problem for interface designers: text that doesn’t reflow when you switch from regular to bold.

Ridd interviews Kris Puckett, design manager at Stripe and formerly design lead at Mercury and Dropbox, on becoming an AI-native designer by using tools like Claude Code, OpenClaw, and personal AI to ship his own apps, supercharge his design practice, and build highly personal systems for life and work. I’m deeply curious about the last part and can’t wait to dig into his course Neuma on building a personal AI system.

A first look at Config 2026 speakers — AI artist Holly Herndon, creator of the world’s first 3D-printed fashion collection Danit Pele, designer and author Vicki Tan, designer and founder Matthew Ström-Aw, and mathematician and educator Grant Sanderson from 3Blue1Brown. Config returns to San Francisco on June 23–25. Virtual registration is free.

The new Workflow Lab format, showing an end-to-end process, is a smart way to frame the new AI image tools in context. The three new tools (erase object, isolate object, expand image) are genuinely useful for anyone who’s had to leave Figma to do basic cleanup in Photoshop, and Vectorize finally removes a step that’s been a quiet annoyance for years.

Patrick Morgan makes a clean distinction that vibe-coding discourse keeps blurring: prototype code is for exploration, production code is for endurance. He is building a protected prototyping environment using Claude Code, a place where his team can move fast and then deliberately port the right assets across the boundary into production.

There is a clear parallel with how the design team at Notion works. In the recent episode of How I AI, Brian Lovin showed their collaborative ​“prototype playground,” where the entire team can create, share, and iterate on functional prototypes.

That also reminded me of how my team worked a decade ago, back when front-end development was a tad simpler. We had a separate ​“mockups” directory inside the Rails monorepo, where designers prepared static HTML mockups with production-ready CSS and JS. By the time designs were handed off to engineers in a feature branch, all polish and design details were already baked in. The design team must be fairly technical, but there is no going back to handing off Figma files after working this way.

Jenny Wen leads design for Claude at Anthropic, and in the past, she was Director of Design at Figma, where she led the teams behind FigJam and Slides. At Lenny’s podcast, she lays out how AI is collapsing the classic ​“research → mock → iterate” workflow into two main jobs for designers: supporting rapid implementation alongside engineers, and setting shorter 3–6 month product visions that keep a swarm of agents and builders pointed in a coherent direction. Jenny describes the day-to-day at Anthropic as equal parts surfing internal prototypes, pairing with engineers, and doing last-mile implementation herself. She still sees Figma as critical for exploring many directions and fine visual decisions, but treats Claude as her primary stack for long-running tasks and front-end polish.

A live walkthrough of all February launches across Figma products, plus a Q&A with CPO Yuhki Yamashita on where design and software are headed this year. Don’t miss an early preview of Slots, launching in open beta this Thursday.

The Figma Makeathon is officially live! $100,000 in prizes are up for grabs. Check out the guidelines to get started.

Figma’s editorial team revisits the most influential interactions of the last 20 years — alongside stories from designers and builders working now — to see how singular design decisions can grow to define an era, and how the next generation will be shaped by the products we build today.

You can now bulk share resources like files and projects with user groups.

The new tab menu replaces the three dot menu to make it easier to find and manage open files when your tab bar fills up.

The AI team of Gather is joining Figma: ​“Second, our AI team is joining Figma. Over the past year, several team members have been exploring new ideas to make work more pleasant and productive, especially for people designing and building software. As we developed these concepts, we had the opportunity to meet the Figma team, and discovered a remarkable alignment in vision and values. We’re thrilled to announce that this group has entered an agreement to join Figma, where they’ll continue pursuing this important work.”

Weavy’s CEO Itay Schiff walks through his path from 25 years in high‑end VFX to building Weavy, and why Figma acquired it. Weavy lets you package complex node‑based AI flows into simple apps that 200+ teammates can use, baking in brand rules and references by default. It matters if you care about how Figma will operationalize AI beyond one‑off prompts — this is effectively ​“internal tools for creatives” hiding behind a friendly app layer.

Tom Johnson outlines a nine-step AI-heavy design workflow where he starts with messy voice transcripts, uses Claude and tools like Willow, Notion, or Granola to structure the problem, then lets AI generate a deliberately bad but functional app as a scaffold. This matters because it reframes AI’s weakness at UX as a feature: a cheap way to explore directions, expose edge cases, and pressure-test scope before committing to real craft in Figma and a proper engineering handoff.

This is my new favorite palette generator. After working on the Supa Palette plugin for a few years, Angelo Libero went deep on the new standalone tool. It offers an insane level of control — you can start with a preset like Tailwind CSS 4 and add new color palettes following their algorithm, or go into the Curve mode for full control over lightness, chroma, and hue. Accessibility checks are built in, and there are lots of export options.

Jakub Krehel shows how he uses AI every day as a design engineer. My process is very similar, but I still picked up a few things!

Ridd shares his mental model for deciding which tools to reach for when coding with AI. Also available as a Dive Club video.

In this talk from Hatch Conference, Jenny Wen, Design Lead at Anthropic and former Director of Design at Figma, explains why the traditional design process is outdated and no longer works for today’s tools and tech: ​“With AI accelerating prototyping, smaller teams doing more, and craft becoming a key differentiator, rigid processes are failing designers. Jenny shares real examples from Figma and Anthropic that show how great work actually gets made today. Starting from solutions, caring deeply about details, building intuition, skipping steps, and designing for delight.”

Jenny’s talk really resonated with me. Quickly trying and discarding solutions, iterating on details, and relying on intuition is how I prefer to work. Still, without formal collateral such as personas or problem statements, it can feel like taking a shortcut. I went through a phase of producing these artifacts, but often found them more useful for justifying decisions than making them. It finally clicked when I read Alan Cooper’s interaction design bible, ​“About Face,” a decade ago: a lot of these processes came from design consultancies. They have to learn a client’s business, do product discovery, solve a problem, and sell it to stakeholders in a short time before moving to the next client. The longer you work on a product, explore the problem space, and listen to users, the stronger your intuition gets, which lets you fast-forward and compress discovery and design process.

Tom Johnson: ​“It’s literally faster for me to build a concept inside of the actual codebase than it is to work in Figma. But the amount of versions and breadth of the final result is not up to the quality bar that I usually hold. I’m loving the speed, but the output is sloppy at times. So I’ve got this weird flow of Code → Code → Figma → Code → Figma. Repeat, reorder, etc. The issue is that the transition from Figma → code with their MCP is solid. […] But code → Figma… is a terrible flow.”

I often spend more time recreating a particular screen in Figma than actually designing the change. I’ve been beating on the Code Connect drum for a while as it has huge potential for connecting design and code components. Even though it was built to translate components from Figma to code, I don’t see why it wouldn’t work in reverse. Code Connect was announced almost two years ago (way before LLMs and MCPs got powerful), but because it’s locked behind Organization and Enterprise plans, it’s rarely discussed in the community or considered by plugin and tool makers.

Speaking of Tom, in this interview with Jay, he shows the DM he sent to Linear’s CEO to get an interview — and later the portfolio and case studies he used to land the job at Vercel.