Excessive Token Usage with Claude Code (Anthropic Pro) #1492
Description
Hi team, thanks for the excellent work on this framework — it has been very useful when combined with Claude Code.
When using the framework with Claude Code on an Anthropic Pro account, usage limits are typically reached in under an hour of active work. This is noticeably faster than what many users report for typical Pro usage patterns, even with relatively heavy coding sessions.
This suggests that the generated spec-related artifacts may be larger or more verbose than necessary, driving up token usage for both generation and downstream interactions. In particular, long, highly redundant, or repeatedly regenerated specs can quickly consume a significant portion of the Pro allocation.
It might be helpful to explore strategies to reduce the overall token footprint of these artifacts, for example:
- Making spec and auxiliary artifacts more concise by removing redundancy and boilerplate.
- Introducing a “compact” or “minimal” mode that aggressively shortens descriptions, metadata, and comments.
- Caching or reusing previously generated spec fragments instead of regenerating them from scratch on each run, where feasible.
Optimizing for token efficiency would let users stay within their Claude Pro limits longer while still benefiting from the framework’s capabilities, especially during extended coding sessions.
Happy to share concrete usage examples or logs if that would help with debugging or design discussions.