If you've ever started a Claude conversation with three paragraphs explaining your tech stack, folder structure, and coding conventions before you could even ask your actual question — Claude Projects are for you.
Projects give Claude persistent memory scoped to a specific codebase or workflow. You set it up once, and every conversation inside that Project starts with Claude already knowing your context. No re-explaining. No copy-pasting README sections. Just ask your question.
What you can store in a Project
- Your tech stack and architecture — 'This is a Next.js 15 App Router project using TypeScript, Tailwind, and Supabase'
- Coding conventions — naming patterns, folder structure, preferred libraries
- Files and docs — paste in your CLAUDE.md, API docs, or schema files and Claude can reference them any time
- Ongoing context — decisions you've made, things to avoid, known quirks in the codebase
- Custom instructions — how you want Claude to respond, what format you prefer for code, level of explanation
How it changes your workflow
Without Projects, every conversation is stateless. Claude is helpful but starts from zero. With a Project set up, you can jump straight to: 'Add a loading skeleton to the ResourcesClient component' and Claude already knows what ResourcesClient is, what styling conventions to follow, and what imports are standard in the codebase.
It's also useful for non-coding workflows — a writing Project with your brand voice guidelines, a research Project with background reading uploaded, a client Project with their requirements and constraints. Anywhere you find yourself re-establishing context repeatedly, a Project removes that overhead.
How to set one up
In Claude, click 'Projects' in the left sidebar, create a new Project, and add a Project instruction — this is your persistent context block. You can also upload files directly into the Project knowledge base. Any conversation you start inside the Project inherits all of it automatically.
The quick win
If you work on the same codebase more than a few times a week, spending 10 minutes setting up a Project pays back immediately. Write a short description of your stack, paste in any key conventions, and you'll never re-explain your project again.