Put Your Source of Truth in Project Knowledge
What it is
A Projects habit: load the stable reference material a body of work depends on — style guide, product facts, key docs, decisions — into the project's knowledge once, so every chat in that project starts already knowing it, instead of you re-pasting the same context each time.
Why it works
Without project knowledge, each new chat is amnesiac: you re-explain your product, re-paste the style guide, re-establish the constraints, and small inconsistencies creep in between chats. Putting the source of truth in the project makes it ambient — every conversation inherits the same facts, answers stay consistent across chats, and your prompts get shorter because the standing context is already there. It's the difference between briefing a new contractor every day and having a teammate who already knows the account.
When to use it
Any ongoing work with stable shared context — a client account, a product, a book, a codebase's conventions — where you'll have many chats that all need the same background.
When not to use it
One-off tasks, or fast-changing context that would go stale in the project and quietly mislead later chats. Keep project knowledge to what's genuinely stable.
Prompt
(In a Project) I've added <the reference docs> to this project's knowledge. From now on, use them as the source of truth for <product/brand/domain>. If a request conflicts with them, follow the docs and flag the conflict. For this chat: <task>.Example
A project holds your brand voice guide and product one-pager; every chat — a launch email, an FAQ, a sales reply — comes out on-brand and factually consistent without you pasting the guide again, and updating the doc once updates every future chat.
Advanced version
Keep the project knowledge curated, not accumulated: prune superseded docs and mark what's authoritative, because stale reference material is worse than none — it makes Claude confidently consistent with the wrong facts.
Common mistakes
- Re-pasting the same context every chat instead of loading it into the project once.
- Letting project knowledge go stale, so chats stay 'consistent' with outdated facts.
- Dumping everything in without marking what's authoritative, diluting the signal.