Setting Up Claude as a Content Team: Folders and Global Instructions

The trick that makes Claude behave like a team rather than a chatbot is mechanical, and it takes about five minutes to set up. You point it at a folder, and you give it one standing instruction to read that folder before it does anything. After that, it stops asking you who you are, because it already knows.

This is the plumbing behind the rest of the Claude-for-YouTube series. Here is how it fits together.

Why a folder beats a chat window

A normal chat starts from nothing every time. You re-explain your channel, paste your context, remind it of your audience, and only then get to the actual task. Multiply that by every video and the re-explaining becomes the job.

A folder-based workspace removes that. Claude can see every file and subfolder you give it, so your channel context, your templates, and your past outputs are all there permanently. You set it up once and stop repeating yourself.

What you need

You need the desktop Claude app and a paid plan, because the folder workflow is not on the free tier. The cost is modest against the time it saves once you are running real volume. Install the app, sign in, and switch to the workspace mode that can read folders.

One option worth turning on early is the browser connection. With it, Claude can do research for you, looking at what is trending in your niche or analysing competitor channels, rather than relying only on what it already knows. The research parts of this system depend on it.

Structure the folder simply

Keep one main folder for the channel. Inside it, a folder for your context, holding the Master Context Doc, and separate folders for each kind of task you run, each with a short instruction file describing what that task should do and where to save its output.

The point of this structure is that you can say “run the script refiner” and Claude knows where to find the instructions for that job and where to put the result, without you spelling it out each time.

The one instruction that ties it together

The step most people miss is the standing instruction. In the settings, you give Claude a permanent rule that applies to every session: at the start, go to the channel folder, read the relevant task instructions and the Master Context Doc, and only then begin.

That single rule is what stops it asking generic questions. Every time you open it, it orients itself in your channel first. You told it the routine once, and it follows the routine forever.

Confirm it works

Ask it to read your Master Context Doc and tell you who your ideal viewer is. If it navigates to the folder, reads the file, and answers in your detail, the wiring is correct and every other task in the series will draw on the same context. If it does not, check the folder is connected and the file names match what the instructions expect.

Frequently asked questions

Do I need a paid Claude plan to set this up?

Yes. The folder-based workflow that reads your files automatically requires a paid plan; the free tier does not include it.

Why use a folder instead of just pasting context into chat?

A folder gives Claude permanent access to your channel context, templates, and past work, so you never re-explain yourself. A chat window starts from zero every time.

What does the global instruction do?

It is a standing rule that runs every session, telling Claude to read your channel folder and context document before doing anything, so it always works from your specifics rather than asking generic questions.

Get the AI tools that are actually worth it

One short, honest email a week: what’s real, what’s hype, and what’s worth your money. Subscribe and get my full tool-stack guide, free.

Get the free guide
Scroll to Top