Three short lessons are up in the Automation Skills course. Each one stands on its own, so start with whichever sounds like your problem: • When to start a new AI chat instead of carrying on in the old one • How to write a CLAUDE.md that does not eat your usage limit • How to make Claude Code's /compact keep the part you actually care about All three come from the same idea: an AI model has no memory, so the whole conversation is sent again every time you press Enter, and that is what your limit is actually being spent on. If any step in them does not make sense, say so underneath and I will rewrite it. That is more useful to me than a thank you.

This is everything from the video about what actually eats your usage limit: the ten slides with a written explanation under each one, the four prompts, and the one-page guide to writing a prompt properly. It is for you if you keep running out of limit in the middle of something and have never been told what is spending it. WHAT IS ATTACHED • The complete pack (PDF) — the ten slides explained so they make sense on their own, the four prompts with the words you need to change marked, a page on the four commands, and two pieces that are not in the video • The one-page prompt guide (PDF) — meant to be kept open beside you while you write a prompt • A starter CLAUDE file — a block you can copy into the file Claude Code reads at the start of every session in a project • All four prompts as plain text — easier to copy from than a PDF START HERE Start with the starter CLAUDE file, because it is the one that keeps paying. Open a folder you actually work in, make a new file there called CLAUDE, with the normal .md extension, paste the block in, replace the parts in angle brackets, and delete the lines that do not apply to you. Then open Claude Code in that folder and type /context. The number it shows against your memory files is what that file costs you on every single message. There is nothing to install and nothing to sign up for. Every command in here is already inside Claude Code. ONE QUESTION Full walkthrough, with all of it running live: https://youtu.be/bvaHxURbMK0 What is the point in your day where you notice the limit? Reply with it and I will tell you which of the seven fixes I would point at it first.

This is everything used to build a ten page website five different ways in Claude Code: one session, parallel sessions, subagents, agent teams, and a dynamic workflow. It is for you if you have only ever used one chat and want to know what the other four are, what they cost, and which one your own job actually needs. What is attached: - pack.pdf, the whole thing in one document. Nine diagrams with an explanation under each, all twelve prompts with the words you need to change marked, and one page that is not in the video - brief.md, the complete website brief. This is the file every prompt reads - prompts.md, the twelve prompts as plain text, easier to copy from than a PDF - site-check.md and site-check.js, the two files Claude wrote when it was asked to save a job as a reusable command. A real one, so you can see what a saved command is - finished-site.zip, the ten pages that came out the other end Start with brief.md. Make a new empty folder anywhere on your computer, put brief.md inside it, open that folder in Claude Code, and paste prompt 1 from the pack. That is the whole setup. There is nothing to install. If you have never done any of this before, do the first four prompts and stop. They build a working page in one conversation, and they are the part everything else is measured against. One question, and I would genuinely like to know: what is the job you keep doing by hand that you think might be too big for one chat? Reply with it and I will tell you which of the five I would point at it.

Welcome. This community exists for one reason: everything I use in a video is in here, free, written up properly. The slides, the prompts, the files. I have just put the first three lessons in the classroom, under How To. Each one stands on its own, so you do not need to have watched anything to use them. 1. Which of the five ways should you actually use? Claude Code gives you five ways to split work between agents, and people pick the wrong one because they pick by name. There is one question that sorts all five in about ten seconds. 2. Turning on agent teams. This is the only setup where the agents talk to each other instead of reporting back to you. It is off by default and there is one edit to make. In my run they rearranged my whole site order themselves, and they were right. 3. Turning a workflow into a command you can reuse. Getting a job done once is fine. Getting it saved as a command you type next week is the actual point. Two other places to look: Video Resources is where each video's full pack lands, one post per video. Guides is where I put written things that never became a video. If you get stuck on any of it, reply here. A question you think is too basic is exactly the kind this place is for.