Articles

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.

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.

Carina B. Velasquez, a Design Systems Lead locked out of AI tools at work, spent a Friday afternoon on her personal laptop with Claude Code and the Figma MCP server. By 6pm she had built Prisme: a complete three-tier token system, four brand themes, and a bidirectional plugin (Prisme Bridge) translating between Token Studio and native Figma variable formats. Her conclusion: ​“AI is amazing, Claude Code built my design system for me, the future is here. That is not what happened. What happened is that I showed up with years of accumulated knowledge, a specific problem I understood deeply, and a clear enough mental model to describe what I wanted with precision. Claude Code was fast; impressively fast, and smart in ways that genuinely surprised me. But it was executing a vision I already had. The intelligence in that Friday afternoon was not artificial.”

Helena Zhang kicks off a series on advanced icon design with a simple but non-obvious principle: dots in icons should be slightly larger than the stroke weight to look optically balanced, a rule borrowed directly from type design. The kind of detail that instantly improves an icon set once you see it.

Figma Make gets two features aimed at consistency and context. Kits bring reusable component sets across projects. Attachments embed files directly in the prototype, reducing context switching during handoff. Both address the real friction of working at scale in Make.

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.

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.

Figma opens the canvas to agents. The use_figma MCP tool lets Claude Code and Codex generate and modify designs grounded in your actual design system. The key distinction from earlier code-to-design experiments: agents work with what your team has already built, making design system quality a direct input to AI output quality. 

Mike Davidson runs the largest design team at Microsoft AI, and shares tips on making it through 2026. The assembly layer of design is being absorbed — button states, data processing, detailed specs. What remains, and what companies are hiring for, is orchestration: running AI and human teams toward a shipping goal. Specific advice on portfolio, job search strategy, and skills worth building.

Worth noting Mike’s scepticizm about data in the above report: ​“Perhaps the data reflects reality, or perhaps design jobs aren’t accurately tracked by this company, but either way, this is not what I or a lot of my colleagues at other companies are seeing. If anything, most cross-functional teams are more underwater on design than on other functions.”

Strong PM and engineering job markets, hockey-stick AI hiring, and one notable flat line: design. Lenny Rachitsky’s fourth job market report makes the case that the tech market is actually healthy — for most roles. The design plateau is the conversation starter in this issue — read the responses from Soleio, Claire Vo, and Cameron Moll below for the community’s reaction.

Luis on what the ​“shadcn-ification” debate is actually about — not the visual uniformity, but the organizational misread: ​“The mistake isn’t in the ingredient. It’s in thinking that having access to good ingredients is the same as knowing how to cook.”

Stakeholders are concluding that the design system infrastructure is done because a great foundation exists. The teams that have spent years practicing design systems understand exactly why that conclusion is dangerous.

TK Kong shares a detailed guide to his workflow with Claude Code and Paper, the design tool built on native HTML/CSS rather than a WebGL canvas. The workflow of agent writing HTML into Paper frames, designer editing on canvas, and agent implementing code is similar to the Figma MCP workflow covered above, but also allows working with existing designs.

The Paper Snapshot Chrome plugin — which copies live web UIs directly into Paper as editable layers — is exactly what I wanted while wondering why Figma won’t make ​“a universal ​“Send to Figma” browser extension”.

Jakub Krehel’s collection of small interface details that compound into a significantly better experience: text-wrap balance, concentric border radius, contextual icon animations, tabular numbers, interruptible animations, optical vs. geometric alignment, and shadows instead of borders. Each one has a live interactive demo. The kind of small details that separate a polished interface from one that just functions.

These details also exist as an installable skill for Claude Code, Codex, and Cursor. Once installed, your AI coding agent automatically applies these principles when building UI.

Kevin Muldoon traces the ​“humans can see between 1 and 10 million colors” claim to its source, and finds it’s an 80-year-old shrug repeated without verification. Designers cite this number constantly; the actual answer is more complicated and more interesting.

The Not Boring Software founder’s five-year reflection on rejecting the venture script in favor of slow success: ​“Slow success means you get to stick with an idea long enough for it to get interesting. Interesting work takes time. Many artists spend their entire life exploring a single technique or topic. Deeper work leads you to deeper meaning leads you to deeper fulfillment.”

Yann-Edern Gillet, design engineer at Linear, revisits his ​“Rosetta Stone” metaphor for design engineering translation through the lens of AI. The central argument: when translation is cheap and instantaneous, the bottleneck shifts from execution to meaning — and the new craft is preserving intent while everything accelerates.

An upcoming interactive exhibit restoring the design moments that shaped software history, from Xerox Alto’s Smalltalk-76 interface to the original ​“slide to unlock” on iPhone. Each restoration requires reverse-engineering details, motion, and behavior from low-quality assets.

Martin Rariga, Founding Product Designer at Equals, breaks down a practical AI-powered design engineering stack: Claude Code for big refactors and complex builds, Cursor for precise edits, and Figma (via MCP) to reference the new design direction while restyling.

Yarden Katz, Product Manager at Figma, walks through the bidirectional workflow between Codex and Figma’s MCP server. The design-to-code direction is the expected one — copy a Figma frame link, paste it into Codex, and the get_​design_​context tool extracts layouts, styles, and components to implement against. The more interesting direction is code-to-canvas: Codex can capture a live running UI and push it back into Figma as editable frames, letting the design side iterate before syncing changes back to code.

Five practical strategies for integrating Slots into a design system, sourced from teams who’ve been testing the feature since Schema 2025. The most actionable tip is to start with the components people detach the most — that’s where Slots will deliver the fastest payoff. I also liked the tip of using pre-filled slots where content is predictable, and empty slots where designers need to add something on their own.