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.