Posting my Imperfections - Video 2 - The Claude Side

Hi all! Video two is done. The first one was the human side of how I work. This one is the Claude side: how I run it so the right model does the right job, without me having to tell it.

It's 3 minutes 45 seconds, and I explain it as a mechanic's shop:

- Haiku is the parts runner

- Sonnet is the mechanic

- Opus is the foreman

- The Fable models are the specialist I call in on purpose

You don't pay the foreman to fetch a filter, and you don't ask the runner to decide if the engine is worth saving.

Then it covers how my rules sit in layers (one for everywhere, one for each project), why that keeps the cost of a request down (the cache), how helpers and workflows use it, and my own numbers from the last month. About 96% of my input tokens were cache reads, which at public list prices works out to roughly 90% cheaper than paying full price for every token. That's list-price math, not my bill, and the video says so.

I'm not saying it's perfect or right. It's just what we built. I'm still learning and I still get things wrong, so if you spot something I got wrong, please tell me.

Video: https://youtu.be/6RonYbHcbbw

First video, if you missed it: https://www.skool.com/cliefnotes/the-most-productive-procrastination-period-ive-ever-had

Heads up: the narration is an AI clone of my own voice (ElevenLabs), every drawing is an illustration, and I wrote the words and directed Claude to build it.

Which model do you reach for first, and what makes you switch up or down?

23 comments

Posting my Imperfections - Video 2 - The Claude Side