Tweets

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.

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.

Miggi flags a new Draw shortcut: hold ⌘ (Ctrl on Windows) with a brush selected to make it your current brush. Pick up where you left off on an illustration, or build a palette right on the canvas.

“Unpopular opinion: I haven’t used Figma text layers in last 3 years. every component uses a text/​heading component instead. buttons, inputs, cards, everything. no raw text layers, no text styles panel.” usrnk1, designer at OpenCode, just convinced their whole team to rebuild around this. Here is why: Figma’s type panel is slow, Auto Layout is built-in, and typography variables just work when type is a component. Good check on how dependent your file is on un-systematized type.

Grace Li lists 7 common design smells in GPT 5.5: huge typefaces with tight tracking, lack of textures, bento boxes with unrelated icons, pill-with-dot in hero sections, gradient keywords, grid background, and rounded cards with three nested cards. ​“TLDR: if you’re vibe coding with GPT 5.5, the easiest wins are: loosen the tracking on your headlines, delete the status pill, and pick one accent color instead of a gradient. That’ll get you out of the uncanny valley before the next model release closes the gap on its own.”

GPT 5.5 is strong at programming, but not great at visuals: ​“Across 5,000+ preference pairs, GPT‑5.5 ranks #13 in Website Arena, #16 in UI Component Arena, and #19 in 3D Design Arena. It loses to Claude Opus 4.7 and Sonnet 4.6, to Gemini 3.1, to GLM 5.1, and to Kimi K2.6.”

“Design is a process, not an artifact. Design is the act of deciding what should exist, why it should exist, and what ​‘right’ looks like before you’ve committed to building it.” A new piece from Jake Albaugh, dev advocate at Figma, articulating what design actually means in 2026. The four-point framing — design is process not artifact, AI accelerates execution not clarity, 100×0 = 0, collaboration amplifies intent.

Especially the second point: ​“The most expensive thing you can do isn’t build something badly. It’s to execute well on the wrong idea.” If you’ve been struggling to explain why polished AI demos can be worse than no demo at all, this is the piece to send.

Ben Blumenrose pushes back on what the whole thread is really arguing about: ​“Product designers do help with UI design systems but that’s a fraction of what they do which also includes what product to build, how it should work, how to ensure people understand how to use it, how to create a brand people love and rally around, how the system should work together, etc etc etc but yes they’ll need to do visual design of UI design systems less so I’ll concede on that.”

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

“I’m increasingly sure that 2026 signals the end of product design as a full-fledged stand-alone function within companies.” Gokul Rajaram makes the controversial maximalist case: startups will outsource design systems to consultants, AI will generate the UI, and design headcount will shrink to 20% of its current size at larger companies.

It’s an argument that reduces design to UI mockup production, which is where most of the responses below push back. The reactions to Claude Design launch in the previous issue have already discussed confusion in terminology, the difference between design practice vs. design production, and made the case that ​“real design is the search for fit between form and context, not the generation of form itself.”

Makes now run natively on the Figma mobile app for on-device testing and touch interaction previews. Mobile creation and editing is coming soon.

Figma ships a meaningful performance update across the board: 10x faster vector editing, 4x smoother Make frame rates, faster load times, 92% fewer memory warnings. Just the memory side of this update was six months in the making!

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.

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

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

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.

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

David Hill explores implementation options for a color system, and Matt Sellers, design lead at Lovable and Reshaped, shares the color token architecture he chose for Lovable’s upcoming design system. The core decision: color-agnostic state overlays (a small set of OKLCH alpha composites) vs. per-intent state tokens (one hover/​pressed value per color × per state × per variant). His case for Option 1 is architectural — the state layer and color layer stay independent, so adding a new intent color requires zero new state tokens. The thread goes deep on OKLCH derivation engines, pseudo-element stacking, and the Figma implementation tradeoffs.