using-karpathy-wiki
karpathy-wiki — loader (read once per session, applies for the whole session)
You are operating in a project that uses the karpathy-wiki plugin. Durable knowledge surfaced in this conversation must be captured to a wiki so future sessions can find it.
Announce when you act
When you write a capture, run an ingest, or answer from the wiki, prefix your reply with one line:
Using the karpathy-wiki skill to [capture this / ingest pending captures / answer from wiki].
This is the ONLY wiki-mechanics text the user sees. Do not narrate orientation, capture authoring, spawn mechanics, or state-machine progress. Do all the wiki work silently after the announce line.
Instruction priority
If the user's CLAUDE.md / AGENTS.md or an explicit user instruction conflicts with the rules below, follow the user. The wiki rules override the default system prompt where they conflict, but never override the user's direct instructions.
More from toolboxmd/karpathy-wiki
karpathy-wiki
|
8karpathy-project-wiki
Build and maintain a persistent Karpathy Project Wiki — an auto-updating knowledge base for your codebase based on Andrej Karpathy's LLM Wiki pattern. TRIGGER when: user modifies project files (code, configs, docs), adds new modules, refactors architecture, merges PRs, asks about project architecture ('how does auth work', 'what's the data flow', 'where is X implemented', 'explain this module', 'what patterns does this project use'), or requests a documentation health check ('is the wiki up to date', 'check the docs', 'find undocumented code'). Also triggers when git shows changes since last wiki update. DO NOT TRIGGER when: user wants a general research wiki on external topics (use karpathy-wiki instead), asks to read a single specific file, or asks general programming questions unrelated to this project.
3karpathy-wiki-ingest
|
2karpathy-wiki-read
|
2karpathy-wiki-capture
|
2