It's never the prompt
The prompting turns out to be the least interesting part of my Claude Code setup, and most of what's actually doing the work is a handful of files I wrote once and then stopped thinking about.
7 posts filed under Tooling, newest first.
The prompting turns out to be the least interesting part of my Claude Code setup, and most of what's actually doing the work is a handful of files I wrote once and then stopped thinking about.
Porting an internal Claude Code safety tool from Linux to macOS took a couple months, and nearly every failure I found on the new platform failed in the permissive direction while printing a checkmark on the way out.
Our template for new Shopify projects contains no theme code at all, and the most useful thing in it turned out to be the part that says which files we own, which ones belong to the client, and which ones should never have been copied in.
How a Shopify theme change at work went from somebody typing a push command on a laptop to one repo of shared GitHub Actions workflows, and the backup cleanup I had to get wrong three times before I stopped overthinking it.
A client's homepage sat blank for a second and a half before it painted anything, and the code holding it there came from the tool they had bought to make the site convert better.
A client's nav collapsed at the wrong width on my machine and nobody else's, and it took two days to find out that the four of us had four different copies of the same dependencies.
Spending all week on a tool just to save 11 seconds a run. Nobody does that math beforehand.