Don't start from
a blank chat

You have Claude installed, you know the surfaces, and you have a constitution. So far you have been loading that context by hand, pasting it into each new chat. That works once. By the third time it is a chore, and chores are where good habits quietly die.

There is a better home for your context than a fresh chat. It is called a Project. A Project is a chat that remembers. You give it standing instructions and a few files once, and every conversation inside it starts already knowing who you are and what you are doing. The blank chat forgets you the moment you close it. A Project does not.

A blank chat is a stranger you meet again every morning. Polite, capable, and with no memory of yesterday. A Project is a colleague you have briefed. The briefing is the instructions and the files you load in once. After that, you just talk, and it already has the background.

One note so you never feel locked in: this is not a Claude invention. ChatGPT calls them Projects too, Gemini calls them Gems. The button moves, the move stays the same. Brief it once, work inside it. What you are learning here is the habit, not one company's menu, and the habit travels with you.

One practical thing before you make one. Projects work on every plan, free included, but the free tier caps how many you can keep at once. That is plenty to start, but it is a real ceiling, so if you ever find you cannot add a new Project, you have not broken anything. You have just filled your allowance, and that is the moment a paid plan starts to earn its keep. So make your first Project count rather than spinning one up for every passing idea.

The shape is simple, and it is the same shape you will reuse for every serious thing you build. Context goes in once at the top, then the work flows underneath it.

The instructions are the heart of it. They are short, written in plain language, and they tell the Project how to behave for every conversation. Here is a real set for a small online shop owner who wants help with customer messages and product copy.

That last line matters more than it looks. Telling a Project to ask before guessing is the single most useful standing instruction a beginner can give. It turns a tool that confidently runs off in the wrong direction into one that checks with you first.

One thing before you load a single file, because the honest version matters here. The goal is not to upload everything about yourself. It is to load only what this work actually needs: your constitution, and the specific references this Project will use. That is it. Pouring in your whole life does not make the answers better, it just spreads your information wider than it has to go.

And it is worth knowing where that information goes, because the course would be hype if it skipped this. On a personal plan (Free, Pro, Max), whether your conversations are used to improve the model is a setting you control, and you should go and check it once. On a business plan (Team or Enterprise), your data is not used for training at all. Either way, the simple rule holds: load what is yours to share and the work needs, and keep other people's things, a signed NDA, a client's personal data, the contract you have not been cleared to share, out of it. Same instinct as not leaving those papers on a cafe table.

You stopped meeting a stranger every morning. You briefed a colleague once, and now you just get to work.