Strategic Model Selection

Master Claude Code's model selection to optimize performance, cost, and usage limits while maximizing development effectiveness through strategic model switching.

Model Selection Philosophy

Right Model for the Right Task: Each Claude model has unique strengths. Strategic selection maximizes output quality while managing usage limits and costs effectively.

Plan with Power, Code with Efficiency: Use high-capability models for complex planning and reasoning, then switch to efficient models for implementation and iteration.

Available Models & Strategic Use Cases

🎯 Default (Recommended)

Model: Opus 4.1 up to 50% usage limits, then Sonnet 4
Best For: Balanced approach with automatic optimization
Usage Pattern: General development with built-in limit management

🚀 Opus

Model: Opus 4.1 for complex tasks, reaches limits faster
Best For: Complex architecture, critical debugging, advanced problem solving
Usage Pattern: Reserve for challenging tasks requiring maximum reasoning capability

⚡ Sonnet

Model: Sonnet 4 for daily use
Best For: Coding, refactoring, testing, routine development tasks
Usage Pattern: Primary workhorse for implementation and iteration

🎨 Opus Plan Mode ⭐ Recommended Strategy

Model: Opus 4.1 for planning, Sonnet 4 for execution
Best For: Complex projects requiring detailed planning with efficient implementation
Usage Pattern: Strategic thinking with cost-effective execution

Editing Mode Control

Shift+Tab Mode Switching

Claude Code provides powerful mode switching via Shift+Tab:

Shift+Tab → Cycles through editing modes:
1. Default Mode    (Balanced model selection)
2. Opus Mode       (Maximum reasoning power)
3. Sonnet Mode     (Efficient coding focus)  
4. Opus Plan Mode  (Strategic planning + efficient execution)

Pro Tip: Keep pressing Shift+Tab until you see "Opus Plan Mode" for optimal workflow balance.

Strategic Model Usage Patterns

Pattern 1: Complex Project Lifecycle

flowchart LR
    subgraph "Planning Phase"
        A["🎨 OPUS Plan Mode<br/>@prd.md<br/>@ask.md architecture"]
    end
    
    subgraph "Development Phase"
        B["⚡ Auto-Switch to Sonnet<br/>@code.md<br/>@debug.md<br/>@refactor.md"]
    end
    
    subgraph "Review Phase"
        C["🎨 OPUS Plan Mode<br/>@review.md<br/>Complex analysis"]
    end
    
    subgraph "Optimization Phase"
        D["⚡ Sonnet<br/>@optimize.md<br/>@test.md"]
    end
    
    A --> B
    B --> C
    C --> D
    D --> B
    
    classDef opus fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef sonnet fill:#e8f5e8,stroke:#388e3c,stroke-width:2px
    
    class A,C opus
    class B,D sonnet

Pattern 2: Problem-Solving Escalation

flowchart TD
    START["⚡ Start with Sonnet<br/>Standard coding task"]
    ISSUE{"Encounter<br/>Complexity?"}
    SWITCH["🎨 Switch to Opus Plan Mode<br/>Plan solution approach"]
    IMPLEMENT["⚡ Auto-switch to Sonnet<br/>Implement planned solution"]
    STUCK{"Still<br/>Stuck?"}
    OPUS["🚀 Full Opus Mode<br/>Maximum reasoning power"]
    SUCCESS["✅ Solution Complete"]
    
    START --> ISSUE
    ISSUE -->|Simple| SUCCESS
    ISSUE -->|Complex| SWITCH
    SWITCH --> IMPLEMENT
    IMPLEMENT --> STUCK
    STUCK -->|Working| SUCCESS
    STUCK -->|Critical Issue| OPUS
    OPUS --> SUCCESS
    
    classDef sonnet fill:#e8f5e8,stroke:#388e3c,stroke-width:2px
    classDef opus fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef decision fill:#fff3e0,stroke:#f57c00,stroke-width:2px
    
    class START,IMPLEMENT sonnet
    class SWITCH,OPUS opus
    class ISSUE,STUCK decision

Model-Specific Command Optimization

🎨 Opus Plan Mode - Strategic Commands

Ideal Commands:

@prd.md - Complex product requirements with market analysis
@ask.md - Architectural consultation requiring deep reasoning
@state_tracker.md create - Project phase planning
@review.md - Comprehensive code quality analysis

Workflow:

# Switch to Opus Plan Mode
Shift+Tab (until you see "Opus Plan Mode")

# Strategic planning with Opus reasoning
@prd.md "Advanced Analytics Platform"
@ask.md "What's the best microservices architecture for high-volume data processing?"

# Implementation automatically uses Sonnet
@state_tracker.md create
@state_tracker.md start 1  # Auto-invokes @code.md in Sonnet

⚡ Sonnet Mode - Implementation Commands

Ideal Commands:

@code.md - Feature implementation and development
@debug.md - Issue resolution and troubleshooting
@refactor.md - Code structure improvements
@test.md - Testing strategy and implementation
@optimize.md - Performance improvements

Workflow:

# Switch to Sonnet for efficient coding
Shift+Tab (select "Sonnet")

# High-velocity development
@code.md "User authentication system"
@debug.md "Login validation errors"
@refactor.md "Authentication middleware structure"
@test.md "Authentication flow testing"

🚀 Full Opus Mode - Critical Tasks

When to Use:

Complex architectural decisions with multiple trade-offs
Critical debugging requiring deep system understanding
Advanced algorithm implementation
Integration of complex third-party systems
Security-critical implementations

Workflow:

# Switch to full Opus for maximum capability
Shift+Tab (select "Opus")

# Critical problem solving
@ask.md "How to implement zero-downtime deployment with database migrations?"
@debug.md "Intermittent race condition in distributed system"
@code.md "Implement custom encryption algorithm with specific requirements"