Claude Wiki
From Claude Wiki, the free skill that gives your Claude Code a brain.
Claude Wiki is a persistent knowledge base skill for Claude Code that solves AI memory loss. Based on Andrej Karpathy's LLM Wiki methodology, it transforms Claude from a memoryless assistant into a persistent knowledge curator that learns, organizes, and evolves alongside your project. Install in 30 seconds with one command. Works on any project type — language and framework agnostic.
Claude Wiki is a skill for Claude Code that solves a problem every developer faces: your AI assistant forgets everything each session. Directly inspired by the LLM Wiki methodology published by Andrej Karpathy — former Director of AI at Tesla and one of the most respected names in artificial intelligence — this skill transforms Claude from a memoryless assistant into a persistent knowledge curator that learns, organizes, and evolves alongside your project. Instead of rediscovering context from scratch every time you open the terminal, Claude builds and maintains a cumulative knowledge base: ingesting sources, extracting entities and concepts, recording architectural decisions, and preserving lessons learned — all with cross-references, YAML frontmatter, and automatic mirroring to Obsidian via MCP. The idea is simple: if Wikipedia works as humanity's collective memory, why can't your project have one? The difference is that here, the one writing and maintaining the encyclopedia is Claude itself.
Claude Wiki
| Type | Claude Code Skill |
| Author | Giovani Junior - MCV |
| Inspired by | LLM Wiki by Andrej Karpathy |
| Requires | Claude Code |
| Optional | Obsidian + MCP |
| License | MIT |
| Tested | 100% pass rate |
| Community | Open Source |
| Repo | GitHub → |
== Origin ==
Claude Wiki was born from a simple realization: every time you start a new Claude Code session, your AI assistant starts from zero. No memory of what was discussed yesterday. No knowledge of decisions made last week. No awareness of lessons learned last month.
After reading Andrej Karpathy's article "LLM Wiki" — where the former Tesla AI Director proposed a pattern for building persistent knowledge bases with LLMs — the creator of this skill, Giovani Junior - MCV, saw an opportunity to turn that methodology into something any developer could use in 30 seconds.
Karpathy's core insight was elegant: instead of retrieving raw documents on every query (RAG), let the LLM build and maintain a structured wiki — markdown files with cross-references, entity pages, concept maps, and decision logs. The wiki becomes a compounding artifact that gets smarter over time.
The problem? Setting up this system manually for every project is tedious. You need to create directories, write rules, configure behaviors, maintain an index, keep a log — the kind of bookkeeping that kills knowledge bases before they start.
Claude Wiki automates all of it. One command. 30 seconds. Your project has a brain.
"The tedious bookkeeping — updating cross-references, keeping summaries current, noting contradictions — is what causes knowledge bases to fail. LLMs don't get bored."
== How It Works ==
Three-layer architecture showing how Claude Wiki organizes your project knowledge:
== Getting Started ==
=== New Projects ===
# 1. Install the skill
claude install-skill giovani-junior-dev/claude-wiki
# 2. Open your project
cd my-new-project
# 3. Activate the wiki
"Set up a wiki for this project"
# That's it. Claude will:
# ✓ Detect Obsidian MCP (install if needed)
# ✓ Create wiki/ and raw/ directories
# ✓ Initialize index.md and log.md
# ✓ Configure CLAUDE.md with all rules
# ✓ Mirror everything to Obsidian30 seconds. Your project has a brain.
=== Existing Projects ===
# 1. Install the skill (if you haven't)
claude install-skill giovani-junior-dev/claude-wiki
# 2. Open your existing project
cd my-saas-app
# 3. Activate the wiki
"Set up a wiki for this project"
# Claude will:
# ✓ Create wiki/ and raw/ alongside your existing code
# ✓ APPEND rules to CLAUDE.md (never overwrites existing rules)
# ✓ Mirror to Obsidian under YourProject/wiki/
#
# Your code, configs, and git history stay untouched.Pro tip: After setup, drop your existing docs into raw/docs/ and tell Claude: "ingest everything in raw/". In minutes, you'll have a structured knowledge base built from your own documentation.
Claude Wiki works with any project type: React, Python, Rust, Go, mobile, backend, SaaS, monorepo — language and framework agnostic.
Key Takeaways
| What it is | Persistent knowledge base skill for Claude Code |
| Installation | claude install-skill giovani-junior-dev/claude-wiki |
| Setup time | 30 seconds — one command |
| Based on | Andrej Karpathy's LLM Wiki methodology (2025) |
| Languages | All — language and framework agnostic |
| Obsidian | Optional — local-only mode works perfectly |
| Breaking changes | Zero — never overwrites existing code or CLAUDE.md |
| License | MIT — free and open source |
== Commands ==
| Command | What it does | Example |
|---|---|---|
wiki ingest <file> | Process a source from raw/ into structured wiki pages | "wiki ingest raw/articles/clean-arch.md" |
wiki ingest all | Ingest all new (unprocessed) sources in raw/ | "wiki ingest all" |
wiki query <question> | Search the wiki and synthesize an answer with citations | "wiki query how does our auth system work?" |
wiki status | Show stats: pages by type, pending sources, last operations | "wiki status" |
wiki lint | Health check: contradictions, orphan pages, missing links | "wiki lint" |
wiki decision <title> | Record an architectural decision with context and trade-offs | "wiki decision switch from REST to GraphQL" |
wiki learning <title> | Record a lesson learned from a bug fix or insight | "wiki learning race condition in payment queue" |
wiki search <term> | Search across wiki pages | "wiki search authentication" |
wiki sync | Force sync all local pages to Obsidian vault | "wiki sync" |
You don't need to memorize commands. Claude also responds to natural language.
Automatic Behaviors:
- Reads the wiki at the start of every session
- Asks to record decisions after architecture discussions
- Asks to record learnings after complex bug fixes
- Alerts you when new info contradicts the wiki
- Asks to ingest new files dropped in raw/
== Before & After ==
Without Claude Wiki
-
Every session starts from zero. Claude asks the same questions again.
-
Architectural decisions live in Slack threads, lost in chat history.
-
You fix the same bug twice because no one documented the root cause.
-
New team members spend weeks understanding the codebase.
-
Knowledge lives in people's heads. When they leave, knowledge leaves too.
-
Articles you read last month? Forgotten.
With Claude Wiki
-
Claude reads the wiki and already knows your project context, decisions, and lessons learned.
-
Every decision is recorded with context, options considered, and trade-offs.
-
Lessons learned are indexed. Claude warns: "We fixed a similar issue on March 12."
-
"wiki query how does the payment system work?"gets an instant, cited answer. -
Knowledge lives in markdown files — versioned, linked, searchable, permanent.
-
Ingested into the wiki with summaries, entities, and cross-references.
The difference isn't what Claude can do — it's what Claude remembers. Without a wiki, every session is a first date. With a wiki, it's a long-term partnership that compounds over time.
== Frequently Asked Questions ==
1. Do I need Obsidian installed?
2. Does it work offline?
wiki sync to push later.3. Will it mess with my existing code or CLAUDE.md?
wiki/ and raw/ folders, appends to CLAUDE.md. Never overwrites.4. What languages/frameworks does it support?
5. Does Claude actually read the wiki every session?
6. Can I edit wiki pages manually?
raw/ files are meant to be immutable sources.7. How is this different from Claude's built-in memory?
8. Is my data sent anywhere?
9. Who is Andrej Karpathy and what is the LLM Wiki?
Ready to give your project a brain?
One command. 30 seconds. Works on new and existing projects.
claude install-skill giovani-junior-dev/claude-wikiThen open any project and say: "Set up a wiki for this project"