Persistent Context — Projects, Instructions & Files

The Problem with Regular Chats

Every time you start a new chat in Claude, it knows nothing about you. You have to re-explain who you are, what your company does, your writing style preferences, your audience — every single time.

After a week of this, it gets tedious. Claude Projects solve it.

What Are Claude Projects?

Projects are a feature in Claude that lets you:

Set persistent context — instructions that Claude follows in every conversation within that project
Upload reference documents — files Claude can refer to in any conversation
Keep conversations organized by topic

Think of a Project as a briefed Claude instance. You do the briefing once, and every conversation in that project benefits from it.

Setting Up Your First Project

In Claude.ai, look for Projects in the left sidebar
Click New Project
Give it a name (e.g., "Work", "Content Creation", "Side Project")
You'll see an option to add Project Instructions — this is your persistent context

Writing a Good Project Instructions (System Prompt)

This is where you tell Claude everything it needs to know to help you well. Here's a template:

## About Me
[Your name, role, industry, company description if relevant]

## My Goals
[What you're trying to accomplish in this project area]

## My Audience
[Who I'm communicating with, their background, what they care about]

## Tone & Style Preferences
[How I like to communicate: formal/casual, length preferences, things to avoid]

## Important Context
[Anything specific Claude should always know — constraints, preferences, recurring references]

## How I Want You to Respond
[Format preferences, when to ask clarifying questions vs. just respond, etc.]

Example Project Instructions: Content Creator

## About Me
I'm a solo content creator in the B2B SaaS space. I run a newsletter with 8,000 subscribers and post on LinkedIn 3x per week. My topics: startup operations, productivity, and building with AI tools.

## My Audience
Founders and operators at companies of 10–100 people. They're smart, busy, and skeptical of hype. They want concrete, actionable advice.

## Tone & Style
- Direct and confident. Never wishy-washy.
- Short sentences. No fluff.
- Use analogies to make abstract ideas concrete.
- Never start with "In today's fast-paced world" or similar clichés.
- Occasional dry humor is fine; never try-hard.

## Important Context
- I publish every Tuesday. Deadline mindset.
- My best-performing posts are contrarian takes or tactical how-tos.
- I avoid vendor names in editorial content.

## How I Want You to Respond
- Give me drafts, not just advice.
- If I ask for options, give me 3 and tell me which you'd pick.
- Push back if my premise seems weak.

Example Project Instructions: Developer (for Module 3+)

## About Me
I'm a non-technical founder learning to build with Claude Code. I'm building a [describe your app idea].

## Tech Stack
- Frontend: Next.js
- Database: Supabase
- Deployment: Vercel
- Language: TypeScript

## My Level
I'm a beginner. Explain things clearly. When writing code, add brief comments so I understand what each section does. Don't use jargon without explaining it.

## Communication Style
- Be direct about when something is a bad idea.
- If there are multiple ways to do something, tell me the tradeoffs.
- When I paste an error, tell me what caused it, not just how to fix it.

Uploading Reference Documents to a Project

Within a project, you can also upload files that Claude can reference:

Brand guidelines — so it always writes in your brand voice
Product documentation — so it knows your product inside out
Meeting notes — so it has context on what's been decided
A style guide — for consistent writing

To upload: open a Project → click the attachment icon or "Add files" → upload your documents.

Claude will now be able to reference these in every conversation within the project.

Practical Project Ideas

Project Name	Purpose	Key Instructions to Set
Work	General work tasks	Your role, company, communication style
Marketing	Writing and campaigns	Brand voice, audience, content rules
My App	Building your side project	Tech stack, app description, your level
Personal	Personal tasks	Your preferences, relevant life context
Research	Deep dives on topics	How you want information structured

Persistent Context Beyond Chat: Cowork

Projects live in Chat (claude.ai) — the cleanest way to brief Claude once and reuse it across conversations. When you move to Cowork, the same principle applies but it works through your files:

Keep a context file in your working folder. Drop a context.md (or a style guide) into the folder Cowork works in — who you are, your standards, your formats — and tell Cowork to follow it. Now every task in that folder starts already "briefed," exactly the way a Project briefs a chat.
The work itself persists. Because Cowork edits and saves real files, your outputs and notes stay on disk between sessions — there's nothing to re-paste.
Pair it with Skills (Lesson 5) for the tasks you repeat.

Same idea in both places: brief Claude once, benefit every time — through Project instructions in Chat, and through a context file plus your folders in Cowork.

When NOT to Use Projects

Projects are great for recurring work. But sometimes a fresh chat is better:

Sensitive one-off tasks you don't want mixed with other context
Experiments where you want Claude's "default" behavior
Topics completely unrelated to any of your projects

Summary

Projects give Claude persistent context across all conversations in that project
Write detailed Project Instructions (a system prompt) to brief Claude once
Upload reference documents for things Claude should always know
Create separate projects for different areas of your life/work
In Cowork, get the same persistence by keeping a context.md in your working folder — brief once, benefit every task