Claude Projects Setup Guide for Professionals (2026)

Most professionals who try Claude give up within a week. Not because it doesn't work, but because they're using it wrong: as a one-off chatbot where every conversation starts from scratch. The fix is Claude Projects, and the fix takes about 30 minutes to set up properly.

This is the canonical guide for turning Claude into a coworker. Follow it once and you'll never have to re-explain yourself to Claude again.

What a Claude Project actually is

A Project in Claude.ai is a persistent workspace with three parts:

1. Custom instructions — a text block that Claude reads at the start of every conversation in the Project. This is where your voice, your rules, and your context live.
2. Project knowledge — documents you upload once that Claude can reference across all conversations in the Project.
3. Chat history — every conversation you've had inside the Project, searchable and organized.

Once you've set up a Project, every new chat inside it starts with Claude already knowing who you are, how you write, and what you care about. No more re-explaining.

The four-part custom instructions structure

The single biggest mistake professionals make is writing vague custom instructions. "Be helpful and professional" is not an instruction. It's a wish. Use this structure instead:

1. Profile. Who you are, what you do, who you serve, what constraints you work under. For a paralegal, this might be "I'm a paralegal at a mid-size commercial litigation firm. I support three partners. I draft discovery requests, summarize depositions, and prepare exhibit binders. I'm not a lawyer and I never give legal advice."

2. Voice. How you write. Specific examples beat adjectives. "Short sentences. No filler. Use contractions. Never use 'unlock,' 'leverage,' or 'seamless.' Prefer concrete examples over abstract claims." If you have a writing sample you're proud of, paste a paragraph of it and say "match this tone."

3. Rules. Hard constraints that must never be violated. "Never invent facts I didn't provide. Never include patient identifiers in outputs. Always tie clinical language to documented findings." This is where professional defensibility lives. Be explicit. Claude will follow explicit rules.

4. Formatting. What outputs should look like. "Default to bullet points for lists longer than three items. Never use headers in short replies. Always put action items at the top of a response, not the bottom." The more specific you are, the less editing you do later.

A well-built custom instructions block is usually 200 to 500 words. Much shorter and it's too vague. Much longer and Claude starts losing pieces of it in long conversations.

What to upload to project knowledge

Project knowledge is for reference material, not for working documents. Good candidates:

• Your style guide or voice guide. If your firm has one, upload it. If not, write a one-pager and upload that.
• Templates you reuse. Standard engagement letters, SOAP note templates, listing description templates, proposal skeletons.
• Policy documents you reference constantly. A pharmacy's formulary rules. A firm's conflict-check process. A brokerage's disclosure requirements.
• Examples of good outputs. Three or four real examples of work you're proud of. Claude learns your standards from examples faster than from descriptions.

Bad candidates for project knowledge: individual client files, patient charts, one-time matter documents, anything confidential that shouldn't live in a long-lived workspace. Those belong in the chat itself, not in persistent knowledge.

How to maintain a Project over time

Projects decay if you don't maintain them. Here's the maintenance cadence that actually works:

Weekly (5 minutes). Skim your recent chats. If you caught yourself re-prompting Claude for the same correction twice, add that correction to your custom instructions. Every correction you add is one you'll never make again.

Monthly (15 minutes). Re-read your custom instructions top to bottom. Remove anything that's no longer true. Add anything that's become standard. Delete rules you've stopped caring about.

Quarterly (30 minutes). Audit your project knowledge. Remove outdated templates. Add new reference documents. Make sure nothing in there is stale or contradictory.

Profession-specific examples

The AI Career Lab cowork guides give you worked examples for specific professions. A few good starting points:

• /professions/therapist for clinical documentation workflows
• /professions/attorney for legal drafting and review
• /professions/real-estate for listing, marketing, and client communication
• /professions/financial-advisor for compliance-aware client communication
• /professions/management-consultant for proposals, decks, and client memos

Each profession page links to worked cowork setups with example custom instructions and knowledge you can copy and adapt.

The 30-minute version

If you want the fastest possible setup: create a new Project, paste a four-part custom instructions block (profile, voice, rules, formatting), upload two or three reference documents, and start using it. Refine weekly. Don't overthink the first version.

A rough Project you actually use beats a perfect Project you never ship. Start messy. Maintain consistently.

Create your free AI Career Lab account at /sign-up to access profession-specific cowork guides and templates.