Back to articles
Slash 90% of Tokens Per Session With This Pre-Compiled Wiki (Karpathy Inspired Workflow)

Slash 90% of Tokens Per Session With This Pre-Compiled Wiki (Karpathy Inspired Workflow)

via Dev.tohouseofmvps

Last June, Karpathy posted something that got 2.3 million views. He said context engineering matters more than prompt engineering specifically, "the delicate art and science of filling the context window with just the right information for the next step." Then last week he posted about building structured markdown knowledge bases that LLMs can reason over. Also went viral. Both ideas point at the same problem: your AI is only as good as the context you give it. And right now, most of us are giving it terrible context. the problem nobody's measuring Every time you start a Claude Code session, it spends the first chunk of time just figuring out your project. Reading files. Grepping for routes. Opening package.json. Exploring the import graph. Finding your schema. Checking your env vars. I started measuring how many tokens this costs. On a real 92-file monorepo (Hono + Drizzle, 4 workspaces): ~66,000 tokens. Every session. Not cached between sessions. On a 53-file project: ~46,000 tokens.

Continue reading on Dev.to

Opens in a new tab

Read Full Article
2 views

Related Articles