Claude projects: giving it a permanent brain

What it is good at

• Uploaded files stay available to every chat in the project without re-attaching them each time.
• Project instructions apply automatically, so you don't repeat 'write in our tone' at the start of every conversation.
• Handles a substantial amount of reference material at once, useful for a full brand guideline plus past copy examples together.
• Keeps separate clients or collections cleanly apart, avoiding tone or fact bleed between unrelated work.

Where it falls short

• There is a ceiling on total project knowledge size, so an enormous archive still needs curating down to what matters.
• It won't automatically know which uploaded file is most relevant to a specific question unless you point to it.
• Projects don't share knowledge with each other, so genuinely cross-project facts need repeating in each one.

How to use it for creative work

1. 01

   Create one project per client or collection

   Start a dedicated project the moment new ongoing work begins, rather than working in a single general chat that accumulates unrelated context.

2. 02

   Upload your reference material as files, not pasted text

   Add brand guidelines, past approved copy and briefs as actual files in the project's knowledge section so they persist across every future chat there.

3. 03

   Write project instructions once, precisely

   Set tone, audience and formatting rules in the project's custom instructions field so you never retype them at the top of a new chat.

4. 04

   Name the file you mean in ambiguous requests

   When a project holds several similar documents, specify which one a question should draw from to avoid it blending details from the wrong source.

5. 05

   Prune outdated files periodically

   Remove superseded briefs or old brand guidelines from the project knowledge so Claude isn't weighing an outdated version alongside the current one.

Ready-to-use prompts

Write instructions for this Claude project. Client: [name]. Purpose: [brief description]. Tone: [description]. Always reference: [key facts]. Never do: [list].

Summarise everything currently in this project's knowledge in a short list, organised by file, so I can check nothing outdated is still included.

Using only [file name], answer: [question]. Do not draw on any other file in this project's knowledge.

Compare [file A] and [file B] in this project's knowledge and flag any contradictions in tone, facts or figures.

I'm starting a new project for [client/collection]. Ask me the five most important questions you need answered before I upload files, so the project is set up properly from the start.

Questions people ask

What's the difference between a Claude project and a normal chat?

A project persists uploaded files and custom instructions across every chat inside it, while a normal standalone chat has no memory of files or instructions from any other conversation.

How much can I upload to a Claude project?

Projects hold a substantial amount of reference material, but there is a total knowledge limit, so very large archives should be curated to the most relevant documents rather than uploaded wholesale.

Do Claude projects share information with each other?

No, each project's knowledge and instructions are isolated, so facts you need available everywhere should be repeated in each relevant project rather than assumed to carry over.