Guide basis: Anthropic's Projects, project management, RAG, personalization, usage-limit and consumer-data pages were checked on 25 August 2026. This is a documentation-led operating design; we did not create a Project or measure retrieval quality.

A useful Claude Project is not a folder where every client file accumulates. It is a small knowledge system with an owner, a source policy and a refresh rule. Build those before writing a permanent instruction.

Design the project architecture

Use four layers:

  1. Project charter: the client, permitted jobs, prohibited data and final reviewer.
  2. Stable references: brand rules, approved terminology and durable product facts.
  3. Changing facts: prices, staff, dates, offers and policies with visible “checked on” dates.
  4. Task packet: the brief for one deliverable, including output format and source priority.

Keep the changing layer separate. When a price changes, you should replace one dated file rather than hunt through old chats and instructions.

Claude Project refresh cycle

  1. Select sources
    Action
    Add only authorised files that have an owner, date and reason for inclusion.
    Output
    A compact knowledge set with traceable origins.
    Stop when
    Stop if the client has not approved the data category or account.
  2. Write instructions
    Action
    Define audience, allowed claims, preferred sources, forbidden assumptions and review format.
    Output
    A short instruction block that can be tested independently.
  3. Run a validation task
    Action
    Ask questions whose answers are known, including one fact that is absent and should be refused.
    Output
    A retrieval and boundary check, not a production deliverable.
  4. Refresh deliberately
    Action
    Replace stale files, note the date and rerun the known-answer questions.
    Output
    A dated project state and a record of what changed.

Choose sources by authority, not convenience

Put client-approved primary material first. A polished old proposal is not authoritative if the current product sheet contradicts it. Keep examples for tone separate from facts, and label them accordingly. Remove duplicated files because two versions of the same policy create an avoidable retrieval conflict.

Anthropic documents retrieval-augmented generation for Projects when knowledge approaches or exceeds the normal context capacity. That can change how material is selected for a response; it does not make every uploaded sentence current or correct. Your validation set should include facts spread across several files and one deliberate contradiction.

Write instructions that survive handoff

State what the Project may do, not just the desired tone. For example: use the dated pricing sheet for numbers; quote no client testimonials unless the brief links the approval; label missing evidence; return a source list with the draft. Then name the human who resolves conflicts.

Avoid burying temporary campaign details in permanent instructions. Put a campaign deadline in the task packet so it can expire without changing the Project's stable rules.

Validate before client production

Create five known-answer questions and two “not in sources” questions. Check whether the response selects the latest file, identifies a missing answer and follows the output structure. After each source refresh, repeat the same set. A different response is not automatically wrong, but an unexplained source change needs review.

Monitor account usage separately. Anthropic says limits can depend on plan, message length, files and feature use. A Project architecture should not promise a fixed workload from a headline limit.

Close or transfer the Project

At handoff, provide the charter, source register, current instructions, validation questions and a deletion or transfer decision. Chat history is not sufficient documentation. If the client will own the process, agree on the destination account before adding confidential files.

Use the client-data approval worksheet for non-public material. The unresolved evidence is retrieval behaviour in a real account: no files were uploaded, no RAG threshold was observed and no collaborator handoff was tested.