Lesson 02 · Claude Mastery Pro ~14 min read 3 Project builds

Claude Projects: your personal research assistant.

Claude Projects is the feature most Claude users have never used — and it changes everything. A Project is a persistent workspace where Claude knows your context, your knowledge base, and your style across every conversation. This lesson walks the full setup of three different Projects: a personal research assistant, a writing partner, and a code review buddy.

The mental model

Projects are the difference between Claude-as-chat and Claude-as-coworker.

A normal Claude conversation is amnesiac — each chat starts fresh. A Project remembers: your custom instructions, your uploaded knowledge base (docs, PDFs, transcripts), and the style you've established. Every new chat inside the Project starts with all that context.

The Reframe

If you find yourself re-explaining the same context to Claude more than twice, you should be working in a Project. Setup is one-time; the payoff is every future conversation on that topic.

Workflow 01 Build a personal research assistant Project

1

Project: "My Research Assistant"

Set up a Project that knows your industry, your interests, and your past research notes. Every chat starts with that context.

The prompt that works

Setup walkthroughClaude → Projects → New Project → name: "Research Assistant" → Custom instructions: "You're my research partner. I work in [your field]. Bias toward evidence, flag your confidence level, link to sources when web-enabled. Never invent stats." → Upload: any background docs, papers, or notes that frame your work.

Best use cases

  • Industry-specific research (your sector, your competitors)
  • Topic deep dives (you investigate this topic across months)
  • Personal interests where context compounds (e.g., your reading list)
  • Anywhere you've found yourself re-pasting the same context
Don't upload sensitive data (customer info, contracts) unless you're on Claude for Enterprise with proper data agreements.
Time savings: Re-explaining context every session: gone forever.

Workflow 02 Build a writing partner Project

2

Project: "Writing Coach"

A Project that knows your writing voice and gives feedback or drafts in your style.

The prompt that works

Setup walkthroughNew Project → "Writing Coach" → Instructions: "You're my writing partner. My voice is [conversational, direct, uses contractions, avoids buzzwords]. When I share a draft, give specific feedback on clarity, voice, and structure. Never rewrite without permission." → Upload: 3-5 of your previous writing samples that exemplify your style.

Best use cases

  • Bloggers, newsletter writers, founders writing publicly
  • Anyone who needs writing to sound like THEM at scale
  • Drafting customer-facing copy that needs consistency
  • Practicing writing with a feedback loop
Don't ask the Project to write FOR you in your voice — that flattens you. Use it to give feedback on YOUR writing.
Time savings: Voice consistency without losing your authorship.

Workflow 03 Build a code review buddy Project

3

Project: "Code Reviewer"

A Project that knows your codebase conventions, your team's style guide, and your typical review priorities.

The prompt that works

Setup walkthroughNew Project → "Code Reviewer" → Instructions: "You review my code with these priorities: (1) correctness, (2) readability, (3) testability, (4) performance. Cite specific lines. Suggest improvements but don't rewrite unless asked." → Upload: your style guide, a few exemplar PRs, your test patterns doc.

Best use cases

  • Pre-PR self-review before sharing with the team
  • Learning a new language with feedback
  • Catching the bugs your linter misses
  • Mentor-style review when no human is available
Don't substitute Claude review for human review on critical code. The Project gives you a faster first pass, not the final word.
Time savings: Pre-PR review: 30 min → 5 min.

Final challenge: build one Project that pays off

Pick the topic you talk to Claude about most. Build a Project for it tonight. Spend 15 minutes on instructions and uploads. Use it for the next week. Notice how much faster every conversation becomes.

Back to Claude Mastery → See pricing →

What you can do now

  • Set up a Claude Project with custom instructions in under 5 minutes
  • Upload knowledge base files that give Claude persistent context
  • Decide what belongs in a Project vs. a one-off chat
  • Build domain-specific Projects (research, writing, code) for recurring work
  • Know what NOT to upload (sensitive data without enterprise agreements)
Pro
Up next in Claude Mastery

Lesson 3 · Artifacts: the side panel most Claude users ignore

When to invoke Artifacts, when to skip them, and the iterative-refinement workflow that turns Claude into a coding/writing partner instead of just an answer machine. See pricing →