Every new Claude chat starts from zero. It doesn't know your role, your company, your writing style, or the files you work with. So you spend the first few messages catching Claude up — again — before you can get anything done.
Projects fix that.
What a Project actually is
A Project is a dedicated workspace inside Claude. It has its own chat history, uploaded files, and custom instructions that persist between sessions. When you open a Project, Claude already knows the context. You pick up where you left off instead of starting over.
Think of it like a shared folder with a coworker who reads everything in it before every conversation.
Memory vs Projects. Claude's Memory feature remembers things across your whole account — preferences, recurring facts, how you like answers formatted. A Project is scoped: instructions, files, and chat history that only apply inside that workspace. Use Memory for things that should follow you everywhere. Use a Project when you want a dedicated workspace that doesn't bleed into the rest of your work.
When to use a Project vs a normal chat
Use a normal chat when you have a one-off question or quick task you won't revisit.
Use a Project when you'll come back to the same topic more than twice.
Use a Project when Claude needs background context to do good work (your role, your audience, your tone).
Use a Project when you're working with the same files repeatedly — reports, templates, reference docs.
Use a Project when multiple conversations should share the same ground rules.
How to set one up
Step 1: Create the Project
Go to claude.ai and click Projects in the left sidebar. Click New Project. Give it a clear name — something you'll recognize in two weeks. "Q2 Board Deck" is better than "Work Stuff."
Step 2: Write your instructions
Open the Project and click Edit Project Instructions. This is where you tell Claude who you are, what you need, and how you want it to work. Be specific. These instructions load automatically at the start of every chat inside this Project.
Here's a starting template you can paste and customize:
You are helping [your name], [your role] at [company].
Audience: [who reads your output]
Tone: [how it should sound — direct, formal, casual, etc.]
Format preferences: [bullet points, short paragraphs, tables, etc.]
Things to always do:
- [e.g., Use metric units]
- [e.g., Keep responses under 300 words unless I ask for more]
Things to never do:
- [e.g., Don't use jargon my audience won't know]
- [e.g., Don't invent data or statistics]
Step 3: Upload what Claude needs to know
Click Add Content to upload files. These stay attached to the Project. Good things to upload:
Reference docs Claude should draw from (style guides, SOPs, org charts)
Templates you want Claude to follow
Past examples of good output ("write it like this")
Data files Claude should analyze or summarize
You can upload PDFs, text files, code files, CSVs, and images. There's a file size limit, so keep uploads focused. Don't dump your entire drive — give Claude what's relevant to this Project.
Four Project recipes
Recipe 1: Weekly meeting prep
Good for: Managers, team leads, anyone who runs a recurring meeting and wants an agenda and pre-read pulled together fast.
Upload this: Last 2-3 meeting notes, team roster or org chart, any standing agenda template.
Instructions to paste:
You help me prepare for my weekly [team name] meeting every [day].
Use the uploaded meeting notes to track open action items.
Draft an agenda that includes: follow-ups from last week, new items I mention, and a time estimate for each item.
Keep the agenda to one page. Use bullet points, not paragraphs.
Flag any action items that are overdue or were carried over more than once.
Try this first: "Here are my notes from this week. Draft next Monday's agenda and flag anything that's been stuck for more than two weeks."
Good for: Anyone who writes frequently and wants Claude to match their voice instead of sounding like a chatbot.
Upload this: 3-5 examples of your past writing (emails, memos, reports — whatever you write most). A style guide if your org has one.
Instructions to paste:
You help me draft written communications — mostly emails, memos, and short reports.
Match my writing style based on the uploaded examples. Pay attention to sentence length, tone, and how I open and close messages.
Default to concise. If I need something longer, I'll say so.
Never use "I hope this email finds you well" or similar filler.
When I give you bullet points, turn them into a polished draft. Don't add information I didn't provide.
Try this first: "Draft a memo to my team announcing that we're changing our weekly standup from Tuesday to Thursday. Keep it short. Tone: matter-of-fact, not apologetic."
Recipe 3: Research digest
Good for: Analysts, PMs, consultants, or anyone who needs to stay current on a topic and wants Claude to cut through the noise.
Upload this: A few articles or reports that represent the kind of sources you trust. A glossary or key terms list if the topic is specialized.
Instructions to paste:
You help me stay current on [topic/industry]. I'll paste in articles, reports, or raw notes, and you summarize them.
For each source, give me:
- 3-bullet summary (what happened, why it matters, what to watch)
- One sentence on whether this changes anything for [my team / my company / my project]
- Confidence level: are you summarizing what the source says, or interpreting?
Don't editorialize. Don't add context I didn't ask for. If something contradicts a previous source, flag it.
Try this first: "Here's an article from [publication]. Summarize it using the format in my instructions."
Recipe 4: Client or account background
Good for: Account managers, consultants, sales reps — anyone who manages relationships and needs Claude to know the backstory.
Upload this: Account briefs, CRM notes, past proposals, contract summaries, org charts for the client.
Instructions to paste:
You are helping me manage my account with [client name].
Key facts:
- Industry: [their industry]
- Our relationship: [how long, what we do for them]
- Main contacts: [names and roles]
- Current status: [active project, renewal coming up, etc.]
When I ask you to draft something for this client, use a [formal/friendly/direct] tone.
Reference specific details from the uploaded docs when relevant — don't be generic.
If I ask about something not covered in the uploads, say so instead of guessing.
Try this first: "Draft a check-in email to [contact name] about the status of [current project]. Mention the timeline we agreed to in the last proposal."
Common mistakes
Writing instructions that are too vague. "Help me write better" gives Claude nothing to work with. "Match the tone of my uploaded examples and keep emails under 150 words" does.
Uploading too much. Claude reads everything in the Project at the start of each chat. If you upload 20 documents, you're using up context on material that may not be relevant. Be selective.
Forgetting to update instructions. Your role changes, your priorities shift. If your Project instructions are stale, Claude's output will drift. Review them once a month.
Using one Project for everything. A Project works best when it has a clear purpose. "All My Work" is a junk drawer. "Q2 Marketing Plan" is a tool.
What to do next
When Claude produces something substantial — a draft, a table, a plan — open it as an Artifact to keep editing it in place. Artifacts stay attached to the conversation, so you can refine without re-prompting from scratch.
If you want Claude to go beyond chat and start working across your computer — managing files, running tasks, drafting docs in your apps — that's Cowork.