Claude Projects are the most underused feature in AI right now. Most people use Claude like a search engine — type a question, get an answer, start over. Projects change that completely.
A Claude Project is a persistent workspace where Claude knows your business. Your brand voice. Your SOPs. Your codebase. Your client data. Instead of re-explaining context every conversation, you set it once — and Claude remembers.
I use Projects for everything: writing in my voice, analyzing client data, managing my course content, even debugging code. Here is exactly how to set them up and the five project types that will change how you work.
What You Need Before Starting
Claude Projects require a paid plan:
- Claude Pro ($20/month) — personal use, up to 5 Projects
- Claude Teams ($30/user/month) — shared Projects across your team
Free-tier Claude does not support Projects. If you are deciding whether to upgrade, Projects alone justify the cost — they save hours per week once configured.
Step 1: Create Your First Project
- Open claude.ai and click Projects in the left sidebar
- Click Create Project
- Name it something specific — not "Marketing" but "Q2 Email Campaign — Product Launch"
- Add a description (optional but helps you find it later)
That is it. Your workspace exists. Now make it useful.
Step 2: Write Custom Instructions That Actually Work
Custom instructions are where the magic happens. This is your chance to tell Claude exactly who it is, what it knows, and how it should behave inside this Project.
Most people write vague instructions like "Be helpful and professional." That is wasted potential. Here is what good instructions look like:
You are my content strategist for Like One Academy.
CONTEXT:
- We sell AI education courses at likeone.ai
- Our audience: professionals who want to use AI at work but feel overwhelmed
- Tone: direct, warm, practical. Never corporate. Never condescending.
- We use "you" not "one" — we talk TO people, not AT them.
RULES:
- Every piece of content must have a specific takeaway the reader can use today
- Never use jargon without explaining it in plain language first
- Always include at least one real example (not hypothetical)
- Format for scanning: short paragraphs, headers, bullet points
WHEN I ASK YOU TO WRITE:
- Draft in my voice (reference the uploaded writing samples)
- Include a hook in the first two sentences
- End with a clear call-to-action
Notice the structure: Context → Rules → Behavior. This is the formula. Claude needs to know who it is working for, what constraints to follow, and how to respond to different requests.
Step 3: Upload Your Knowledge Files
This is what makes Projects powerful. Upload documents and Claude can reference them in every conversation inside this Project.
What to upload:
- Brand guidelines — voice, tone, visual identity docs
- SOPs and processes — how your team does things
- Product docs — features, pricing, FAQs
- Writing samples — 5-10 examples of your best content
- Data files — CSVs, reports, spreadsheets for analysis
- Code — repository files, API docs, schemas
What NOT to upload:
- Sensitive credentials or API keys
- Files larger than what you need (trim to the relevant sections)
- Entire books when you only need specific chapters
The 200K token context window is generous but not infinite — roughly 500 pages of text. Be strategic about what goes in.
Step 4: Test and Iterate
Your first version will not be perfect. That is fine. Use the Project for a day, notice where Claude gets things wrong, and refine your instructions.
Common iterations:
- "You keep using passive voice — always use active voice"
- "When I say 'draft a post,' I mean LinkedIn, not blog. Default to LinkedIn unless I specify."
- "Stop adding emoji unless I ask for them"
Each refinement makes the Project smarter. After a week of tuning, you will have an AI assistant that genuinely understands your work.
The 5 Project Types Every Professional Should Build
1. The Voice Clone
Purpose: Write content that sounds like you.
Upload 5-10 of your best pieces (blog posts, emails, social media posts). In the instructions, describe your voice: sentence length, vocabulary preferences, topics you always cover, phrases you use.
Real result: I write 3x more content per week because my Voice Clone drafts are 80% ready on the first try.
2. The Knowledge Base
Purpose: Instant answers from your documentation.
Upload your company wiki, SOPs, product docs, and FAQs. Claude becomes a team member who has read everything and can answer questions instantly.
Best for: Onboarding new employees, answering customer questions, finding information buried in documents.
3. The Data Analyst
Purpose: Explore and analyze your data conversationally.
Upload CSVs or data exports. Ask Claude to find trends, create summaries, compare periods, identify outliers. No SQL needed.
Example prompt: "Compare our March revenue to February. What products grew? What declined? Give me the top 3 things I should focus on."
4. The Code Partner
Purpose: A developer who knows your codebase.
Upload your key files — schema definitions, API routes, configuration files, README. Claude can then write code that fits your existing patterns, debug issues in context, and suggest improvements that align with your architecture.
Pro tip: Upload your style guide and linting rules so generated code matches your conventions.
5. The Strategy Advisor
Purpose: A thinking partner with full business context.
Upload your business plan, competitive analysis, market research, and financial projections. Use this Project for brainstorming, planning, and pressure-testing ideas.
Example prompt: "We are considering adding a $99 lifetime tier. Based on our current pricing and conversion data, what are the risks? What would the break-even look like?"
Advanced Tips
Use Projects With Claude's Extended Thinking
When you need Claude to reason deeply — complex analysis, multi-step planning, nuanced writing — enable Extended Thinking inside a Project. Claude will think through the problem step by step using all your uploaded context.
Combine Projects With MCP
If you use Claude Code or the Claude desktop app, MCP (Model Context Protocol) servers can connect Claude to live data — databases, APIs, file systems. Projects handle static context; MCP handles dynamic context. Together, they make Claude extraordinarily capable.
Want to learn MCP in depth? Check out the MCP Masterclass in our academy.
Share Projects With Your Team
On Claude Teams, you can share Projects with colleagues. Everyone gets the same context, same instructions, same knowledge base. This means consistent output across your team — no more "Claude gives me different answers than it gives you."
Common Mistakes to Avoid
- Too-vague instructions — "Be helpful" teaches Claude nothing. Be specific.
- Too much uploaded context — 500 pages of everything is worse than 50 pages of the right things. Curate.
- Never iterating — Your first instructions will have gaps. Refine weekly.
- Using Projects for one-off tasks — Projects shine for repeated work. One-time questions belong in regular chats.
- Forgetting to update files — If your SOPs change, update the Project. Stale context creates stale output.
Start Building Today
The gap between people who use Claude casually and people who use Claude Projects is enormous. One types prompts. The other has an AI team member who knows their business inside out.
Start with one Project — the Voice Clone is the easiest win. Upload your writing samples, write clear instructions, and test it for a week. You will not go back to vanilla Claude.
Want to go deeper? The Claude Mastery course covers Projects, Extended Thinking, MCP, and advanced prompting techniques across 10 hands-on lessons. First 3 lessons are free.