Lesson 2.2: Claude Projects — Stop Repeating Yourself

Learning objectives

• –Explain what a Claude Project is and what problem it solves
• –Identify at least three common ways people organize Projects
• –Build a working custom-instructions template for a Project
• –Set up one real Project for a recurring area of work or life

Real-world example

Work Project Setup

Analogy

A Project is a bit like giving a new team member a proper onboarding document instead of re-briefing them from scratch every single morning. Once the background is written down once, every future conversation can pick up from a shared starting point instead of starting cold.

Best practices

• –Set up a small number of purpose-built Projects rather than one single catch-all space
• –Keep custom instructions specific enough to be genuinely useful, not so generic they add no real value
• –Revisit and update Project instructions periodically as your role or preferences change
• –Use a Project’s knowledge base for reference material you’ll return to often, not one-off documents
• –Start a new conversation inside the relevant Project rather than a general chat whenever the task fits that Project’s focus

Common mistakes

• –Creating one single Project for everything, which dilutes its usefulness for any specific area
• –Writing custom instructions so vague they don’t actually change how responses come back
• –Setting up a Project once and never updating it as circumstances change
• –Forgetting to actually start conversations inside the Project, defaulting back to a general chat out of habit
• –Overloading a Project’s knowledge base with outdated or irrelevant files

Important note

Projects work best for genuinely recurring context — not for one-off tasks. If something is a single, self-contained request, a regular conversation is usually simpler than setting up a new Project for it.

Lesson summary

A Claude Project is a persistent space with custom instructions and an optional knowledge base that eliminates the need to re-explain background information in every new conversation. Organizing Projects around a small number of recurring areas — personal life, main job, a specific initiative — and keeping their instructions current is what makes them genuinely useful over time, rather than a one-time setup that quickly goes stale.

Hands-on exercise

Objective

Set up one real, working Project for a recurring area of your own work or life.

Instructions

1. Choose one recurring area where you find yourself repeating the same background information across conversations.
2. Fill in the starter template: role, focus, audience, tone, things to keep in mind, things to avoid.
3. Set up a Project using that filled-in template as its custom instructions.
4. Start a new conversation inside that Project and ask for something relevant to test whether the context carries through correctly.
5. Note anything about the response that reflected the custom instructions without you having to restate them.

Expected outcome

One functioning Project with genuinely useful custom instructions, plus direct confirmation that a new conversation inside it correctly used that background without repetition.

Reflection Question: What’s a second recurring area of your work or life where a dedicated Project would likely save you real repeated setup time?

Key takeaways

• –A Project is a persistent space with custom instructions and an optional knowledge base
• –Its main purpose is eliminating repeated context-setting across conversations
• –Organizing a small number of purpose-built Projects works better than one catch-all space
• –A simple fill-in-the-blank template — role, focus, audience, tone, do’s and don’ts — is enough to get real value
• –Projects need occasional updates to stay useful as your role or preferences change