Claire used Claude Design to redesign my newsletter. I think it's a winner. lennys-product-zoneee.vercel…

"Surprisingly, occupations with higher exposure to AI have grown faster than least-exposed ones, not slower." Not surprising! Productivity growth -> economic growth -> job growth.

I built and launched an iOS app using nothing but @claudeai, Figma MCP, and @garrytan's GStack. The idea isn’t a novel one, and the design itself borrows a lot of inspiration, but I was focused entirely on becoming an expert craftsman with the tools and processes I expect my own design team to be leveraging. In @stewartbrand's book Maintenance: Of Everything, he includes a quote from Matthew Crawford’s Shop Class as Soulcraft about becoming "masters of our stuff." We need “a basic intelligibility of our possessions: in their provenance, in their principles of operation, in their logic of repair and maintenance.” That simple remark is what kicked off my mission. You can't lead people through changes you've never experienced and tools you've never touched. And with the scale and speed of change, I don't think leaders can ever again afford to outsource their understanding. Time to roll up your sleeves.

we'll look at yesterday as the start of a new class of design tools: tools for convergence. visual design is now commoditized. every prompt gives you something that's 'good enough' and a probable solution. in a sea of options, the best tools will help you decide what you want.

the win isn't automating creativity away. it's removing the translation layer between idea, design, and shipped software. the magic happens in exploration, instinct, and discovery—not in generated output. eliminate the handoff. not the creativity.

Here is a trick to review your AI-generated code: Have two separate Claude Code sessions (open Claude in different terminals). • Use the first session to write the code. • Use the second session to review that code. The reviewer doesn't know anything about the process or shortcuts used by the session that wrote the code. This makes it somewhat unbiased. I also use this to write my tests: • First session writes the test • Second session writes the code that passes that test

Interesting to see what the Cursor design team can do given a clean start. Cursor 3 looks and works well. (I do wish it was two separate apps though. Cursor Code and Cursor Agents. I need both)

We’re adding more visibility into where your Claude Code usage goes. Run /usage to see a breakdown of what's driving it: parallel sessions, subagents, cache misses, long context, plus tips to optimize each.

someone reminded me that i haven't shared details abt my process for the draw with claude project yet. i put together an overview here! lelezhang.design/drawing

I'm trying to figure out when a watch was made. Initially ChatGPT thought 1966 and Google 1965. I tried feeding their suggestions to one another, but both agreed and swapped. So then I tried going back to their original answers, and both swapped again.

2012: figma makes design collaborative. 2026: still clicking through admin panels... everyone's racing to connect design<>code, but nobody's automating the workspace around it. i built an open source cli and mcp that lets agents manage and operate in your figma workspace -- runs locally, with Claude Code, Cursor and OpenClaw. one message runs a full workspace audit, finds wasted seats, offboards a user. files transferred, access revoked, removed from the org. chores that eat hours a month across dozens of workspace ui pages, automated, parallelized, and done in seconds by an agent. no clicking around, just intent → execution. @figma you guys spent a decade making design collaborative. Now it's time to make it a playground for agents.

I regret spending 2.5 years on the application layer despite repeated advice from VCs and friends to focus on AI infra. I was wrong about that bet, and I’m shifting back to AI infra now. There’s less things left to do than in 2022, when I should’ve started, but it’s still better than not doing anything.