The steady state of a good designer is permanent dissatisfaction with how things are, which is an uncomfortable but essential fuel.

A product can be technically flawless and still fail. If anything in the experience creates a flicker of doubt, a confusing screen, copy that hedges too much, a moment where the user has to stop and wonder what's happening, the trust collapses.

The setup that worked for one team, one product, one platform starts to buckle under the weight of multiple verticals, competing release cycles, and a product org that wants to experiment with everything.

The best version of this component is not the one with the most clever positioning code. It is the one where the panel feels physically attached, behaves predictably, and leaves you with less code to distrust.

This talk unpacks UI density from first principles, moving through Tufte, gestalt psychology, and perceived performance to arrive at a framework you can actually use.

By connecting your agent to a Safari browser window, your agent can emulate what your users experience, giving it the information it needs to debug more autonomously, like access to the DOM, network requests, screenshots, and console output.

The gap between what is possible and what most teams are actually doing is huge.

Creative focus, which leads to creative abundance, starts with prioritizing. In deciding you can't do everything, you can do anything.

The keywords are just presets — every keyword is one spot to leave the handles, and these are not approximations, they are the exact values the browser uses.

A curated collection of agent skills for designers and builders using Codex, Claude, Cursor, and other AI coding agents to build rich user interfaces, frontend systems, agent loops, automations, and reusable workflows.

We talk about Figma's vision for AI, why design is having 'an identity crisis and a renaissance at the same time,' and what it means to use AI to express what's already in your head (not outsource creativity to it).

Apple's prohibition on shapes is a step backward for both usability and creativity in app icons.

Career advice is common amongst designers. Often from respected designers. But I see common problems with some advice.

If you are on a struggling team here is the simplest playbook I know for how to make things better.

A design system is not a static artifact, it is a continuously maintained claim about what a product should look and behave like.

The more the product adapts to me, the more it has to explain which version of me it thinks it is serving.

The most useful part of the Anchor Positioning API, in my opinion, is the fact that it's dynamic.

Today, a lot of creativity and productivity happen onscreen, but our interfaces do not often respect the fingers the same way older instruments did.

In this interview you will see how Carol Lei designed Command which is Mercury's agentic operation system for banking.

You need a rich set of concepts in your mind to think creatively and fluently about how to move something forward.

The demos show you one clean layer working under perfect conditions. Your actual work needs three or four layers stacked together, and nobody shows you the stack, because the stack is where it gets messy and half-solved.

A design system can only raise the quality floor. It sets the baseline below which nothing should ship.

Production is being commoditized much much faster than taste. It's an open question of whether AI will be able to produce 'taste.' For now, the ability to create qualitatively new judgments remains distinctly human.