Section 5: Projects as Your Workspace

A conversation with Claude is a session. A Project is a workspace. The distinction matters more than it sounds: sessions end, workspaces persist. This section is about structuring ongoing work in Claude so that the context, documents, and instructions you’ve carefully assembled don’t have to be rebuilt from scratch every time you return.

Why this section matters

The single biggest efficiency loss for regular Claude users is re-establishing context. Every new conversation starts cold. You re-explain your company, your project, your preferences, and the background you’ve already covered. For one-off tasks, that’s acceptable. For ongoing work, it’s a significant and unnecessary tax.

Projects solve this. They’re persistent containers where you store documents, instructions, and reference material that Claude can access across many conversations. You set it up once, and the context is there every time.

What you’ll learn

What Claude Projects are. A Project is a named workspace where you can store files, instructions, and reference context that persists across sessions. Claude treats everything in a Project as available background for any conversation started within it.

Projects as context folders. The core concept: a Project is not a task or a deliverable. It’s the context container for a category of work. Research projects, client engagements, content creation, personal planning, each can have its own Project with its own relevant materials.

Adding documents, PDFs, and reference material. Uploading files to a Project makes them permanently available without re-uploading each session. A client brief, a style guide, a set of company policies, reference materials that Claude needs for a broad category of tasks can live in the Project.

Writing Project instructions. Instructions are the standing directions Claude follows for every conversation in a Project. Your preferences, constraints, tone guidelines, and any context that would otherwise have to be repeated can be written once and applied automatically.

Projects vs. Artifacts: persistent inputs vs. things you produce. Projects hold inputs (documents, instructions, context). Artifacts are outputs (things Claude produces that you can save and use). Understanding this distinction prevents confusion about what goes where.

Using Projects for research, content, and collaboration. The practical applications: a research project with source documents, a content project with a style guide and brief templates, a client project with background documents and relationship notes.

The mini project

You’ll build a functional Project for a real category of ongoing work: a client engagement, a research topic, a content type you produce regularly. The deliverable is a configured Project with uploaded reference material, written instructions, and at least one conversation demonstrating that the context carries forward correctly.

How to approach this section

Projects are best understood by using them rather than reading about them. Set one up for something real. The concepts become clear once you see how much simpler a Claude interaction becomes when the context is already there.

By the end of this section, the idea of starting every Claude conversation from zero should feel unnecessarily inefficient.