There isn’t just one way to build. For the best ideas to move forward, we need the power of code and the canvas. Claude Code to Figma is just one way we’re giving builders more choice.

Modern frontend development has shifted heavily toward custom design systems. Teams no longer want off-the-shelf UI kits that dictate colors, spacing, and layout. Instead, they want full control over styling while still getting:

Claude Sonnet 4.6 is our most capable Sonnet model yet. It’s a full upgrade of the model’s skills across coding, computer use, long-context reasoning, agent planning, knowledge work, and design. Sonnet 4.6 also features a 1M token context window in beta.

AI agents generate 98% more PRs but reviews take 91% longer. The work didn’t disappear — it moved. A synthesis of eight perspectives on where it actually went.

As an aside, I received a lot of positive feedback on that essay, thank you! (And I’m sorry that I still haven’t responded to some of you. My inbox is a disaster for a variety of reasons.) The wild thing is that I received zero negative feedback. My pet theory is that it was simply too long and nuanced for casual drive-by critics and that anyone who stuck with it did so…

Build a smooth horizontal parallax gallery in DOM/CSS/JS, then upgrade it to GPU-powered WebGL (Three.js) with shaders.

But in my early career, I worked as a full-stack developer and designer at creative agencies. Back then, we called it being a “webmaster.” You did everything: design, frontend, backend, deployments, the whole stack.

If you’re trying to break into software engineering right now, in 2026, in the age of AI coding assistants, you need to understand something: the bar hasn’t just moved. It’s been launched into orbit.

Unlike the scrollable scroll-state queries, scrolled remembers the last direction you scrolled into, which you can use to build “hidey bars”: when scrolling down (or having scrolled down), the hidey bar hides itself. When then scrolling back up, the hidey bar reveals itself.

Prescriptive class name conventions are no longer enough to keep CSS maintainable in a world of increasingly complex interfaces. Can the new @scope rule finally give developers the confidence to write CSS that can keep up with modern front ends?