Use Max Effort for Architectural Decisions

Not every task deserves the same level of thinking. For a quick rename or a simple bug fix, Claude Code's default reasoning is fine. But when you're making structural decisions that will ripple through your entire codebase, you want Claude working at full capacity.

Claude Code supports different effort levels. For architectural work, pushing to the maximum level produces noticeably better output compared to the standard high setting.

# When asking Claude to design something significant, be explicit:
"Use maximum effort to design the authentication architecture for this app."

# Or lean on the ultrathink keyword:
"ultrathink: what's the best way to structure our data access layer?"

The tradeoff is real: max effort burns through tokens significantly faster than high effort. Use it strategically, not for every task.

Good candidates for max effort:

• Designing system architecture or data models
• Reviewing complex, interconnected code before a refactor
• Evaluating tradeoffs between different implementation approaches
• Debugging a gnarly issue with unclear root cause

For routine coding tasks, file edits, or anything straightforward, the standard effort level is faster and cheaper.

Think of max effort like calling in a senior architect rather than a capable developer. Right tool, right moment.

via @rayyzinoo