02-core-rtk-token-proxy-prefix-for-all-commandslisted

# RTK — Token-Proxy Prefix for All Commands (CORE) **What it is:** RTK is a local terminal proxy that wraps a command, runs it for real, and returns a *compressed / summarized* view of stdout+stderr instead of the raw firehose. It saves enormous token volume on noisy commands (installs, builds, test runners, `ls`, `git log`). The difference in context cost is night-and-day — that's why it's mandatory. 1. **Prefix every command with `rtk`**: Begin every terminal command with `rtk` (e.g. `rtk bun install`, `rtk git status`, `rtk docker build .`). No exceptions by default. 2. **HOW IT WORKS**: `rtk <cmd>` executes `<cmd>` unchanged, captures its output, and emits a token-minimized rendering. Exit codes pass through. It is a *view* layer — it does not change what the command does. 3. **DROP RTK ONLY IF IT HIDES OUTPUT YOU GENUINELY NEED**: Re-run the SAME command without the `rtk` prefix when you suspect the compression dropped something load-bearing — then re-add `rtk` for the next command. Dropping is per-command, never global. 4. **SIGNALS RTK MAY BE HIDING SOMETHING** (drop it and re-run raw): exact error text / stack trace / line numbers matter and were summarized away; you need byte-exact output (hashes, tokens, diffs, base64, a full table); column/whitespace alignment matters; a value got truncated with `…`; the summary contradicts the exit code; you're parsing the output programmatically; or two runs you're comparing must be diffed verbatim. 4a. **DROP RTK WHEN IT HANGS