Guides/Claude
Claude12 min readPremium

Turn Rough Notes Into a Reusable Claude Project

The biggest time sink when using AI is re-explaining context. Every new conversation, you're back to square one โ€” who you are, what your company does, what tone you prefer. Claude Projects eliminate all of that.

A Project is a persistent workspace where Claude retains context across every conversation. Set it up once, and every session starts with Claude already knowing everything it needs about your work.

What a good Project contains

Most people create a Project and leave the instructions blank, or paste a one-liner. A well-built Project has four components, each doing a specific job. The first is a role definition โ€” not "I work in marketing" but a precise description of your function and decision-making authority that shapes how Claude frames every response.

The second component โ€” the context brief โ€” is where most people leave the most value on the table. It's not a company description. It's a structured summary of the specific things Claude needs to know to be useful: your team's constraints, the current priorities, the stakeholders involved in the work, and the things that are true about your situation that Claude would have no way to know otherwise.

The third component is behavioral rules โ€” the standing instructions that prevent Claude from defaulting to generic, sanitized output. And the fourth is at least one uploaded reference document that Claude can access in any conversation within the Project.

Premium guide

Unlock the full guide

Every guide, the full prompt library, and the growing daily sprint archive. Cancel any time.

Get Premium โ€” $9.99/moโ† Back to all guides

For teams

Want us to build this for your whole team?

We run AI workshops and full implementations for teams of 5โ€“200. Custom prompts, workflows, and training built around your actual work.

See how we work โ†’