Why Claude Projects + Markdown is the document-knowledge unlock
Two facts compound. First, Claude's 200K context comfortably fits 30-60 typical company documents (10-20 pages each) when those documents are clean Markdown. Second, Sonnet 4.6 and Opus 4.7 are unusually good at quoting source material verbatim with attribution — "according to section 4.2 of the Refund Policy, refunds within 30 days require…" — provided the source is structured enough for the model to navigate.
Convert each Word document to Markdown via Word to Markdown, drop the .md files into a Claude Project. Every conversation in that Project starts with the entire library available. Ask "what do our policies say about X" and Claude cross-references all loaded documents with proper attribution.
Patterns that work
One Project per domain: HR Policies, Engineering Specs, Sales Playbook, Customer Contracts, Compliance SOPs. Convert each Word file once, drop into the relevant Project, name files descriptively (the filename becomes part of Claude's attribution). New version of a document? Re-convert, replace the .md in the Project — Claude picks up the new content on the next conversation.
Combine with PDF for Claude, URL for Claude, Audio for Claude, and Video for Claude for a complete cross-modal knowledge base. Every source format reaches the Project as the same kind of structured Markdown.