01Links
Claude Code
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
Build, test and deploy Cloudflare Workers from the command line, so deployment stays with the project.
Why I keep it
I use Wrangler every day because parts of my setup run on Cloudflare Workers. It’s Cloudflare’s CLI for building, testing and deploying Workers projects, so it handles deployment for the media server serving withseismic.com/spike/*.
The mail guide on the guides shelf also deploys with Wrangler, so the same CLI is part of getting that mail setup running. Its deploy script runs npx wrangler deploy, but it needs wrangler login on the Cloudflare account first.
01Links
Put your agent inside the repo, where it can read the plan, run the skills and check its work.
02Links
Give the writing to the model I prefer for copy, while Claude checks every claim against its source.
03Links
Keep separate jobs open across Claude accounts, with Notch showing which account has room to work.
04Links
Speak the job, the look and the stack in one brief, so your agent gets the context together.
06Links
Give apps and tools their own shortcuts, so you can switch contexts from the keyboard.
I’ll send you one build log a week: what I added to the library and what I shipped with it. You can unsubscribe any time.