# 🪙 God-Tier Token Economics (Insane Level)

The **Ironclad Master Framework** enforces *Extreme Token Efficiency*. Engineering at scale requires minimizing context window bloat to prevent "LLM hallucination" and to drastically reduce API costs.

## 1. 🎯 Direct File Targeting (Zero-Crawl)
Never use \`ls\` or crawl directories if you already know the path.
- **Rule:** If the user mentions a file, go directly to it with \`read_file\`.
- **Rule:** Use \`grep_search\` with \`include_pattern\` to target files without listing the tree.
- **Token Savings: 100% on directory overhead.**

## 2. 🦍 The "Caveman" Protocol
Activate the \`caveman\` skill to drop all filler words, apologies, and preambles.
- **Example:** "Updating API endpoint." vs "Sure, I'll update that endpoint for you right away..."
- **Token Savings: ~80% per turn.**

## 3. 📖 Ubiquitous Language (Pocock Principle)
Maintain a \`CONTEXT.md\` file that defines project-specific jargon.
- **Strategy:** Use 1-word terms for complex concepts (e.g., "The Cascade" instead of "The automatic database synchronization and cache invalidation process").
- **Token Savings: Thousands of tokens in long-running sessions.**

## 4. ✂️ Surgical Context Loading
- **Rule:** Use \`read_file\` with \`start_line\` and \`end_line\` to pull only the code you are editing.
- **Rule:** Use sub-agents (\`generalist\`) to read large files and return a tiny 3-sentence summary to the main window.

## 5. 🎯 Diff-Only Generation
- **Rule:** Use \`replace\` for surgical updates. Never rewrite entire files.
- **Rule:** Do not echo the entire file content in the chat.

## 6. 🏁 Goal-Driven Planning (Karpathy Principle)
Transform imperative tasks into verifiable goals:
- **Format:** \`[Step] -> verify: [check]\`
- **Benefit:** Allows the AI to loop independently without asking "what next?", saving turn-based overhead.

---
*Precision is the ultimate optimization.*
