Learn how to create a Claude Project, add reusable knowledge and instructions, and use a document-checking workflow to verify important answers.
Create a Claude Project
Anthropic says Projects are available to all Claude users, and free accounts can create up to five. In the current Projects experience, open Projects, select + New Project, and provide a name and description.
Claude does not receive that name or description as context. Use them to organize the workspace, then place anything Claude should consider in project knowledge or project instructions.
Before following the remaining steps, identify which Projects experience you have. Anthropic is gradually moving some Pro and Max users to a new beta version. In that beta, a project is one conversation supported by parallel threads, shared files, instructions, memory, and a Library. Projects that have not moved remain on the current version described below.

Add files to project knowledge
On the current project page, find the knowledge base on the right and select its + button. Anthropic’s project-management instructions say you can upload relevant documents, text files, or code snippets. Claude processes content added there and uses it as context in chats within that project.
Choose the location according to how long the material should remain available. Content uploaded during an individual conversation stays separate from project knowledge, while files placed in the project area can be used across the project’s chats. Context from one chat is not shared with another unless the relevant information is added to the knowledge base.
As a practical suggestion, add only material relevant to the project’s recurring work. Use conversation attachments for temporary examples that do not need to become reusable project context.

Set reusable project instructions
Select Set project instructions, enter directions for Claude’s behavior and responses, and save them. According to the Claude Help Center, those instructions apply to every chat in the project.
Anthropic’s training material identifies tone, expertise level, response style, intended outcomes, and additional context as possible subjects for these instructions. For a document-focused project, I suggest specifying the intended audience and preferred format, then asking Claude to distinguish information drawn from project files from its analysis. This is an editorial recommendation for making answers easier to review, not a guarantee about the resulting response.
Keep enduring reference material in project knowledge and recurring response preferences in project instructions. The project name and description should not substitute for either because Claude cannot access those details as context.
Use a verification workflow for important answers
Start a chat inside the Claude Project and state the task in plain language. If the answer should rely only on your uploaded material, Claude Academy advises turning off web search. I suggest also naming the relevant file and asking Claude to identify the supporting section or passage for each important point. That request can make manual review more structured, but its success should be assessed from the response itself.
Then compare every consequential statement with the original material. Check figures, dates, names, qualifications, exceptions, and conclusions directly against the files. If a statement cannot be matched confidently, ask Claude to revise it or mark it as an interpretation, and repeat the comparison.
Treat this comparison as the verification step. Project knowledge supplies context across chats, while project instructions guide response behavior; neither official description replaces checking the underlying document when accuracy matters.
Conclusion
For a dependable starting workflow, I recommend creating one Claude Project, adding one authoritative document to project knowledge, and saving short instructions that define the audience, format, and treatment of source material. Turn off web search when the answer should come only from your documents, then compare the response’s important claims with the original file before using them.
If your interface is the redesigned beta, use its shared Library, files, and instructions for the same organizational purpose, but follow the controls shown in that version. Anthropic says the beta is being introduced in stages, so the available layout can depend on whether a project has already been moved.
Sources
- Getting started with Claude · Claude Academy
- How can I create and manage projects? | Claude Help Center
- What are projects? | Claude Help Center
- Projects redesigned: from folder to conversation
- Introduction to projects · Claude 101 · Claude Academy
Disclosure
This article was prepared with AI assistance.
Improve this guide
Report a problem or suggest the next question
Submissions enter a private editorial queue. They are reviewed and deduplicated before any public update or new page is created.
