Chapter 06 · WEB
Projects: knowledge and instructions
A Project groups conversations around ongoing work with project instructions and knowledge. It does not automatically know every document in your organization. Supply relevant material and check what Claude cites from it.
Video
Steps
- Create a Project with a clear name and outcome, such as "Internal course planning." Add instructions covering audience, output format and allowed sources.
- Add clean, current documents to Project knowledge. Specify which document wins if versions conflict. Old material can produce an old answer even with a new model.
- Start a conversation inside the Project and ask a question answered by a document. Request the source, then compare the citation with the original.
- Large knowledge collections may use retrieval rather than placing every word in every message. Sharing and collaboration depend on the plan. Review access before adding another person.
Common pitfall: A Project conversation does not prove every file was read in full or is current. Source checks still matter.
Hands-on exercise: Create a Project with one sample document and one instruction. Ask a question inside and outside the Project and compare the result.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
What gives a Project reusable context?
Recap
- Group work, instructions and knowledge
- Keep sources current and resolve conflicts
- Check plan-specific sharing and retrieval