2-1-projects

--- title: "Claude Projects: Persistent Memory and Always-Active Context" description: "Claude Projects change the way you work. Set permanent instructions, upload reference documents, and stop repeating context every single conversation." slug: "2-1-projects" enslug: "2-1-claude-projects" accesslevel: registered status: published visible: true featured: true priority: 21 date: 2026-04-22 updated: 2026-04-22 author: "Dario Santocanale" reading_time: "8 min" prerequisites: - Active Claude Pro plan - Completed Cluster 1 tutorials tags: [claude, projects, memory, pro, advanced, workflow] ---

If every time you open Claude you have to re-explain who you are, what you do, and how you want it to respond, you're wasting time. Projects eliminate this problem once and for all.

---

What is a Project

A Project in Claude is a dedicated workspace with three components:

1. Project instructions (permanent system prompt): text Claude reads at the start of every conversation in the project
2. Reference files: documents, guides, guidelines that Claude can consult
3. Organized conversations: all project-related chats in one place

The difference from a normal chat: the instructions and files are always present, without you having to paste them again every time.

---

Creating your first Project

1. In the left sidebar of claude.ai, look for "Projects" or click the + next to "Projects"
2. Give the project a name (e.g., "Content Blog", "Client Smith", "Market Research")
3. In the "Project instructions" section, write your permanent instructions

How to write project instructions

The project instructions are your permanent "system prompt." They're read by Claude before every conversation in that project.

Template for freelancers/consultants:

You are my assistant for [project/client name].

CONTEXT:
- Client: [Company name]
- Industry: [Industry]
- Project goal: [What we're working on]

HOW TO RESPOND:
- Tone: [formal/informal/technical]
- Language: English, always
- Preferred format: [bullet points/prose/tables]
- Response length: [concise/detailed]

THINGS YOU ALREADY KNOW ABOUT ME:
- [Info you don't want to repeat every time]

NEVER:
- [Behaviors you want to avoid]

Template for a creative project:

We're working on a technology blog for professional readers.

EDITORIAL GUIDELINES:
- Tone: direct, no unnecessary jargon, practical examples always
- Article length: 1200-1800 words
- Structure: hook intro + problem + solution + practical example + CTA
- Words to avoid: "revolutionary", "game-changer", "synergy"
- Preferred words: concrete, practical, measurable

STYLE:
- First person when useful
- Specific data and numbers when possible
- Rhetorical questions only at the beginning

---

Adding files to a project

Files in a project are documents Claude can consult in every conversation.

What to upload:

• Brand or client guidelines
• Company policy documents
• Templates you use frequently
• Style guides
• Industry FAQs
• Technical reference documents

How to do it:

1. Open the project
2. Click "Add content" or the upload icon
3. Upload files (PDF, Word, TXT, code) or paste text

Practical limit: there's a storage limit for files (depends on plan). For huge documents, consider uploading only relevant sections or a summary.

---

Practical workflow: Project for a client

Here's how I use Projects in practice for a consulting client:

Project structure:

📁 Project: Client ABC
├── 📝 Instructions: who the client is, tone of voice,
│   Q2 goals, what not to say
├── 📄 brand-guidelines.pdf
├── 📄 target-personas.md  
├── 📄 editorial-calendar-template.xlsx
└── 💬 Conversations:
    ├── April newsletter
    ├── Social media copy
    └── New campaign proposal

Workflow:

1. Open the project once and set everything up
2. Create each new task as a new conversation inside the project
3. Claude already knows the client, style, constraints
4. Save 2-3 minutes of setup per session

---

Ideal use cases for Projects

Use case	What to put in instructions	Useful files
Blog / content	Editorial guidelines, target, keywords	Brand guide, competitor analysis
Consulting client	Who they are, goals, communication	Client docs, contract
Study / research	Topic area, technical level	Papers, research notes
Software development	Tech stack, coding style, naming	README, project docs
Sales / CRM	Product, common objections, tone	Product sheets, sales script
Personal	Who you are, goals, preferences	CV, personal notes

---

Projects vs Custom Instructions

Before Projects, Claude had Custom Instructions (global settings). The difference:

	Custom Instructions	Projects
Scope	All conversations	Only conversations in the project
Attached files	No	Yes
Count	1 configuration	Unlimited
Organization	Single	Per project/client

Tip: use Custom Instructions for global preferences (e.g., "always use British English") and Projects for specific contexts.

---

Project limitations

• Requires Pro or Team plan (not available on Free)
• Files have a total size limit per project
• Conversations in a project don't connect to each other — Claude doesn't automatically read previous chats in the project (only instructions and files)
• Instructions have a character limit (~2000 words approx.)

---

Up next →2-2-artifacts