LLM-Wiki
GitHub
Claude Code · Project template

LLM-Wiki

Drop in call notes, emails and docs. Claude compiles them into a structured, interlinked wiki you can ask anything, with sourced answers.

LLM-Wiki is a personal knowledge base that an LLM maintains for you. Your source material stays untouched in raw/. Claude owns the compiled layer in wiki/: projects, people, decisions, concepts and a timeline, all cross-linked and kept current.

Start here

Set up your wiki

Open an empty folder in Claude Code (or Claude on the web) and paste this in. Claude pulls in the template and gets it ready for your first files.

Set up LLM-Wiki in this folder. Clone https://github.com/johnbr0phy/llm-wiki, copy its CLAUDE.md, skills/, raw/ and wiki/ folders here, then delete the clone. Read CLAUDE.md and tell me where to drop my first files.

The template ships with a small sample company so you can try a query straight away. Ask Claude to clear it out when you're ready to add your own.

Prefer to run it in a terminal?
git clone --depth 1 https://github.com/johnbr0phy/llm-wiki.git my-wiki && cd my-wiki && claude

Clones the template into my-wiki/ and opens Claude Code there.

How it works

Three operations. That's the whole loop.

1

Ingest

Drop a transcript, email or doc into raw/ and say "compile the wiki". Only new files get processed.

2

Query

Ask a question. Claude reads the index, finds the right articles and answers with sources.

3

Lint

Run a health check now and then. It finds contradictions, stale content and broken links.

What's in the box

llm-wiki/
├── CLAUDE.md      routing, rules, conventions
├── skills/
│   ├── compile-wiki/
│   └── lint-wiki/
├── raw/           your sources, never edited
│   ├── calls/
│   ├── email/
│   └── docs/
├── wiki/          compiled by Claude
│   ├── projects/
│   ├── people/
│   ├── decisions/
│   ├── concepts/
│   └── timeline/
└── voice/         optional: talk to it
  • ▹Two layers, one truth. raw/ is ground truth. wiki/ is what you read and query.
  • ▹Five article types. Projects, people, decisions, concepts and quarterly timelines, all cross-linked.
  • ▹Incremental. A manifest tracks what's been compiled, so each run only reads what's new.
  • ▹Sourced answers. Every claim traces back to the raw file it came from.
  • ▹Voice mode. Press a hotkey, ask out loud, and hear the wiki answer back.

Using it

Name files YYYY-MM-DD_Description_Type.md, drop them in raw/, then just talk to Claude:

You: "Compile the wiki."

You: "What's the current state of Project X?"

You: "What has Sarah been involved in this quarter?"

You: "What's on my plate this week?"

The more you feed it, the more useful it gets. Each source folder has a short guide to automating ingest for email, Slack and call transcripts.

Talk to your wiki

An optional realtime voice interface. Press a global hotkey, ask a question out loud and hear the answer, grounded in wiki/ through the same index, TLDR, article read path Claude uses.

See voice setup