llm-wiki

Topics in the source

• LLM Wiki — Second Brain for Claude Code + Obsidian
• Core principle
• When to use
• Architecture (three layers)
• Three core operations
• Quick start
• Slash commands (this plugin ships)
• Sub-agents (this plugin ships)

Inspired by Andrej Karpathy's LLM Wiki pattern (gist). This skill turns Claude Code (or any agent CLI) into a disciplined wiki maintainer that incrementally builds and maintains a persistent, interlinked Obsidian vault as you feed it sources. The knowledge compounds — cross-references, contradictions, and synthesis are already there when you query. Most LLM+docs workflows are RAG: retrieve fragments at query time, synthesize from scratch, forget. The wiki is compounding: sources are read once, integrated into a persistent markdown knowledge base, and kept current. You curate and ask; the LLM reads, files, cross-references, and maintains. Obsidian is the IDE. The LLM is the programmer. The wiki is the codebase. Personal: track goals, health, psychology, journaling, self-improvement Research: deep dives over weeks on a topic — papers, articles, reports, evolving thesis Book companion: file chapters as you read; build a fan-wiki-style companion for characters, themes, plot threads Business/team: internal wiki fed by Slack, meeting notes, calls — LLM does maintenance nobody else wants to do Competitive analysis, due diligence, trip planning, course notes, hobby deep-dives Do NOT use wh

This is an excerpt. Refer to the complete source and its current requirements.