The version you wish someone had given you on day one.
Projects are the feature that turns Claude from a chat tool into a real working tool. Most beginners don't know they exist. The ones who do know often don't use them right.
This guide is the version of Projects you wish someone had given you on day one.
What a Project actually is.
A Project is a folder that holds three things. A custom instruction (what Claude should know about this work). A set of files (the documents, examples, references for this work). And every chat you've ever had inside that Project.
When you open a chat inside a Project, Claude already knows the instruction and has read the files. You don't paste them again. You don't re-explain. You just start the next chat.
Think of a Project as a coworker who's been on the job for a while. They know the context. They've read the docs. They remember the conversation from last week. That's the difference.
What changes when you switch.
Without Projects, every Claude chat starts cold. You paste the same context, the same examples, the same explanation, every single time. You waste 5 minutes setting up before you ask the question. After a week, you stop using Claude for the harder work because the setup is exhausting.
With Projects, the setup happens once. Every chat after that starts where the last one left off. The work compounds.
This is the single feature most likely to change what you use Claude for.
How to make a Project in 90 seconds.
Click Projects in the left sidebar of Claude. Click Create new project . Give it a name that describes the work, not the tool. "Quarterly board updates" beats "Claude help." Add a one-paragraph description of what the work is and who it's for.
Then do two things.
Custom instructions
What Claude should know every time you open a chat in this Project. Three to five sentences. What the work is. Who reads it. What style. What to avoid.
Knowledge files
The documents this work depends on. Past examples of the output. Style guides. Reference material. Anything you'd hand a coworker on their first day.
That's it. The Project is ready. Open a new chat inside it and ask the first question.
Three Projects to set up this week.
Don't try to organize your whole life into Projects on day one. Start with three. These three work for almost everyone.
Recurring writing
The thing you write every week that always feels like starting from scratch. Status update, newsletter, client check-in, investor note. Files: the last three or four examples. Instruction: who reads it, what tone, what it should never include.
Most important relationship
The person you communicate with most. Boss, biggest client, key partner, board chair. Files: a few past email threads. Instruction: who they are, what they care about, what they don't have time for.
The thing you're learning
A topic you're trying to understand. A book you're reading. A skill you're building. Files: the source material. Instruction: what you already know, what you're trying to figure out, how you learn best.
The ones that match your work
Three is the right number for week one. You can add more later. Most people stay at three or four for a long time and that's fine.
What "recurring writing" looks like, end to end.
Say your work involves writing a weekly internal update. Here's the Project setup, top to bottom. Copy it, change the names, ship it.
Name: Weekly internal update Description: A short Friday update I send to my team lead summarizing what I shipped, what's blocked, and what's next. Custom instructions: This project is for drafting my weekly Friday update. The reader is my team lead. She reads fast and hates fluff. The shape is always: 3 short paragraphs. Shipped, blocked, next. Keep the tone plain and specific. No buzzwords. No padding. If the input doesn't have specifics, ask me what shipped, what's blocked, and what's next before drafting. Knowledge files: - 4 past Friday updates I've written - Our team's quarterly goals doc
Set this up once. Use it every Friday in 5 minutes instead of 30.
From there, every Friday you open a new chat in that Project and paste your raw notes. The output looks like you wrote it. Because you set up Claude to know what "like you" means.
Common traps.
- Making one giant Project for everything. The whole point is separation. Different Projects for different work.
- Stuffing the custom instructions with a wall of text. Three to five sentences. Edit ruthlessly.
- Adding 50 files on day one. Start with the three or four most important. Add more later.
- Re-pasting context inside the chat that's already in the knowledge files. Trust the Project.
- Treating the Project as final. Update the instructions as the work changes.