Module 2Lesson 5 of 15·4:23

Making Changes with Planning and Thinking Modes

Learn how to use screenshots, planning mode, and thinking modes in Claude Code to implement complex changes across your codebase with precision and confidence.

Making changes to a codebase is where Claude Code truly shines. Whether you need a quick UI tweak or a complex multi-file refactor, Claude Code provides powerful features — screenshots for visual communication, planning mode for broad changes, and thinking modes for deep reasoning — that help you implement changes with precision.

Visual Communication with Screenshots

One of the most effective ways to communicate with Claude Code is through screenshots. When you want to modify a specific part of your UI, a screenshot eliminates ambiguity — Claude sees exactly what you are referring to.

Pasting screenshots

Use Ctrl+V (not Cmd+V on macOS) to paste screenshots into the Claude Code chat interface. This keyboard shortcut is specifically designed for image input.

Planning Mode for Multi-Step Changes

For complex tasks that require understanding many parts of your codebase, enable Planning Mode. This makes Claude Code perform thorough research across your project before implementing any changes.

Activate Planning Mode by pressing Shift+Tab twice (or once if you are already auto-accepting edits). In planning mode, Claude Code will:

  • Read more files across your project to build comprehensive understanding
  • Create a detailed implementation plan before writing any code
  • Show you the plan and wait for your approval to proceed
  • Give you the opportunity to redirect before any changes are made

Thinking Modes for Deep Reasoning

Claude Code offers progressively deeper reasoning modes that allocate more tokens for the model to think through complex problems before responding:

  • "Think" — basic extended reasoning for moderately complex problems
  • "Think more" — deeper analysis for tricky logic
  • "Think a lot" — comprehensive reasoning for architectural decisions
  • "Think longer" — extended time for very complex analysis
  • "Ultrathink" — maximum reasoning capability for the hardest problems

When to Use Planning vs. Thinking

Planning Mode vs. Thinking Mode

Planning Mode (breadth)

  • •Tasks requiring broad understanding of your codebase
  • •Multi-step implementations that touch many files
  • •Changes where you want to review the approach before execution

Thinking Mode (depth)

  • •Complex algorithmic or logic problems
  • •Debugging difficult, elusive issues
  • •Architectural decisions requiring careful trade-off analysis

Combine both for maximum effect

You can use planning mode and thinking modes together for tasks that require both breadth and depth. Ask Claude Code to "ultrathink" while in planning mode for the most thorough analysis possible. Note that both features consume additional tokens.

Key Takeaways

  • 01Paste screenshots with Ctrl+V to communicate UI changes precisely.
  • 02Enable Planning Mode (Shift+Tab twice) for multi-file changes that need research first.
  • 03Use thinking modes ("think", "ultrathink", etc.) for complex logic and debugging.
  • 04Planning handles breadth; thinking handles depth. Combine them for the toughest tasks.