You commented “PROJECTS”: here it is

Claude Projects Setup: The Right Way to Isolate Context

Follow this step-by-step guide to set up Claude Projects so each one has isolated context, no bleed, no confusion.

Free guide · copy-paste ready · built by the BrainVaultAI team

Claude Projects are underused because most people set them up like a folder, not like a team member. A project needs: a sharp system prompt that defines scope, the right files attached (not too many), and a naming convention that tells you what each project is actually for. This guide covers the four-step setup pattern that keeps projects from turning into context soup. It also covers the biggest mistake, attaching too many files, and how to pick what actually belongs in the project versus what belongs in a CLAUDE.md. Use this when spinning up a new Claude Project for a client, a product, or a recurring workflow. Revisit it quarterly to prune projects that have gone stale. The checklist at the end is the part most people skip. Run it before you consider a project ready to use.

Project setup: system prompt template

You are working inside the [Project Name] project. ## Scope
This project covers: [describe exactly what this project handles, product area, client, workflow, etc.] Do NOT work on anything outside this scope without saying so explicitly. ## Context you have
- [File 1], what it is and when to use it
- [File 2], what it is and when to use it ## How I work
- [Key preference 1]
- [Key preference 2]
- Terse answers. I'll ask follow-ups. ## Current status
[One paragraph on where this project is right now, phase, what's done, what's next.] ## Conventions
[Any naming, formatting, or process conventions specific to this project.]

What files to attach: decision rule

## File attachment decision rule Attach a file to a Project if ALL three are true:
1. You reference it in more than 50% of conversations in this project
2. It's stable (doesn't change more than once a week)
3. Claude needs to READ it, not just know it exists Do NOT attach:
- Files Claude will edit (use CLAUDE.md + open files in session instead)
- Large files Claude only needs 5% of (paste the relevant section in conversation)
- Files that change frequently (stale context is worse than no context) Good candidates to attach:
- Product spec or PRD
- Brand voice doc
- API schema
- Database schema
- Style guide
- Client brief Bad candidates:
- Full codebase
- Log files
- Any file over ~50KB

Project readiness checklist

## Before you call a Claude Project ready to use - [ ] System prompt defines scope in one sentence
- [ ] System prompt says what NOT to do
- [ ] Attached files all pass the three-criteria rule above
- [ ] Current status section is accurate and dated
- [ ] You've run one test conversation and it stayed on scope
- [ ] Project name is specific enough to distinguish it from your other projects
- [ ] You have a note for when to archive this project (completion condition) ## Quarterly pruning
Set a calendar reminder. For each project ask:
- Did I use this in the last 30 days?
- Is the status section still accurate?
- Are the attached files still the right ones? Projects that fail these questions get archived. Dead projects with stale context are worse than starting fresh.

Want the editable version?

We'll send the editable version of this asset, plus a short series of our highest-leverage AI plays for operators. No spam. Unsubscribe in one click.

Free. No spam. Unsubscribe in one click. By submitting you agree to receive emails from BrainVaultAI.

More free AI guides in the full library · follow @brainVaultAI