token-efficiencylisted

# Token Efficiency Reduce output token waste and prevent iteration cycles that consume context. ## Trigger Use when: - Sessions feel expensive or slow - Output is verbose with filler text - Claude is re-reading files or iterating unnecessarily - Setting up a new project for token-efficient work ## Anti-Sycophancy Rules These patterns waste 30-60% of output tokens: | Pattern | Example | Fix | |---------|---------|-----| | Sycophantic opener | "Sure! Great question!" | Delete. Lead with answer. | | Prompt restatement | "You're asking about X..." | Delete. Answer directly. | | Closing fluff | "Let me know if you need anything!" | Delete. Stop after the answer. | | Unsolicited suggestions | "You might also want to..." | Delete unless asked. | | AI disclaimers | "As an AI model..." | Delete entirely. | | Verbose preambles | "I'll help you with that..." | Delete. Start with the action. | ## Tool-Call Budgets Set explicit budgets by task complexity: | Task Type | Tool-Call Budget | Wrap-Up At | |-----------|-----------------|------------| | Quick fix / lookup | 20 calls | 15 | | Bug fix | 30 calls | 25 | | Feature (small) | 50 calls | 40 | | Feature (large) | 80 calls | 65 | | Refactor | 50 calls | 40 | | Exploration / research | 30 calls | 25 | At the wrap-up threshold: commit progress, assess remaining work, decide whether to continue or start fresh. ## One-Pass Coding Discipline For simple-to-medium tasks: 1. **Read all relevant files** including tests first 2. **Und