What A Project Is

Time: 20 minutes
You'll end up with: A project folder Claude is actually working in

Why this exists

You've got Claude Code running. It answered you. So far it feels like ChatGPT in a different window — and if that's the model you carry forward, everything from here will be confusing in a way you can't put your finger on.

Because there's one thing going on underneath that changes how you use it, and nobody says it out loud: Claude Code is always standing in a folder. Which folder decides what it can see, what it can change, and how much of your answer is guesswork. Get this now and the next twenty lessons make sense. Skip it and you'll spend weeks wondering why it "forgot" things it was never shown.

The idea

Claude Code isn't in the cloud. It's standing in a folder on your computer, and it can only see what's in that folder.

ChatGPT knows nothing about your machine. You paste something in, it responds, and the moment you close the tab it's gone. Claude Code is the opposite: point it at a folder and it can read every file in there, change them, make new ones, and remember what it did.

That folder is the project.

It's not a special format. There's no "new project" button that creates a magic thing. A project is any ordinary folder on your computer — the same folders you already make in Finder — that you've pointed Claude at. That's the whole definition. The folder was already a folder. Pointing Claude at it is what makes it a project.

Which leads to the one rule that does all the work here:

Claude can see everything in the project folder, and nothing outside it.

Ask about a file that's in there — it reads it and answers from what's actually written. Ask about a file that's somewhere else — it can't see it, so at best it says so and at worst it guesses. That guess is the single most common reason people think Claude is unreliable. It usually isn't wrong. It's usually standing in the wrong room.

So there are only two questions worth building a habit around, and you'll ask them for the rest of your career:

Which folder am I in?
Is the thing I'm asking about actually inside it?

The practical consequence: one project per real thing. Your website is a project. Your client work is a project. Your notes are a project. Don't point Claude at your entire hard drive hoping it'll sort it out — it'll be slower, more expensive, and worse, because it's reading a thousand files to answer a question about one.

Do

Make a new folder on your desktop called first-project. Finder is fine — no ceremony required.
Put something in it. A text file, a document, a screenshot. Anything real.
Open Claude Code and point it at that folder.
Ask it: what folder are you in, and what's in it? Check the answer against what you can see in Finder. They should match exactly.
Ask it to make you a file — write me a file called notes.md with three bullet points about what I'm working on. Watch it appear in Finder.
Now the important one. Ask it about a file that's somewhere else entirely — something in your Downloads, say. Watch what it does. Note whether it says it can't see it, or has a go anyway.
Point it at that other folder instead. Ask the same question again. Get a real answer.
Write one sentence in notes.md, in your own words, explaining why the answer changed.

Step 6 is the one that matters. Everyone reads "it can only see the project folder" and nods. Watching it fail on a file you can see with your own eyes is what makes it stick.

Done when

first-project exists on your desktop with at least two files in it, one of which Claude made.
Claude's description of the folder matched what you saw in Finder.
You asked about a file outside the project and saw what happens.
notes.md has your own sentence explaining why pointing it at a different folder changed the answer.

If Claude answered confidently about the outside file and got it wrong — good. That's the most useful thing that can happen in this lesson. Note exactly what it said. You'll recognise the shape of that mistake for years.

Never do

Don't point Claude at your entire home folder or hard drive. It'll be slow, it'll cost more, the answers get worse, and you've handed read-and-write access to every file you own — tax returns, passwords, everything — for a task that needed one folder.

One project, one real thing. If you're tempted to widen the scope because it can't see something, that's the signal to move the file in, or start a session in the right place — not to open the doors.