Articles

Admins can now set a custom AI credit limit for an individual person, and when someone hits that limit they can send a request to their admin to raise it. Design tools now ship with an expense approval flow.

Kaelig Deloumeau-Prigent, co-chair of the W3C Design Tokens Community Group, audited 20 open-source design systems and 6 platforms, logging 187 AI affordances and 157 techniques. 17 ship an official MCP server, 17 ship official agent skills, 14 publish llms.txt. Two ship Figma Code Connect: Carbon and Primer. Design systems are being rebuilt as machine interfaces right now, and the design side of that bridge is the part almost nobody has wired up. Code Connect is still Organization and Enterprise only.

Figma Make now has a properties panel and annotations. Select an element and adjust padding, corner radius, line height, z‑index, or border style with actual controls, or mark a spot on the canvas and describe the change in words, like ​“fade this button in after a 300ms delay”. The quiet part is credits: edits stack up in the chat panel staged and free, and only bill once you apply them. Dragging a slider costs less than explaining the same change to an agent.

“A working demo in your actual codebase beats a Product Requirements Document (PRD) every time.” That’s Software Engineer Ethan Adams on why the nested folders team stopped arguing about permissions in Slack threads and started merging PRs that had to clear one bar: don’t break anything. Imperfect copy, missing functionality, and logical gaps all got fixed later. The making-of companion to the release note above.

Projects are now Folders, and folders finally nest, up to 10 levels deep, each with its own color. Access is inherited from the parent folder unless you explicitly limit it. The catch is in the fine print: Starter gets a single folder and no nesting, and on Professional you can only restrict access on top-level folders, while Organization and Enterprise can lock down any folder at any depth.

(This reminds me how we originally went with ​“servers” instead of ​“folders” in Postmark, and years later had to get creative with UI copy. Still one of my favorite onboarding blocks to this day.)

“Q2 was a record quarter and our first full quarter of AI credit monetization.” CFO Praveer Melwani on $370.1M in revenue, up 48% year-over-year, with Net Dollar Retention at 136% as customers expanded both seats and credit add-ons. Dylan’s line is the same thesis he took to TBPN below: ​“as code gets commoditized and value moves up the stack, the opportunity ahead of us has only grown.”

“Instead of individual assets, you design systems.” Justin Jay Wang, designer at Cursor and before that the person who grew design at OpenAI from 0 to 1, on code as a creative medium for brand work: graphics, charts, posters, logos, animations. Define an idea as a set of rules and you can generate endless variations, dial in parameters, and converge on the strongest one.

“The failure is not in the components; it is in the composition.” Matt Rothenberg, Principal Engineer at Cloudflare, handed three isolated agents the same shadcn/​ui library, the same tokens, the same app shell, and three ordinary settings tickets. Back came tabs, cards, and a long form, all three of which a token linter would happily pass. He then gave the next three runs a named vocabulary and a short page of rules, and they finally read as one product. The agents didn’t cause the drift, they just made it impossible to keep pretending it wasn’t there.

Two criteria do most of the work: cap-centered vertical metrics, and an x‑height at 70–75% of cap height. Hit both and labels optically center in buttons on their own, so a single padding token covers the whole system. Two alternatives are made by this foundry — Unifora and Innovator Grotesk, which I use on my personal website. The other eight are Universal Sans, Plain, SwissNow, Muoto, Aktiv Grotesk, Akkurat, Basier, and CoFo Sans.

Figma reworked auto layout so it behaves like CSS Flexbox at handoff, closing the small gaps that used to force developers into workarounds to match the canvas. The border-box model is now the default: inside strokes count toward layout like a CSS border, outside and center strokes are excluded like an outline, padding is never squeezed below its set value, and auto gap collapses instead of going negative like space-between. New frames get it automatically; existing frames stay on the legacy version until you upgrade, with a revert option through January 2027.

Admins can now download a CSV showing credit use in beta AI features, giving a fuller picture of AI spend and something to forecast against. Organization and Enterprise plans only.

Rauno Freiberg, a design engineer widely respected for his UI craft, keeps a running collection of short notes on the small decisions that make interfaces feel right. One entry works through why an animation delay meant to highlight a scrolled-to message backfired and felt more awkward; another walks through the redesign of cards. It’s the kind of thinking-out-loud that can teach more than any tutorial.

Luis Ouriach makes the provocative case that when LLMs make code cheap to write, edit, and migrate, the contribution model and the component-as-source-of-truth lose their reason to exist. His point is that consistency was always carried by tokens, not components, so a well-defined token set could govern ten different LLM-generated inputs at once. He stops short of full obituary, asking whether components live on as the unit of constraint.

Anthony Hobday on why most design career advice comes from people who don’t hire designers and reflects a single lucky path. The practical core: a five-minute curriculum, ways to look impressive without impressive jobs, and the signs an org genuinely values interface design. His argument that one strong credential can cover for a weak portfolio pairs neatly with ​“Components Are Dead” below — both circling what actually holds value as the job changes.

The team behind Bud (formerly Orchids), an AI-powered platform for building web apps and internal tools, is joining Figma. Bud was built around the idea that AI could ​“democratize the ability to build software,” and the acquisition fits neatly into Figma’s push into that same territory with Figma Make. The announcement doesn’t say what the team will work on, but the direction isn’t hard to guess.

A deep dive into the principles that separate intentional motion from decoration: easing and timing, anticipation, overshoot, follow-through, hold, and settle. The piece makes a compelling case for grounding animation in real-world physics and film editing rather than trending motion work, and lands on a point worth keeping: as AI tools make quality motion faster to produce, skill and restraint matter more, not less.

Luis Ouriach lays out a clear mental model for design systems at scale: before adding a component, ask whether you actually need a structural change or just a value override. The piece covers theming hierarchy across modes, Extended Collections, and direct token updates; when platform separation is worth the headcount cost (often it isn’t); and why you shouldn’t restructure your system for AI tooling until AI tooling can handle multi-file setups.

Contra Labs put four frontier AI models through a rigorous landing page benchmark: nine professional designers, 40 live HTML artifacts, 540 pairwise matchups across typography, layout, palette, and grid. Sol (GPT 5.6) dominated loosely-specified briefs with an 81–83% win rate, praised for capturing tone the brief ​“only gestured at.” Fable (Claude 5) flipped the result on structured briefs, jumping from 31% to 72% client-readiness when given detailed specs. The real finding is that these models have different philosophies: Sol fills ambiguity with its own taste, Fable waits for yours.

Figma’s third annual AI survey, covering 8,403 product builders across 10 markets, lands on a deceptively simple conclusion: AI is most valuable when it’s a team sport. Two years ago, 7% said AI meaningfully changed how their teams collaborate – this year, that number is 41%. The most cited reason is the canvas — where teams can actually riff together rather than trading prompts solo. The cross-functional blurring numbers are striking too: designers participating in development jumped from 21% to 41%, developers doing design work from 44% to 60%. The role boundaries are dissolving faster than most teams have figured out what to do about it.

A large survey of tech workers in 2026 finds the industry splitting into two groups: roughly half feel amplified by AI, while 14% feel destabilized and 12% are simply resentful. Designers and researchers are overrepresented in the fragile half. What’s striking is that the fear isn’t ​“AI will take my job” — only 22% name that. The bigger worry is unsustainable pace and doing more work for the same pay. Career optimism is down, burnout is up, and 53% would actively discourage someone from entering their field.