Turn a folder of documents into a Claude knowledge base

These documents are [describe what they are, for example "every contract, invoice and supplier agreement for my business since 2024"]. I am [describe your role and what you use them for, for example "the owner, and I mostly need to find specific clauses, dates and amounts quickly"].

When I ask you something, answer only from these documents. Always name the exact file you took the answer from, and quote the relevant line or paragraph so I can verify it myself. If the answer sits across several documents, list each one separately rather than blending them into one summary.

If the documents do not contain the answer, say so plainly and tell me what kind of document would be needed to answer it. Never fill a gap with a general guess about how things usually work, because a plausible wrong answer is worse to me than no answer. Keep replies short and factual by default, and only go long when I ask you to explain something.

Search everything in this project's knowledge and answer this: [your real question, for example "which of these contracts auto-renew, and what is the notice period on each"].

For every part of the answer, name the file it came from and quote the exact sentence. Then tell me which documents you checked and found nothing relevant in, so I know the search actually covered the whole set and not just the first thing it matched.

Finish with anything that looks contradictory between documents, or any place where two files say different things about the same fact. Flag those separately at the bottom under a heading called "conflicts to check".

Using every document in this project's knowledge, build me a single self-contained interactive HTML page as an artifact. It should be a browsable index of everything in here, so I can find the right document without opening files one by one.

Give it a search box at the top that filters live as I type, matching on title, summary text and tags, with no page reload. Under that, put filter buttons for the categories you think fit this material, and show a count of how many items are currently visible. Then render one card per document containing the file name, a two or three sentence plain-English summary of what is actually in it, the key dates, names or numbers it contains, and three to five tags. Clicking a card should expand it to show a longer summary and the most important quoted lines from that document.

Read every document properly before you write the summaries, do not guess from the file names, and do not invent any detail that is not in the source. Sort the cards newest first where the documents have dates. Make it work on a phone as well as a laptop, keep the styling clean and readable with plenty of white space, and put everything in one file with no external dependencies so it still works if I save it and open it offline.

Improve the search so it still finds the right card when I half-remember something. Make it case-insensitive, match partial words anywhere in the text rather than only from the start, and search the long summaries and quoted lines as well as the titles and tags.

If a search returns nothing, show a friendly empty state that lists the five closest matches instead of a blank screen. Keep everything else on the page exactly as it is.

Add a second view to the page, toggled by a button next to the search box, called "timeline". It should lay every document out in date order with the most recent at the top, each one showing its date, file name and one-line summary.

Where two documents cover the same subject at different dates, group them together and note in plain language what changed between them. Use only what is actually in the documents, and if a document has no date, put it in a clearly labelled "undated" group at the bottom.

Add a collapsible panel at the bottom of the page called "gaps and open questions". In it, list the things a reasonable person would expect this collection to contain but which are missing, and any place where two documents contradict each other.

For each item, say which documents led you to that conclusion. Be specific and conservative: only raise something if the documents genuinely support it, and do not pad the list to make it look thorough.

I have just added new documents to this project. Compare them against what was already in the knowledge and tell me what has changed.

List anything that supersedes an older document, anything that contradicts something already in here, and any new dates, amounts or obligations I should know about. Name the specific files on both sides of each comparison.

Then tell me which older files are now safe to delete because a newer version covers them, and which ones I should keep even though they look redundant, with a one-line reason for each.