dev-llm-wiki

Seed idea: Andrej Karpathy's "vibe-coding" gist — the original prompt for keeping an LLM-maintained wiki alongside your code.

A personal dev knowledge base for builders, maintained by an LLM (Claude Code, Cursor, etc.) and read by you. You drop sources into raw/, the LLM distills them into wiki/, and over time the wiki becomes a queryable second brain that informs every future task.

The contract for how the LLM operates lives in CLAUDE.md — loaded automatically on every Claude Code session opened in this directory. Unlike most such contracts, this one is enforced: .scripts/vault-check.py checks every structural rule in it, and a pre-commit hook runs it.

The loop this is built for: the wiki owns everything before and after execution, the tracker owns how and when, and hooks write back at PR time. Linear is the example — substitute yours. Source.

Just want to use it? Jump to Getting started — seven steps, about ten minutes. The sections before it explain why the structure is shaped this way, which is worth reading once but not before your first ingest.

• The invariant — the one rule everything else follows from
• Three zones — who writes what
• The project lifecycle — slots, the plan gate, promotion, the spine
• How the wiki works — the four operations, topics, domain hubs
• The gate — the twelve checks and the pre-commit hook

The invariant

Everything else in this template follows from one rule: