You have 300 generations and no idea which ones are good

That is the job. Not a metaphor for the job: the job.

You ran the batch overnight. There are 300 files called kling_20260803_0417_v2_final.mp4. Forty are usable. You know which prompt you were iterating on but not which file came from which version, and the good one is in there somewhere.

This reads the whole folder, cross-references every file against the prompt that made it, renames them so the names mean something, and hands you the shortlist. Then it does it again tomorrow without being asked twice.

What "lives in a folder" means

You did this in Module 0 without being told why. You start it inside a folder, and that folder is its world.

• It reads what is there without you attaching anything
• It writes back into it
• It runs real programs on your machine: ffmpeg, CapCut exports, Resolve, upload scripts
• It remembers between sessions, if you set it up to

Point it at one project and it knows that project. Point it at your whole drive and it knows too much and works worse.

Every word of that is load-bearing

"Exactly what you said", and what it costs

You say: "clean up the renders folder"

A human assistant asks what you mean.

This picks an interpretation and executes it, quickly and thoroughly.

That is why permissions get their own module, and why undo gets another one.

The fix is one sentence long:

"Clean up the renders folder. Move anything older than 30 days to _archive, delete nothing, show me the list first."

Things it is unreasonably good at

1. Reading a large mess and telling you what is in it

300 generations, 12 versions of a script, a year of project folders. It inventories and compares faster than you can open the first file.

1. Doing the same boring thing 500 times, identically

Rename, transcode, resize, caption, checksum, reformat. It does not get sloppy at file 300.

1. Cross-referencing things that live in different places

Which prompt produced which shot. Which cut is on which platform. Brief against delivery.

1. Turning one format into another

Brief to shot list. Shot list to prompt list. Transcript to captions. Notes to a structured doc.

1. Checking work against a spec, exhaustively

Aspect ratios, durations, safe areas, file naming, whether all 20 platform cuts actually exist. It does not skim the last third.

Notice the pattern: none of these are creative decisions. Every one is the work around the work.

The honest limits

• It cannot watch your footage. It reads text, filenames and metadata brilliantly. It cannot

look at a generation and tell you the hands are wrong. On generated video this is the limit that matters most: you are still the eyes.

• It does not have taste. It can tell you a structure is weak. It cannot tell you whether the

spot is good.

• It is confident when it is wrong. The tone never changes. A wrong answer arrives with the

same calm as a right one. Verification is your job and it stays your job.

• It forgets. Every session starts fresh unless you build memory: which is a module of its own,

because it is the difference between a tool and a studio.

• It will invent a plausible detail to fill a gap unless told not to. A made-up delivery date

is worse than a missing one.

Which Claude you are actually using

This course is Claude Code. It is the one that touches your work.

One word, before it confuses you

In this course a hook is a script that fires automatically when something happens, you meet them when we build your guardrails.

Your kind of hook, the first three seconds, the thing that stops the scroll, we will call the open, every time.

Two different trades borrowed the same word. Naming it once here is cheaper than guessing at it for the rest of the course.

What you will have built by the end

• A studio folder that knows your work and remembers between sessions
• A prompt library that fires variations and keeps what worked
• A pipeline that generates, fetches, renames and files while you sleep
• A spot, finished, and twenty platform cuts of it
• Guardrails around all of it: you watched one refuse you in Module 0; by the end they cover

every job you run

You will not write code. You will type sentences.