daBongo LMS AI Training Courses

← Back to Course

Your Persistent AI Brain – Memory, Context, and Continuity (Claude Edition)

Lesson 3: Projects – Organized, Long-Term Persistent Context

Lesson Objectives

By the end of this lesson, students should be able to:

  • Explain what a Claude Project is and how it differs from a regular conversation
  • Create a Project with uploaded reference files and standing instructions
  • Identify when to use a Project versus a regular conversation
  • Organize multiple Projects effectively for ongoing work

Lesson Content

Projects are persistent workspaces.

A regular Claude conversation is ephemeral – it exists for that session, and its context does not automatically carry into new conversations. A Project is different: it is a named, persistent workspace where conversations share uploaded reference files and standing instructions that are always active.

When you open a Project and start a new conversation, Claude already has access to everything in that Project – the files you uploaded, the instructions you wrote for it – without any re-establishment. This context persists indefinitely until you change it.

What a Project contains.

  • Project instructions: Standing instructions specific to this Project, separate from your account-level Custom Instructions. Example: "All work in this Project is for the Acme Corp account. Always use formal tone. The primary contact is Sarah Johnson, VP of Marketing."
  • Uploaded files: Documents, PDFs, reference materials, brand guides, style sheets, product descriptions, or any other files relevant to this work area. Claude can reference these in any conversation in the Project.
  • Conversation history: All conversations you have had within the Project are saved and accessible in the Project's conversation list.

When to use a Project vs a regular conversation.

Use a Project when:

  • You have reference material you would otherwise upload repeatedly (style guides, product documentation, brand guidelines, past deliverables, research files)
  • You are doing ongoing work that benefits from accumulated history
  • The work has a specific context, client, or focus that is distinct from your other work
  • You want to keep related conversations organized in one place

Use a regular conversation when:

  • The task is one-time and self-contained
  • You do not have persistent reference material for it
  • It does not relate to an ongoing work area

Practical Project organization.

Think of Projects as the equivalent of project folders on your desktop – each one is a distinct work area with its own reference materials and ongoing history.

Useful Project types:

  • One per active client or account
  • One per major ongoing project or initiative
  • One for personal use (personal goals, learning, non-work research)
  • One for frequently-used reference materials that apply across work (style guide, personal brand voice, templates)

Keep Projects current: when a project ends or a client relationship concludes, archive or close the Project rather than leaving stale Projects cluttering your workspace.

Project instructions vs Custom Instructions.

Custom Instructions apply to everything – they are who you are and how you work. Project instructions are scoped to that specific Project – they are what this specific work area requires. Both are active simultaneously when you work in a Project. Custom Instructions provide the general layer; Project instructions provide the specific layer.

Practical Example

A content strategist has four active clients.

Before Projects, she re-uploaded each client's brand guide, style sheet, and current campaign brief at the start of every relevant Claude session – eight to twelve minutes of setup before she could start working.

After setting up one Project per client, each with the relevant files uploaded and a standing instruction describing the client, their voice, and the current campaign focus: she opens a Project and starts working immediately.

The files are there.

The context is there.

The setup time dropped from eight minutes to zero.

She also created a "Master Templates" Project where she keeps her most-used document templates and writing frameworks – a single place to reference these across all client work.

Lesser-Known Tip

Write your Project instructions in the same structured format as your Custom Instructions: ABOUT THIS PROJECT, TONE AND VOICE, KEY CONTACTS OR CONTEXT, ALWAYS/NEVER rules. The structured format makes them easier to update when the project evolves – and projects always evolve. A Project instruction set that was accurate in January may need updates by April.

Safety Notes

Files you upload to Claude Projects are stored in your Claude account on Anthropic's servers. Do not upload documents containing: passwords or credentials, unredacted personal health information, full financial account details, or confidential materials your organization has not approved for cloud storage. For organizational use, check your company's data governance policies before uploading internal business documents to Claude Projects.

Practice Task

Create one Project now for an area of your current work. Give it a clear name. Write at least two sentences of Project instructions. Upload at least one relevant reference file (a document you would otherwise re-upload repeatedly). Start a conversation in the Project and confirm Claude references the uploaded file context in its response.

Completion Check

You should be able to explain the difference between a Project and a regular conversation, create a Project with instructions and uploaded files, identify which areas of your work would benefit from dedicated Projects, and describe the difference between Custom Instructions (account-level) and Project instructions (project-level).

Log in and enroll to access lesson quizzes.

← Back to Course

Scroll to Top