ClaudeProjectsLevel 2: Context

What Should Go in a Claude Project's Instructions?

Put in what you'd otherwise retype at the start of every chat: who you are, who the work is for, the tone, the format you want and the things to avoid. Project instructions apply to every chat in that project. Projects are available on all plans, and Free accounts can create up to five.

Prompt to copy
Paste this into Set project instructions, and edit the brackets:

I am [role] at [company], working on [what this project is].
The readers of this work are [audience]. They care about [what] and already know [what].

Always:
- Write in [tone], using [American/British] spelling.
- Format answers as [format], under [length] unless I ask for more.
- Base facts on the files in this project, and name the file you used.
- If the files don't answer something, say so rather than guessing.

Never:
- [specific thing, such as "mention competitors by name"]
- [specific thing]
Project instructions
  • Who you are
  • Who the work is for
  • Tone
  • Format you want
  • Things to avoid
A rule of thumb, not an Anthropic chart: anything you'd otherwise retype. Claude can't see the project's name or description.

Try it now

  1. 1Click **Projects in the left sidebar, then + New Project**. Give it a name you'll recognize, knowing Claude can't see it.
  2. 2Click Set project instructions, paste the text above, fill in the brackets, and click Save instructions.
  3. 3Start a chat in the project and ask for something you'd normally explain first, without any background.
  4. 4You'll know it worked if the answer already has the right audience and format. If a standing rule gets missed, rewrite it as one short, specific line.

Use it when

Use it for work you come back to: a client account, a course you teach, a newsletter or a product. If you've typed the same background into three chats this month, it belongs in a project.

Skip it when

Skip it for one-off questions, and for a preference you want everywhere. Those fit your account-wide memory and settings better than a project. Don't put task-specific details in the instructions either, since they'd apply to every future chat, so give those in the message.

Why it works

A project is a workspace with its own chat history and knowledge. Anthropic's help center says instructions and knowledge apply across all of a project's chats, while the chats themselves don't share context unless you add it to the knowledge base. So a decision you reach in one chat won't appear in the next unless you put it there. There's one trap at the start: the project's name and description aren't visible to Claude. Anything Claude needs has to go in the instructions or the knowledge.

Example

You write a monthly newsletter for independent pharmacists. The instructions say the readers are owners rather than chains, that they know clinical terms but not marketing ones, that each issue runs to 400 words, and that you never give dosing advice. Next month you open a chat and just say "Draft the lead on the new reimbursement rule", attaching the notice.

Going further

Each project also has its own memory. Project chats use that memory plus your account memory, but not memory from other projects. New memories are saved to the project, and if account memory is on, Claude may reference them outside it too. To keep a client's project fully separate, turn off Use account memory under Memory on the project page. To keep one chat out of memory, turn off Memory in the + menu before your first message.

Common mistakes

  • Writing the context in the project description. Anthropic's help center says Claude can't see the name or description.
  • Expecting a later chat to remember a decision from an earlier one. Add it to project knowledge, or put it in the instructions.
  • Writing a long essay of instructions, so the rules that matter are lost among the ones that don't.
  • Assuming a project isolates a client's details from everything else. Check the Use account memory setting.

Sources

Checked 6 November 2026. Products change often, so confirm details with the vendor.

Related

Beyond the course