Claude Projects: How to Set Them Up So They Actually Help

Claude Projects are the simplest upgrade most teams never make. Instead of pasting your brand guide into every chat, you create a workspace once, add the files and instructions Claude should always use, and every conversation inside it starts with that context. Set up well, projects turn generic answers into work that sounds like your company.

Here's what projects are, the limits by plan, how to write instructions that work and five setups worth copying.

What are Claude Projects?#

The Claude Help Center describes projects as self-contained workspaces with their own chat histories and knowledge bases. Each project has three parts:

• Project knowledge: documents, text, code or other files you upload.
• Project instructions: custom guidance for how Claude should respond in that project, such as tone, role or format.
• Chats: every conversation inside the project, all starting from the same context.

When Anthropic launched Projects, the pitch was grounding Claude in your internal knowledge: style guides, codebases, interview transcripts or past work. That's still the best way to think about them.

Free vs paid: limits that matter#

Source: Claude Help Center. Pro costs $20 a month, or $17 billed annually, on Anthropic's pricing page.

The retrieval detail matters for marketing teams with large libraries. Paid plans switch to retrieval automatically when project knowledge approaches the context limit, so you can keep more reference material without trimming it by hand.

How project knowledge works#

Claude reads project knowledge as background for every chat. That makes it powerful and dangerous in equal measure: it will use whatever you put there, including the outdated pricing sheet from last year.

Rules I give every team:

1. One source of truth per topic. One brand guide, one product sheet, one audience doc.
2. Name files clearly, like brand-voice-2026.md, not final-v3-new.docx.
3. Include examples of great work. Three strong past pieces teach tone faster than a page of adjectives.
4. Remove old versions the day you upload new ones.

Writing project instructions#

Instructions are where most projects fail. "Be professional and helpful" changes nothing. Useful instructions cover:

• Role: "You are the content lead for [company], writing for [audience]."
• Standards: tone, reading level, banned words and claims you never make.
• Process: "Ask up to three clarifying questions before drafting anything longer than 300 words."
• Missing information: "If a fact isn't in the project knowledge, say so. Don't guess."
• Format: the default structure for outputs.

These follow the same structure as my AI prompts for marketing: context, task, constraints, examples and format. The difference is that instructions apply to every chat in the project.

Five Claude Projects worth setting up#

1. Brand voice studio. Voice guide, messaging pillars, five best-performing pieces. Use it for every piece of copy.
2. Customer research hub. Reviews, call transcripts and survey exports. Ask for objections, language patterns and quotes.
3. Campaign workspace. One per campaign: brief, audience, offer details and results as they come in.
4. Sales enablement. Product sheets, pricing rules, case studies and objection handling for fast, accurate proposal drafts.
5. Onboarding assistant. Processes, tool guides and FAQs so new hires can ask before they interrupt someone.

Claude Projects vs skills vs Cowork#

• Projects hold context for an area of work.
• Skills package a procedure Claude follows whenever a task matches, in any chat.
• Cowork executes multi-step tasks on your files and tools.

A mature setup uses all three: a project for brand context, a skill for the review checklist and Cowork to produce the weekly report. Claude artifacts then turn outputs into shareable documents and tools.

Common Claude Projects mistakes#

• One giant project for everything. Mixing brand, sales, HR and product docs makes Claude pull the wrong context. Split by area of work.
• Instructions that describe personality instead of standards. "Friendly and professional" doesn't change output. Banned claims, required structure and examples do.
• Uploading raw dumps. Two hundred unlabeled files are worse than ten clean ones. Curate before you upload.
• Never testing the setup. After creating a project, ask five questions you already know the answers to. Wrong answers show which file or instruction is missing.
• Forgetting to update. When prices, offers or positioning change, update the project the same day, or every chat inherits the old version.
• Using projects for procedures. If you find yourself pasting the same step-by-step process into instructions for several projects, that process belongs in a skill.

Sharing projects with a team#

On Team and Enterprise plans, the Help Center lists two permission levels: "Can view" to chat inside the project, and "Can edit" to change instructions, knowledge and members. You can share with individuals, by email in bulk or with the whole organization, unless an admin disables it.

My recommendation: one owner with edit rights per project, everyone else on view. Shared projects with ten editors drift fast.

The free Claude 101 lesson on projects covers the basics. If you want your team's projects, instructions and skills built around your real work, that's part of my team training.