How to Use Claude Projects (The Feature Most People Ignore)

Most Claude users open a new conversation every time. That means re-explaining context, re-uploading files, and hoping Claude remembers what you told it three sessions ago. It doesn't.

Claude Projects fixes all of this. It's one of the most underused features in Claude — and once you start using it, you can't go back.

What Claude Projects actually does

A Project is a persistent workspace inside Claude. Every conversation you have within a Project shares:

• Custom instructions — a system prompt that applies to every conversation in the project, every time
• Uploaded knowledge — documents, PDFs, code files, or text that Claude can reference across all sessions
• Conversation history — previous chats in the project are visible, so context carries forward

The practical result: Claude already knows who you are, what you're working on, and how you want it to behave — before you type a single word.

Setting up your first Project

Step 1: Create the Project

In Claude, click "Projects" in the left sidebar (Pro plan required). Name it for the context you want to maintain — your business, a specific client, a coding project, a research area.

Step 2: Write your custom instructions

This is the most important step and most people get it wrong. Custom instructions aren't just "be helpful." They're a briefing that tells Claude everything it needs to operate effectively in this context.

Good custom instructions include:

• Who you are and what you're working on
• Your preferred output format (length, tone, structure)
• Things Claude should always or never do in this project
• Key terms, names, or concepts specific to this context

Step 3: Upload your knowledge base

Upload the documents Claude should be able to reference. The more specific, the better. Good candidates:

• Your resume or LinkedIn export (for job search projects)
• Product documentation or feature specs (for product projects)
• Brand guidelines or style guide (for content projects)
• Codebase files or architecture docs (for development projects)
• Research notes or reference materials (for learning projects)

Claude will pull from these files when relevant — you don't need to re-paste content every session.

The Projects that actually move the needle

Job search project

Upload your resume, a list of target companies, and your work history. Set instructions to tailor outputs for your industry and seniority level. Now every resume tweak, cover letter, and interview prep session starts from your full context — not a blank slate.

Client project

One project per client. Upload their brand guide, past deliverables, and any notes from calls. Instructions tell Claude the client's industry, tone, and what they care about. Every piece of work you produce for that client goes through a version of Claude that already knows them.

Content project

Upload your best-performing posts, your brand voice guide, and a list of your content pillars. Instructions define what good output looks like for your audience. Stop explaining your voice every time — Claude already has it.

Research project

Upload papers, reports, or articles you're working from. Instructions tell Claude how you want information synthesized — level of detail, citation style, what questions you're trying to answer. Every research session builds on the last.

What Projects don't do

Projects are not unlimited memory. Claude doesn't learn or update based on your conversations — it can see previous conversations within the project, but it doesn't permanently retain new information the way a human does. The knowledge base is static until you update it manually.

This means you should treat your uploaded files as the source of truth — and update them when your context changes.

The one-time setup that pays forever

Setting up a Project well takes 20 to 30 minutes. After that, every conversation in that project runs faster, needs less explanation, and produces better outputs — indefinitely. It's the highest-leverage thing you can do if you use Claude regularly.

Most people skip it because it feels like setup. It's not setup — it's the actual work.