Claude Project Knowledge Base: What to Add
RedHub AI Editorialupdated August 18, 20263 min read
Jump to a section7
TL;DR
- What it is: the files and reference text you add to a Claude Project for it to draw on.
- Who it's for: anyone whose Project gives generic or wrong answers — see how to use Claude Projects.
- How it works: add the few documents that carry real, reusable truth — and leave out the noise.
- Bottom line: a tight knowledge base beats a big one. Twenty files make Claude draw on the wrong one.
What should go in a Claude Project knowledge base?
A Claude Project knowledge base should hold the few documents that carry reusable truth for the work — the brand voice guide, the product facts, the policies, the templates you actually reuse. It should not hold everything you have on the topic. A bloated knowledge base is the most common reason a Project gives wrong answers: with twenty overlapping files, Claude can draw on the outdated or irrelevant one. Fewer, current, authoritative documents beat a full drive every time.
Best for: making a Project accurate. The Blueprint Library maps what to add for each function.
The knowledge base is where good Projects go wrong. People treat it like storage — upload everything and hope Claude sorts it out. But Claude draws on what you give it, so noise in means noise out. Here's what belongs in a knowledge base, what doesn't, and why less is more.
What to add: the reusable truth
Add documents that are authoritative, current, and reused across many chats. For most Projects that's a short list:
- Source-of-truth references. Product facts, pricing, policies — the things Claude must get right and never invent.
- Voice and style guides. How your writing should sound, so output matches without re-explaining.
- Templates and examples. A few strong examples of the output you want — Claude patterns off them.
- Process rules. The steps or checks a task must follow, if they're stable enough to reuse.
What to leave out: the noise
Leave out anything one-off, outdated, or duplicative. Old versions of a doc, a thread that was relevant to one chat, five overlapping brand files from different years — these don't help Claude, they confuse it. The failure mode is subtle: with two versions of a policy in the knowledge base, Claude might cite the wrong one, and you won't notice until it matters.
The tight-base rule: if you're not sure a document earns its place, leave it out. You can always add it when a real gap shows up. A knowledge base of three authoritative files beats one of twenty mixed ones.
Keep it current, or it lies for you
A knowledge base is a promise that its contents are true. The moment a policy changes or a price updates, the old file in the knowledge base becomes a source of confident wrong answers. Treat the knowledge base like a living reference: when the real thing changes, update the file. An out-of-date knowledge base is worse than none, because Claude will cite it with full confidence.
The knowledge base is one of three parts of a working Project, alongside instructions and how you prompt. The Blueprint Library gives each of its ten Projects a knowledge-base map — what to add for that function — so you're not guessing what belongs.
Know exactly what to add
Ten Projects, each with a knowledge-base map of what belongs — so your base is tight and accurate from day one.
Get the Blueprint Library — $79 →See how the knowledge base works with instructions and prompts in the full Claude Projects guide.
Decision Guide
Trim your knowledge base if: the Project gives generic, outdated, or occasionally wrong answers.
Add a file if: a real gap shows up in the output — not preemptively "just in case."
Best first step: remove every outdated or duplicate file, and confirm only current, authoritative ones remain.
Common Questions
What should I put in a Claude Project knowledge base?
The few authoritative, current, reusable documents the work needs — source-of-truth facts, voice guides, templates, and stable process rules. Not everything you have.
Why is my Claude Project giving wrong answers?
Often a bloated or outdated knowledge base. With overlapping or old files, Claude can draw on the wrong one. Trim to current, authoritative documents.
How many files should a knowledge base have?
As few as carry the reusable truth. Three tight, current files beat twenty mixed ones — more files raise the odds Claude uses the wrong one.
Should I upload everything just in case?
No. "Just in case" files are noise that can produce wrong answers. Add a document only when a real gap shows up in the output.
Do I need to update the knowledge base?
Yes. When a policy or price changes, update the file — an outdated knowledge base makes Claude cite wrong information confidently.
Knowledge base or instructions — where does context go?
Reference material (facts, guides, templates) goes in the knowledge base; how-to-behave rules go in instructions. Point instructions at the knowledge base rather than duplicating it.