← All articles

How to use Claude Projects: the 10 every Pro user should run

Claude Projects are the most underused feature in Claude.ai. Here's how to set them up properly — with the 10 specific Projects that compound your Claude usage. Custom Instructions, Knowledge files, the architecture.

Better with Claude · tutorial

How to use Claude Projects: the 10 every Pro user should run

The single biggest leverage point most Claude users miss isn't a better prompt, a different model, or a paid plan. It's using Claude Projects.

Most people open Claude.ai, type a question, get an answer, and close the tab. Power users run 5–15 specialized Projects — each one a tailored Claude with its own personality, rules, and reference files. The difference in output quality is dramatic. You stop re-explaining yourself. Claude stops giving you generic answers.

This guide covers what Projects actually are, how to set one up well, and the 10 specific Projects every Pro-tier user should have running.

What Claude Projects actually are

The mental model that helps: a Project is Claude with a job description, a folder of reference materials, and a personality. Three layers stack:

claude.ai/project/marketing-writer
CUSTOM INSTRUCTIONS
You are a senior product marketing manager with 10 years at B2B SaaS companies. Voice: clear, specific, never salesy. Default format: structured prose, no bullets…
KNOWLEDGE · 3 FILES
📄 style-guide.pdf📄 brand-voice.md📄 past-launches.pdf
  1. Custom Instructions — the job description. Always loaded into every conversation in this Project.
  2. Knowledge (files) — the reference folder. PDFs, markdown, anything you upload. Claude references these when relevant.
  3. Conversation memory — what you've discussed in this Project carries across sessions.

Available on the Pro plan and above. If you're on Free, this article is your reason to upgrade — Projects are the single feature that justifies the subscription.

How to set up a great Project

The default mistake is treating Custom Instructions like a chat message. They're not. Treat them like a job posting. Six sections that consistently outperform vague paragraphs:

1. Role

Specific. Not "writing assistant" but "senior product marketing manager with 10 years at B2B SaaS companies."

2. Voice

How they sound. "Clear, specific, never salesy. Sounds like a knowledgeable peer, not a marketer."

3. Default format

Most outputs look like X. "Structured prose. No bullets unless I ask. Headlines in sentence case."

4. Always

Non-negotiables. "Lead with a user outcome, not a feature. Use concrete numbers when possible. Cite sources."

5. Never

The bigger half. "Never use ‘leverage,’ ‘synergize,’ or ‘unlock.’ Never open with ‘In today's fast-paced world.’"

6. What good looks like

The quality bar. "Copy a busy CTO would read to the end and forward to her team."

That last line is often the single most useful sentence in the entire instruction block. It gives Claude a concrete quality target instead of guessing.

Picking the right Knowledge files

Three to five curated files beats 50 random ones. Files that compound:

  • Style guides — Claude matches the voice automatically. Write one if you don't have it.
  • Past examples of "good" — 3-5 deliverables you'd want to emulate. Claude reverse-engineers the patterns.
  • Vocabulary / glossary — domain terms your industry uses.
  • A one-pager on your business — product, customers, positioning.

Files that hurt: 200-page PDFs that bury the signal, outdated docs Claude will treat as current, multiple conflicting versions of the same doc. Curate ruthlessly. Re-audit every few months.

The 10 Projects every Pro user should run

If you want a starting set, this is the menu most people benefit from. Pick 5-7 that match your work — add the rest over a month.

  1. Email Writer — Your voice, your common scenarios (cold outreach, internal updates, customer responses). Upload your last 10 good emails as Knowledge.
  2. Brainstorming Partner — Instructed to push back, not just agree. "Critique my idea before extending it."
  3. Code Reviewer — Your stack, your standards. Upload your linting rules and style guide. Drops one file → gets a senior-engineer review.
  4. Meeting Prep — Type the meeting topic + attendees. Get an agenda + talking points + likely objections + recommended close.
  5. Document Reader — Upload long PDFs → get summaries, critiques, action items. Works for board decks, customer interviews, research papers.
  6. Daily Journal Coach — Asks reflective questions. Surfaces patterns from last week's entries.
  7. Decision Maker — Frameworks for comparing options. Pre-loaded with the analytical structures you trust.
  8. Writing Editor — Your style guide loaded. Harsh and specific. "What are the 3 weakest paragraphs and how would you rewrite them?"
  9. Pitch Sharpener — Turns vague ideas into 30-second pitches. Pre-trained on good pitches you admire.
  10. Career Advisor — Your background loaded. Advice on roles, salary negotiations, growth.

Long conversations live inside Projects

One non-obvious benefit: long-running chats work much better inside Projects. The Custom Instructions re-anchor each turn — Claude doesn't drift the way it does in plain chat threads. You can have 50-message conversations with a Project Claude and it stays sharp.

Plain chat: starts strong, degrades after 10 messages.
Project chat: stays consistent for 30-50+ messages because the system prompt re-anchors.

What to do this week

Open Claude.ai. Click Projects → + New Project. Name it for one job you do weekly. Write the 6-section Custom Instructions block. Upload 3 files. Start a conversation.

Sixty seconds of setup. Lasting leverage. The compounding starts when you have 5+ running — every email, every doc, every decision routed to the right specialist.

Related articles

tutorial
How to write Claude Custom Instructions that actually work
9 min
tutorial
Claude Code for non-developers: 10 practical use cases
10 min
tutorial
The 5 Claude prompt patterns every user should know
8 min
How to use Claude Projects: the 10 every Pro user should run · Better with Claude