The 55K tokens before the first real work landed is the number that surprised me most. A one line prompt should feel light, yet the system prompt, tool definitions, and instruction files are already a fixed cost. The source map example makes it concrete too. One reasonable read adding 20,573 tokens shows why the deny rule for build folders is worth setting up first, not after a session gets heavy.
Thanks for reading. That fixed cost surprised us too: it's there before you type a word, and nothing tells you unless you run /context. The build-folder read is the kind of thing Flightpath's coach looks for. When Claude reads from build output or dependencies, it suggests a deny rule you can copy into your settings, so the next session skips them.
OneLifeVibe
The 55K tokens before the first real work landed is the number that surprised me most. A one line prompt should feel light, yet the system prompt, tool definitions, and instruction files are already a fixed cost. The source map example makes it concrete too. One reasonable read adding 20,573 tokens shows why the deny rule for build folders is worth setting up first, not after a session gets heavy.