Stop Re-Explaining Yourself: Set Up a Claude Project Once

You solved something properly on Tuesday. On Wednesday you needed the same kind of thing, opened a fresh chat, and typed your whole situation out again.

If that is your week, you are not the only one. Nobody describes this as a big problem. It gets described as a small tax, paid a few times a day, and mostly it gets described with a shrug.

It is not a small tax. It is where your consistency goes.

Why re-explaining costs more than the typing.

The cost is not the ninety seconds. The cost is that you never explain it the same way twice.

On Tuesday you said the readers are not technical, that you wanted it under four hundred words, and that the tone should be plain. On Wednesday you were in a hurry, so you said the first thing and forgot the other two. Same task, different brief, different output. And then you conclude that the tool is inconsistent.

It did what you asked, both times. The thing that moved was your description of the job.

So the fix is not to describe the job better. It is to stop describing it at all. The last post ended with a small assignment: collect the sentences you retype without noticing into one file. This is where that file goes.

What a Project actually is.

A normal conversation is a sheet of scratch paper. You write on it, take your answer, and the sheet gets recycled. A Project is a labelled folder that stays on your desk, holding the same instructions and the same background material every time you sit down.

In practice it is a workspace you make once, for one recurring kind of work, with standing instructions that apply to every conversation inside it. One for client reports. One for customer replies. One for whatever lands on you every Monday. They do not mix, so the room you walk into is already thinking about the right job.

It installs nothing and costs nothing extra. Projects sit inside the ordinary Claude you already open, on every plan, including the free one.

Five steps, and only one of them is slow.

1. Create the Project and name it after the job it does. Weekly client report beats Work.

2. Write the standing instructions. This is the step that does all the work, and the only one worth slowing down for.

3. Add the material you keep pasting. The style guide, the product list, last quarter's numbers, whatever gets attached to every third message.

4. Start a conversation inside it and give only the task.

5. Adjust the instructions the first three times something comes back wrong, then leave them alone.

Steps one, three, four and five take about a minute between them. Step two is the one people skip, and skipping it is why some people try Projects and report that nothing much changed.

What goes in the standing instructions.

Write the parts of your brief that never change. In practice that is four things: the situation, the role you want Claude to take, the tone, and the conditions that always apply.

Context: I run marketing at a small software company that sells to other businesses. Our readers are operations managers, not engineers. Role: Act as an editor who protects clarity over cleverness. Tone: Plain and direct. No exclamation marks, no superlatives. Conditions: Under four hundred words unless I ask for more. Never invent a customer quote or a number. Flag anything you are unsure about rather than smoothing over it.

Four lines, written once. Now look at what your daily message becomes:

Turn these release notes into a customer email. A short bullet list, then one closing paragraph.

That is the whole prompt. The room supplies the rest, the same way, every time. Your instructions stopped depending on whether you remembered them.

Free Claude toolkit. The companion pack for my Claude book is free, and it includes ready-made Project instruction templates you can paste straight into a new workspace, plus more than five hundred numbered prompts. No card, and you can leave the list in one click. Get the toolkit →

What this will not do.

It will not stop Claude being wrong about facts it has no way of checking. A room full of your context is still not a room full of the truth.

It will not rescue an instruction that was vague in the chat, because it will be exactly as vague in the room. Make it good fails in both places equally.

And it does not carry across to another Project. That separation is the feature, but it also means three kinds of work take three rooms, and you build them one at a time.

One thing to do before the next post.

Pick the job you bring to Claude most often. Make one Project for it and write four lines: situation, role, tone, one condition. Then open a conversation inside it and send nothing but the task.

If what comes back is already shaped the way you wanted, you have just moved your consistency out of your memory and into the room. Ten minutes, once, and then it holds.

If you want the whole system rather than one piece of it, that is what I wrote Claude AI Bible (7 Books in 1) for. Seven books in one volume, with eight ready-to-use Project instruction templates, the setup walkthrough in dated screenshots, and more than five hundred numbered prompts to copy.

This post is part of my Claude series. The one that started it is Why Claude Gave You a Great Answer on Monday and a Flat One on Tuesday.

Tomasz