# Give Claude lasting context with Projects

> Set up a Claude Project with files and instructions so every chat about a client, product or topic starts with the right background.

Source: https://viralistic.nl/help/claude/projects

A Project is a workspace in Claude that holds background files, standing instructions and all chats about one subject. Instead of pasting the same brief into every new chat, you set it up once. This article shows how to create a Project, what to put in it and how to keep it useful.

## When a Project helps

Use a Project when you keep coming back to the same subject with the same background. Good examples:

- One client: their brand guide, tone of voice, product list and contacts.
- One product or website: specs, sitemap, FAQs and past decisions.
- One recurring job: monthly reporting, newsletter writing, sales proposals.

A one-off question does not need a Project. A normal chat is fine.

## What a Project contains

| Part         | What it does                                                                                      |
| ------------ | ------------------------------------------------------------------------------------------------- |
| Instructions | Rules Claude follows in every chat in the Project, such as tone, language and format              |
| Knowledge    | Files and text Claude can use as background in every chat                                         |
| Chats        | All conversations you start inside the Project, kept together                                     |
| Memory       | On plans with memory turned on, each Project keeps its own memory, separate from your other chats |

## Create a Project

1. Open Claude and go to **Projects** in the sidebar (or visit claude.ai/projects).
2. Click to create a new Project.
3. Give it a clear name, such as "Client: [client name]" or "Monthly newsletter".
4. Add a short description so you and your colleagues know what it is for.
5. On Team and Enterprise plans, choose whether to keep it private or share it with your organisation.

> **Note:** Projects are available on every plan, including Free. Free accounts can create a small number of Projects; paid plans have room for more.

## Write the instructions

Instructions are the standing brief. Keep them short and concrete. Write them as you would brief a colleague on day one.

1. In the Project, find the option to set project instructions.
2. Paste or write your instructions.
3. Save.

An example:

```text
You help me write content for [client name], a family bakery in
Utrecht.

- Write in Dutch unless I ask otherwise. Use "je", not "u".
- Tone: warm, plain, a little playful. No hype words.
- Never invent prices or opening hours. Use the price list in the
  knowledge files, or ask me.
- For social posts: max 120 words, no hashtags in the body.
- When something is unclear, ask one question before you start.
```

> **Tip:** If you notice yourself correcting Claude on the same thing twice, add it to the instructions.

## Add knowledge

Knowledge is the reference material Claude can draw on in every chat in the Project.

1. In the Project, find the knowledge panel (usually on the right).
2. Upload files such as PDFs, Word documents, text files or spreadsheets, or paste text directly.
3. Give files clear names, such as `brand-guide-2026.pdf` instead of `final-v3.pdf`.

What works well as knowledge:

- Brand and tone of voice guides.
- Product and price lists.
- Approved texts you want Claude to learn from.
- Background documents about the client or market.

What to leave out:

- Old versions of documents that contradict the current ones.
- Huge archives "just in case". More is not better if most of it is irrelevant.
- Passwords, API keys or anything you would not email to a colleague.

On paid plans, when a Project's knowledge gets large, Claude automatically switches to searching through it instead of reading everything at once. You do not need to do anything for this.

## Work inside the Project

Start every chat about this subject from inside the Project, not from the general chat screen. You can tell you are in a Project because its name shows above the chat. You can also move an existing chat into a Project later.

## Share a Project with your team

On Team and Enterprise plans you can invite colleagues to a Project. You choose per person whether they can only view and chat, or also edit the instructions and knowledge. Give edit rights to one or two owners per Project so the instructions stay consistent.

## Keep it tidy

- Review instructions and files every few months and remove what is outdated.
- Archive Projects for finished work. Archived Projects keep their content but no longer clutter your list.
- Delete a Project only when you are sure you no longer need its chats and files.

## Next steps

- [Brief Claude like a colleague](https://viralistic.nl/help/claude/write-better-prompts)
- [Connect Claude to your tools](https://viralistic.nl/help/claude/connectors)
- [Memory, privacy and your data](https://viralistic.nl/help/claude/memory-and-privacy)
- [What a skill is and when to make one](https://viralistic.nl/help/claude/what-is-a-skill)