Claude Projects Guide 2025: Custom AI Workspaces with Persistent Context
Claude Projects let you create persistent AI workspaces with custom instructions and uploaded knowledge — so you never re-paste context again. Here's everything you need to know.
What Are Claude Projects?
Claude Projects (launched 2024) are persistent workspaces inside Claude.ai where you can store:
- Custom instructions — a system-prompt-like block that sets Claude's role, tone, and behavior for every conversation in that project
- Knowledge files — PDFs, text files, code, docs up to 200,000 tokens total (~500 pages)
- Conversation history — all chats inside a project are grouped and searchable
Available on Claude Pro ($20/mo) and Claude Team ($25/user/mo, min 5 users). Free users see Projects but cannot create them.
Creating Your First Project
- Go to claude.ai and sign in to your Pro or Team account
- Click Projects in the left sidebar
- Click New Project — give it a clear name (e.g. "FastAPI Backend Helper", "Blog Writing Assistant")
- Click Edit project instructions to write your system instructions
- Click Add content to upload knowledge files
Every new chat you start inside that project will automatically load your instructions and knowledge — no re-pasting needed.
Writing Effective Custom Instructions
Custom instructions are the most powerful part of Projects. Think of them as a permanent system prompt. A good instruction block covers:
- Role — "You are a senior Python engineer with expertise in FastAPI and async I/O"
- Output format — "Always structure responses as: Problem → Root Cause → Fix with code"
- Stack context — "This project uses PostgreSQL, Redis, deployed on Fly.io"
- Rules — "Never suggest JavaScript solutions. Always use type hints."
Example: coding project instructions
You are a senior Python backend engineer. Always use type hints. Prefer dataclasses over dicts. Format responses as: Problem → Root Cause → Fix (with code). When reviewing code, check: security, performance, edge cases. Project context: FastAPI app, PostgreSQL, deployed on Fly.io.
Keep instructions under 2,000 tokens — longer instructions dilute focus. Test with a sample question after saving.
Uploading Knowledge Files
Each project holds up to 200,000 tokens of knowledge (~150,000 words). Supported formats: PDF, .txt, .md, .csv, .docx, and direct text paste.
| Use Case | Best Files to Upload |
|---|---|
| Coding assistant | README, architecture.md, API docs, key source files |
| Writing assistant | Brand voice guide, style sheet, sample articles, tone examples |
| Customer support | FAQ doc, product manual, return policy, pricing sheet |
| Research | Papers (PDFs), notes, reference documents, interview transcripts |
| Legal / HR | Contract templates, policy docs, compliance guides |
Tip: remove outdated files promptly — Claude references all uploaded knowledge and stale docs can generate incorrect answers.
Best Project Use Cases
💻 Coding Assistant
Upload your codebase README + architecture doc. Ask Claude to review PRs, debug errors, or write new features — it already knows your stack, conventions, and patterns.
✍️ Writing Style Guide
Upload your brand voice guide and 5 example articles. Every draft will match your tone without lengthy "write like this" instructions each time.
📄 Customer Support FAQ
Upload product docs, pricing, and FAQ. Draft support replies that are always accurate and on-brand — no more copy-pasting the FAQ URL.
🧪 Research Workspace
Upload PDFs of papers and notes. Ask Claude to find contradictions between sources, summarize findings, or draft a lit review — all in one place.
Projects vs Regular Chats vs API System Prompt
| Feature | Regular Chat | Projects | API System Prompt |
|---|---|---|---|
| Persistent instructions | ❌ Re-paste each time | ✅ Auto-loaded | ✅ Per-request |
| Knowledge files | ❌ | ✅ 200k tokens | ✅ In prompt |
| No code needed | ✅ | ✅ | ❌ Requires API |
| Team sharing | ❌ | ✅ Team plan | ❌ |
| Cost | Free / Pro | Pro ($20/mo) | Pay-per-token |
Team Collaboration on Claude Team Plan
On Claude Team ($25/user/mo, minimum 5 users), you can create shared projects where all team members work with the same instructions and knowledge base.
- Any team admin can create and edit shared projects
- All members see the same project instructions and files
- Individual conversations stay private within the project
- Great for: onboarding new hires, shared customer support, team research
Tip for teams: Create a "Company Context" project with your org chart, product overview, and style guide. New team members onboard by chatting with Claude inside it — no lengthy knowledge dumps required.
Pro Tips for Better Projects
- One project per domain: "Backend Code" and "Blog Writing" as separate projects beat one giant "Everything" project — focused context = better answers
- Test your instructions with edge cases: Ask Claude to do something your instructions should prevent — if it complies, tighten the rule
- Update files when docs change: Delete the old version and upload the new one — Claude will reference the latest
- Use the project name in your question: "Based on our FastAPI project context..." helps Claude activate the right mental frame
- Monitor Claude status: Projects run on Claude.ai — if Claude is degraded, check Anthropic API status at Prismix to know if it's a platform issue
Monitor Claude Availability
Claude Projects are only as reliable as Claude itself. Track Anthropic API and Claude.ai status in real time — get instant alerts when Claude goes down.
Monitor Claude Status Free →