ab579b966b
Document the core insight that working entirely on Opus is impractical due to rate limits, and that strategic model tiering (Opus for planning/review, Sonnet for implementation/testing) produces equivalent results with dramatically lower rate limit consumption. Key points: - 90% of tokens go to mechanical tasks suitable for Sonnet - Opus reserved for strategic decisions and pattern detection - Batching amplifies efficiency through context amortization - 3-5x more stories completed per rate limit window Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| _archive | ||
| explanation | ||
| how-to | ||
| reference | ||
| tutorials | ||
| 404.md | ||
| _README_WORKFLOW_DIAGRAMS.md | ||
| _STYLE_GUIDE.md | ||
| batch-processing-architecture.md | ||
| downloads.md | ||
| index.md | ||