What Claude Projects Are For
Projects solve a specific pain point: repeating yourself in every Claude conversation.
If you regularly work with the same codebase, the same client, the same research topic, or the same writing style, you usually paste the same background context at the start of every session. Projects eliminate this. You upload that context once, and Claude has it available in every conversation within the project — automatically, without prompting.
Common project setups:
- Client work — upload briefs, brand guidelines, previous outputs; Claude always knows the client context
- Coding projects — upload key files, architecture docs, coding standards; Claude reviews code in context
- Research — upload papers, notes, source material; Claude analyzes without you re-supplying sources
- Writing — upload style guides, tone examples, audience notes; Claude writes consistently
How to Create a Project
- In the Claude sidebar, click New Project (or the folder/plus icon)
- Give the project a name
- Click into the project to open it
- Upload files using the Add content button or by dragging files in
- Write project instructions in the instructions field — these appear at the start of every conversation in this project
- Click New Conversation to start working
What to Put in Project Instructions
Project instructions are a system prompt that runs at the start of every conversation. Think of it as a standing briefing for Claude.
Template:
Role: You are helping me with [project type].
Context: [Brief description of the project, client, or goal]
Style: [Tone, format, length preferences]
Always: [Rules that always apply]
Never: [Things to avoid]
Example — Client project:
You are helping me with content for Acme Corp, a B2B SaaS company selling HR software to mid-market US businesses.
Audience: HR managers and CHROs, not technical readers.
Tone: Professional but approachable. No jargon.
Always: Reference uploaded brand guidelines when writing.
Never: Use competitor names. Never make claims about pricing or specific features not in the uploaded docs.
Example — Coding project:
You are a coding assistant for my FastAPI + PostgreSQL backend project.
Stack: Python 3.12, FastAPI, SQLAlchemy 2.0, Alembic, Pydantic v2.
Style: Use type hints everywhere. Write unit tests with pytest. Follow the uploaded coding standards.
When I share code, point out bugs and security issues first, then suggest improvements.
Best Practices for Project Files
Upload only what Claude needs to reference. Every byte of uploaded content takes up context window space. Uploading a 200-page PDF when Claude only needs the executive summary wastes space that could go toward the conversation.
Create focused summary documents instead of raw sources. If you have a 50-page research report, write a 2-page summary of the key findings and upload that. Claude can work from a good summary more reliably than from a dense source document.
Organize by what Claude will actually reference. Ask yourself: "Will Claude need this fact in most conversations in this project?" If yes, put it in the project. If it only applies to one task, paste it into that specific conversation.
Update files when context changes. If your codebase changes significantly or a client's brief is updated, replace the old files with new versions. Outdated project files will cause Claude to give outdated answers.
Organizing Multiple Projects
Create one project per distinct workstream:
- One project per client (not one project for all clients)
- One project per codebase or application
- One project per research area
- One project for personal use vs. work use
Name them clearly. "Marketing — Acme Corp" is better than "Project 3." The sidebar displays project names and recent conversations — clean naming makes it easy to jump back in.
Common Mistakes to Avoid
- Uploading everything — More files is not better. A project with 20 uploaded documents will have Claude struggling to prioritize which content matters. 3–5 focused files outperform a dump of everything you have.
- Skipping the instructions — Project files without instructions leave Claude to guess how to use them. Always write at least 3–5 sentences explaining the project context and how you want Claude to behave.
- One giant project for all work — Mixing unrelated projects into one makes the instructions and files irrelevant to any given task. Separate projects stay focused.
- Not starting new conversations when threads get long — A very long conversation within a project fills up the context window, leaving less space for your project files. Start fresh conversations within the project when sessions exceed 50–60 back-and-forth exchanges.
- Expecting Projects to replace your notes — Projects are for context Claude needs, not for your own reference. Keep your own documentation; treat project files as Claude's briefing, not your filing system.