Rather than thinking of a skill as a saved prompt the user or agent can retrieve as needed, think of a skill as a plugin: an extension of the harness.

Designers already have the mental model for all of this, in fact we've had it for decades.

We've reached a point where an idea becomes a prompt and a prompt becomes an app in the store in days. The finished result appears almost instantly, and nobody steps backwards through anything.

The one piece of career advice I'm giving everyone right now is to get a side project.

Screens should always be designed to pause the user so that they make a clear, conscious decision.

I think about it like — if you had to understand what a codebase is from the commit logs, that's kind of what we're doing with agent chats.

Craft isn’t perfectionism. Perfectionism is self-indulgent: it optimizes for the maker’s satisfaction. Craft is empathetic: it optimizes for the person on the other side. We’re not doing art. We’re designing for others.

Some see it as an invigorating return to what brought them to the discipline in the first place, from the joy of creating to finally being able to sweat the details that separate a mediocre product from a great one.

AI leverage becomes workplace pressure when every saved hour simply raises the output expected next time.

Shared-element transitions are useful because they preserve object identity across that break.

Training your design senses is rigorous work, no different from training as a boxer or musician.

"Make it work" is the first 90% of the work. "Make it good" is the other 90%.

What's important to understand about this model is that either of these in isolation would objectively be a small mistake, and caught by the other slices.

Thanks to subgrid, we can nest a grid on the inner items. That means we can have two children positioned at the start and end of the shared grid.

Under partial failure, retry loops can rearrange history. If order, duplication, or staleness matters, retry needs state.

He screenshares dozens of unused concepts, novel art directions, brand identities, and everything in between.

You can write the cleanest AGENTS.md on the internet and still have no idea whether the component that shipped this morning came from your library, or got hand-rolled as a div with a hardcoded blue.

Every AI conference this year was about loops. Here's what that means for design, and a loop you can run in the next ten minutes.

While the performance benefits of bundling absolutely outweigh any negatives, if you have a small amount of JavaScript files, not bundling is perfectly viable.

CSS properties come in two excellent flavors – longhand properties have a direct impact on the element, while shorthand properties take a much more convoluted path.

You cannot build an automatic grader for aesthetic taste, creativity, novelty, etc. because there is no correct answer to grade against.

Speeding up human processes is the least interesting things we can do with the power of AI.

The thing that stays durable and ungradeable is not getting better at solving problems that already have a known answer; it's choosing what to build and judging whether it's any good.

OKHST keeps OKHSL's hue and saturation and replaces lightness with that tone axis.

When you optimize a creative process for raw speed, you don't get better products. You get the same products, just sloppier, sooner and shortsighted.

Federating demands more overhead and operational diligence than any centralised team would, leaving chaos in their wake when federated eventually comes back around to centralisation.