AI & Agentic

Claude Projects: The AI Workspace That Remembers Your Context

Claude Projects lets you create a dedicated workspace with persistent custom instructions and knowledge files - so you never have to re-explain your context in every new chat.

What is Claude Projects?

Every time you open a new AI chat, you have to explain again: “I’m a marketer, working for company X, target audience is Y, writing tone is Z…” before the AI can do anything useful. Claude Projects solves exactly this problem.

What is Projects?

Projects is a Claude feature (available on Claude Pro and Claude for Work) that lets you create a dedicated workspace with:

  • Custom Instructions: AI “remembers” your context, role, and rules permanently within that project - no need to repeat them
  • Project Knowledge: Upload files, paste documents - AI reads them and references them when responding
  • Separate chat history: All conversations within a project are grouped by topic

The result: you don’t have to re-explain from scratch every session. AI understands your context the moment you open a chat.


How is it different from a regular chat?

Regular chatClaude Projects
ContextResets with each new chatPersists permanently
Reference filesRe-upload every timeUpload once, use indefinitely
InstructionsMust repeat each sessionSet once, AI always remembers
OrganizationAll chats mixed togetherClearly separated by project

How to create a Project

  1. Go to claude.ai - select Projects in the left sidebar
  2. Create a new project, name it by topic
  3. Write your Project Instructions - this is the most important part
  4. Upload Project Knowledge if you have reference documents

Example Project Instructions for a Marketer:

You are a content assistant for [Brand name] - a personal brand
in the [topic] space.

Target audience: [audience description]

Writing tone:
- LinkedIn: Professional, peer-to-peer, use first person
- Social: Short, conversational, 500 characters max per post

Rules: No hashtags unless requested.
Short sentences, no filler. No em dashes.

Real-world use cases

Content Creator: One project per brand or client - AI remembers the voice, style guide, and target audience. No need to paste the brand guidelines at the top of every prompt.

Developer: One project per codebase - upload README, schema, tech stack. AI understands the full context when reviewing code or suggesting implementations.

Researcher / Analyst: One project per research topic - upload papers and reports. AI references the right documents when answering instead of giving generic responses.

Marketer handling multiple clients: Separate project per brand - prevents mixing up tone and context between clients.


Limitations to know

  • Only available on Claude Pro (paid) - free tier does not include Projects
  • Project Knowledge has a storage limit (varies by plan)
  • Instructions are not “magic” - AI can still fail to follow them if the in-chat prompt directly contradicts the instruction
  • Knowledge files have a freshness limit - uploaded files do not update in real time

Starter kit - 3 ready-to-use instruction templates

Copy and adjust to your needs:

Template 1: Content / Personal Brand

You are a content assistant for [Name] - [role] specializing in
[topic].

Audience: [brief description, e.g. marketers 25-35, working at tech companies].

Channels and tone:
- LinkedIn: Professional, peer-to-peer, first person.
  No hashtags. Structure: short hook -> bullet body -> lesson -> CTA.
- Social (short-form): Casual, conversational, max 500 characters per post.
  If longer, split into a thread.

General style: short sentences, no fluff, no em dashes.

Template 2: Researcher / Knowledge Worker

You are my research assistant.

Topic I'm researching: [topic]
My background: [role, knowledge level]

When responding: always clearly distinguish between "verified fact"
vs "inference/hypothesis".
If unsure about a piece of information, say so instead of guessing.

Preferred output: bullet points, clear headings,
with "Next questions to explore" at the end of each response.

Template 3: Developer / Technical

You are a senior [language/framework] developer doing pair
programming with me.

Stack in use: [list tech stack]
My level: [junior/mid/senior]

Rules:
- Explain "why" before showing code
- If there are trade-offs, present both options
- Code must have comments explaining non-obvious parts
- If you need more context to give a better answer, ask me first

Summary

Projects = AI remembers context, you save time re-explaining every session. For daily AI users, this is the highest-ROI feature available.

Start simple: copy one of the 3 templates above, adjust to your needs, run it for a week - then refine based on actual output.


Structured Prompting: The RTFC Framework for Better AI Output

✦ Miễn phí

Muốn nhận thêm kiến thức như thế này?

Mình tổng hợp AI, marketing và tech insights mỗi tuần - gọn, có gu.

Không spam. Unsubscribe bất cứ lúc nào.