Short answer: keep project instructions short and specific, put background facts in project knowledge rather than in the instructions, and remember that a Project only knows what's inside it. Every other Project, Claude Code session and teammate starts from zero.
How to set up a Project
Go to https://claude.ai/projects and click + New Project. Open it, click Set project instructions, write them, and click Save instructions [1]. Add files with the + next to project knowledge on the right [1]. Projects are on every plan; free accounts get up to five [1].
Two details that trip people up:
- Claude doesn't see the project's name or description [1]. Put anything it needs in the instructions.
- Chats in a Project don't share context with each other unless the information is in project knowledge [1].
Instructions vs. knowledge
Anthropic's own one-line split: Projects say "here's what you need to know," Skills say "here's how to do things" [3]. Inside a Project:
- Instructions tell Claude how to behave in every chat in the Project [1]. Keep them to a few lines: who it's working for, the tone, the format, the two or three rules that matter.
- Knowledge is the reference material: price lists, past proposals, your style guide. On paid plans, large knowledge switches to retrieval, so only the relevant parts load [1].
Anthropic's usage advice points the same way: shorter instructions and fewer unused files make your limits last longer [2].
Instructions that get followed
- Specific beats emphatic. "Write in US English, under 150 words, no bullet lists" works. "ALWAYS be concise" doesn't.
- One rule per line. Long paragraphs bury the rule you care about.
- Fix with a line, not a lecture. When Claude gets something wrong twice, add one line about it.
- Date your facts. A price in project knowledge with no date is a price Claude will quote after it changed.
Where Projects stop helping
A Project is a silo. Its instructions and files don't reach your other Projects, Claude Code or Cowork, and on individual plans they don't reach a colleague. Run three Projects and you keep three copies of your company, and they drift apart.
The fix is to keep your company facts in one folder that every Project and tool reads, and keep each Project's instructions to what's specific to it.
Do it yourself, or have it done
Chet sets up that folder (we call it Start) from your own documents, grades your Claude setup, and fixes what breaks. $99 a month, cancel anytime.
Maximize Claude with Chet: https://www.coworkers.global/get-chet?utm_source=blog&utm_medium=internal&utm_campaign=chet&utm_content=claude-project-instructions-that-work-cta
FAQ
What's the difference between project instructions and custom instructions? Project instructions apply only to chats inside that Project [1]. Your account-wide preferences apply everywhere.
Is there a limit on project knowledge? On paid plans, Claude switches to retrieval as knowledge nears the context limit, which Anthropic says expands capacity up to 10x [1][3].
Can my team share a Project? On Team and Enterprise plans, yes, with view or edit permissions [1].
Sources
- Claude Help Center, create and manage projects: https://support.claude.com/en/articles/9519177-how-can-i-create-and-manage-projects
- Claude Help Center, how usage and length limits work: https://support.claude.com/en/articles/11647753-how-do-usage-and-length-limits-work
- Claude, Skills explained: https://claude.com/resources/articles/skills-explained
Regards,
Charles Stack
Founder, Coworkers.Global
Coworkers.Global is not affiliated with Anthropic. Claude is a trademark of Anthropic, PBC.