Making Changes
Screenshot Integration
Claude Code supports visual input through screenshot pasting. When you need Claude to understand a specific UI element, layout issue, or visual bug, you can paste a screenshot directly into the conversation. Claude will analyze the image and use it as context for its response.
macOS Shortcut
On macOS, use Control-V (not Command-V) to paste screenshots into Claude Code. This is a common gotcha -- Command-V pastes text, while Control-V pastes images.
The typical workflow: take a screenshot of the problematic area, paste it with Control-V, describe what you want changed, and Claude will locate the relevant code and implement the fix based on both the visual and textual context.
Plan Mode vs Thinking Mode
Claude Code offers two performance-boosting modes that allocate additional computational resources for complex tasks. Understanding when to use each -- and when to combine them -- is key to getting the best results.
| Plan Mode | Thinking Mode | |
|---|---|---|
| Activation | Shift + Tab (twice) | Say 'think hard' or 'ultra think' |
| Strength | Breadth -- wide codebase exploration | Depth -- complex logic and reasoning |
| Best For | Multi-step tasks, large refactors, cross-file changes | Tricky bugs, algorithm design, architecture decisions |
| Behavior | Reads more files, creates detailed implementation plan before acting | Extended reasoning budget, deeper analysis of the problem |
| Cost | More tokens (reads many files) | More tokens (longer reasoning chain) |
| Combine? | Yes -- use both for maximum thoroughness | Yes -- use both for maximum thoroughness |
Choosing between Plan Mode and Thinking Mode
Plan Mode handles breadth, Thinking Mode handles depth
Combining Modes
For the most complex tasks -- like redesigning an authentication system or migrating a database schema -- use both modes together. Plan Mode ensures Claude reads all relevant files, while Thinking Mode ensures it reasons deeply about the implications of each change.
Git Integration
Claude Code has built-in git awareness. It can stage files, write descriptive commit messages, and manage your version control workflow. This is especially powerful when combined with Plan Mode, which naturally creates logical commit points.
# Ask Claude to commit your changes
> Commit these changes with a descriptive message
# Claude will:
# 1. Run git status to see what changed
# 2. Run git diff to understand the changes
# 3. Stage relevant files (not .env or secrets)
# 4. Write a commit message that explains WHY, not just WHAT
# 5. Create the commitThe Full Workflow
Screenshot the problem area, paste with Control-V, describe the desired change, optionally enable Plan Mode (for breadth) or Thinking Mode (for depth), review Claude's implementation, then ask Claude to commit. This is the core development loop with Claude Code.
Key Takeaways
- ✓Use Control-V (not Command-V) on macOS to paste screenshots into Claude Code for visual context
- ✓Plan Mode (Shift+Tab twice) handles breadth: reads more files, creates implementation plans before acting
- ✓Thinking Mode ('think hard' / 'ultra think') handles depth: extended reasoning for complex logic
- ✓Combine both modes for maximum thoroughness on complex tasks like migrations or architecture changes
- ✓Claude Code's git integration handles staging, commit messages, and version control as part of the development loop
Check Your Understanding
Test what you learned in this lesson.
Q1.On macOS, which keyboard shortcut pastes screenshots into Claude Code?
Q2.You need to refactor an authentication system that spans 15 files across your codebase. Which mode should you enable?
Q3.What is Plan Mode's primary advantage over standard mode?