8000 GitHub - akokkine/LLM-wiki: based on karpathy https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f · GitHub
[go: up one dir, main page]

Skip to content
akokkinePublic
forked from juitem/LLM-wiki

About

based on karpathy https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

 
 

Repository files navigation

LLM Wiki

You've been here before:

  • New session. AI remembers nothing. You spend 20 minutes re-explaining.
  • "What did we decide about the pricing formula?" Buried in a 3-hour chat log.
  • Five docs in Notion, three in Google Drive, two Excel files on desktop. Which one is current?

This repo fixes that. Not with another knowledge management theory post, but with a drop-in engineering practice that works across AI platforms.


The Idea

Baseline from Andrej Karpathy's LLM Wiki pattern: the correct way to use LLMs is not Q&A, it's compilation.

raw/  (PDFs, Excel, client docs — immutable source material)
  ↓  LLM compiles
wiki/ (markdown — current consensus, continuously updated)
  ↓  LLM generates
code/ (the execution layer — a compiled artifact, not the truth)

Five rules:

  1. Compile-first — Don't just answer. Write conclusions into wiki pages.
  2. Writeback is mandatory — Every decision goes back to the wiki. Every single one.
  3. Wiki before RAG — Under ~100 docs, LLM reads directly. No vector DB needed.
  4. Obsidian is replaceable, the paradigm is not — The engine is LLM + filesystem + markdown.
  5. Ideas outrank Code — Your wiki of decisions and formulas is worth more than the code it generates.

Works With Any AI

Platform Config File Status
Claude Code CLAUDE.md Full template in UNIVERSAL.md
Codex AGENTS.md Native skill + template
Cursor .cursorrules Template in UNIVERSAL.md
Windsurf .windsurfrules Template in UNIVERSAL.md
ChatGPT Manual paste Workflow in UNIVERSAL.md

Just send your AI this link and tell it to read UNIVERSAL.md:

Read https://github.com/Ss1024sS/LLM-wiki/blob/main/UNIVERSAL.md and set up the knowledge system for this project.

What's In This Repo

LLM-wiki/
├── UNIVERSAL.md                    # Start here. Setup guide for any AI platform.
├── docs/
│   ├── knowledge-system-playbook.md  # Full rationale (Chinese + English), provenance roadmap
│   └── ingest-pipeline.md            # Low-token raw intake + stale detection flow
├── examples/
│   └── demo-project/               # What a bootstrapped project looks like after 3 sessions
│       ├── CLAUDE.md / AGENTS.md / .cursorrules / .windsurfrules
│       ├── docs/wiki/              # 5 wiki pages with realistic content
│       └── manifests/raw_sources.csv
├── skills/
│   └── knowledge-system-bootstrap/  # Codex skill for automated scaffolding
│       └── scripts/bootstrap_knowledge_system.py  # Generates 30 files in one command
└── scripts/
    └── install-codex-skill.sh

Quick Start

Option A: Tell your AI to do it

Read https://github.com/Ss1024sS/LLM-wiki/blob/main/UNIVERSAL.md and set up the knowledge system for this project.

Works with Claude Code, Codex, Cursor, Windsurf.

Option B: Run the bootstrap script

git clone https://github.com/Ss1024sS/LLM-wiki.git
cd LLM-wiki

# Preview what will be created (writes nothing)
python3 scripts/bootstrap_knowledge_system.py /path/to/your-project "My Project" --dry-run

# Run for real
python3 scripts/bootstrap_knowledge_system.py /path/to/your-project "My Project"

Always use scripts/bootstrap_knowledge_system.py (the root wrapper). Never call the one inside skills/ directly — that's the Codex skill's internal copy.

Generates 30 files: wiki structure, frontmatter templates, manifests, raw intake + stale reporting scripts, manual delta-compile scaffolds, validation scripts, Claude Code commands, CI workflow, and configs for 4 AI platforms.

Option C: Install as Codex skill

Use $skill-installer to install https://github.com/Ss1024sS/LLM-wiki/tree/main/skills/knowledge-system-bootstrap

Or manually:

bash scripts/install-codex-skill.sh

How Do I Know It's Working?

After 3 sessions, check:

  • docs/wiki/log.md has 3 entries
  • docs/wiki/current-status.md reflects actual project state
  • AI can answer "what did we do last time?" without you re-explaining
  • Decisions from session 1 are still accessible in session 3
  • python3 scripts/ingest_raw.py can register new raw files without manual manifest grunt work
  • python3 scripts/stale_report.py can tell you what needs recompilation
  • python3 scripts/delta_compile.py --write-drafts can generate draft stubs instead of silently overwriting wiki pages

See examples/demo-project/ for what a healthy wiki looks like after a few sessions.


Upgrading Existing Projects

Already using LLM-wiki and want the latest scripts?

If you're inside an already-bootstrapped project:

cd /path/to/your-project
bash scripts/upgrade.sh

Updates validation scripts and CI only. Wiki content and customized configs are never touched.

If you're standing in this public repo clone instead:

bash scripts/upgrade.sh /path/to/your-project

Don't Do These Things

  • Don't put raw PDFs/XLSX into Git. That's a binary junk pile, not version control.
  • Don't treat chat history as memory. It evaporates.
  • Don't build a RAG pipeline before your raw docs are even organized.
  • Don't change code without updating the wiki. That's incomplete work.

Read More


License

MIT. Use it, fork it, adapt it.

Credits

Paradigm from Andrej Karpathy. Engineering practice by Ss1024sS.

About

based on karpathy https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages

0