← All posts
ClaudeClaude ProjectsAI toolsbeginnersno codetutorial

Claude Projects for Beginners: How to Make Claude Actually Remember You

If you've used Claude, you've hit this wall: you have a great conversation, close the tab, come back the next day, and Claude has no idea who you are. Your preferences, your context, your goals — all gone.

This isn't a bug. It's how Claude works by default. Each conversation starts fresh.

But there's a feature most people don't know about that changes everything: Claude Projects.

What Claude Projects actually are

A Claude Project is a persistent workspace inside Claude. You give it custom instructions and upload knowledge files, and every conversation you start inside that project has access to all of it.

Think of it like this:

  • Regular Claude = talking to a brilliant stranger every time
  • Claude Project = talking to a colleague who has your playbook, knows your preferences, and remembers the ground rules

The key difference: Claude Projects don't "remember" your conversations (they're still separate chats). But they give Claude a persistent context — your instructions, your preferences, your reference material — that carries across every conversation in the project.

Setting up a Claude Project (step by step)

This takes about 2 minutes. You need a Claude account (free or Pro).

Step 1: Create the project

  1. Go to claude.ai
  2. In the left sidebar, click Projects
  3. Click Create Project
  4. Give it a name — "Work Assistant," "Meal Planning," "Journal," whatever fits

Step 2: Add custom instructions

This is where the magic happens. Custom instructions are text that Claude reads at the start of every conversation in this project. It's like a briefing document.

  1. Open your project settings
  2. Find the Custom Instructions field
  3. Write (or paste) instructions that tell Claude who it should be and how it should behave

For example, a simple personal assistant:

You are my personal work assistant. My name is [your name]. I work in [your field].

When I ask you to draft emails, match my tone: professional but warm, direct, no fluff.

When I ask about scheduling, I'm in [timezone] and I don't take meetings before 10am.

When I ask you to review my writing, be honest and specific — don't just say "looks good."

Step 3: Upload knowledge files (optional but powerful)

Knowledge files are documents you upload to the project. Claude can reference them in every conversation.

Examples:

  • A style guide for your brand
  • Your company's product catalog
  • A list of your dietary restrictions and favorite foods
  • Templates for emails, reports, or plans

Upload them in the Knowledge section of your project settings. Claude reads them as context — it won't modify or delete them.

What makes a good project

The best Claude Projects have:

  1. Clear role definition — Tell Claude what it is. "You are a meal planning coach" is better than "help me with food."
  2. Specific preferences — The more Claude knows about you upfront, the less you have to repeat. Your name, your constraints, your goals, your style.
  3. Boundaries — What Claude should NOT do is as important as what it should. "Never give medical advice" or "Don't suggest recipes with cilantro."
  4. Structure — If you want Claude to follow a specific format (like a weekly meal plan table or a daily check-in flow), describe it in the instructions.

Common mistakes

Too vague: "Be helpful and nice." Every Claude conversation is helpful and nice. Instructions should add something Claude wouldn't do by default.

Too long: You don't need to write 10,000 words. A focused 200-500 word instruction set beats a sprawling essay. Claude needs clear direction, not a novel.

No boundaries: If you're using Claude for personal reflection or sensitive topics, define limits. What topics are off the table? When should Claude suggest professional help? Good instructions handle edge cases.

Forgetting knowledge files: Instructions tell Claude how to behave. Knowledge files give Claude what to know. The combination is what makes a project feel genuinely personalized.

Real use cases people are building

  • Journaling companion — Daily check-ins, reflection prompts, pattern recognition across sessions
  • Meal planning coach — Weekly plans, shopping lists, and recipe swaps based on your diet and budget
  • Study partner — Quizzes you on material, explains concepts at your level, tracks what you've covered
  • Writing coach — Edits in your style, catches your specific bad habits, adapts feedback to your goals
  • Career advisor — Preps you for interviews, reviews your resume, practices tough conversations

The shortcut: Claude Project Kits

If you don't want to write instructions from scratch, pre-built Claude Project Kits exist. They're downloadable file sets — system instructions, knowledge files, onboarding templates — that you paste into a project and start using immediately.

The good ones publish their instructions openly so you can read exactly what Claude is told before you buy. The not-so-good ones don't. Choose accordingly.

Getting started

Open Claude. Create a project. Write three sentences about who Claude should be for you. Start a conversation.

You'll immediately notice the difference. Claude with context is a different experience than Claude without it. And once you've set up one project, you'll want to set up five.

Every instruction we sell is public.

Read the kits on GitHub before you decide. No black boxes.