The Complete /powerup Guide — Master Every Lesson in Claude Code
[01]What Is /powerup?
Launched in Claude Code v2.1.90 on April 1st, 2026, /powerup is Claude Code's official gamified tutorial system — an interactive lesson framework built directly into your terminal. Unlike a static README, /powerup walks you through real Claude Code features with animated demonstrations, progress tracking, and an unlock-based progression system.
The timing is significant. /powerup launched the same week Claude Code removed the Buddy companion system in v2.1.97. Rather than abandoning gamification entirely, Anthropic shifted from passive companionship (Buddy) to active skill-building (/powerup). Two different bets on what developers actually want.
To start, just run the command in any Claude Code session:
/powerup[02]How /powerup Works
The /powerup system is structured as a series of interactive lessons that progress through Claude Code's core features. Each lesson:
- Presents a real-world coding scenario
- Walks you through the recommended Claude Code approach with animated guidance
- Unlocks the next lesson upon completion
- Does not save progress between sessions (this is a known limitation — see our Buddy Checker for a persistent companion alternative)
The lesson content adapts based on your interaction. Experienced Claude Code users often find the later lessons more useful — the early ones cover basics you may already know.
Key difference from Buddy: While your Buddy companion was passive (it existed whether you engaged with it or not), /powerup is entirely opt-in. You have to run the command and work through the lessons deliberately.
[03]Core Lessons Overview
The /powerup curriculum is organized into three tiers of increasing complexity:
Tier 1 — Foundations
- First Contact: Opening a Claude Code session, basic prompt structure, the CLAUDE.md file
- Context Craft: How to give Claude the right context — project structure, file references, active goals
- Edit Loops: The Read → Edit → Verify loop, accepting and rejecting changes, iterating with Claude
Tier 2 — Power Moves
- Multi-File Mastery: Working across multiple files simultaneously, cross-file refactors
- Shell & Test Integration: Running commands through Claude, integrating test suites, build verification
- Tool Use Deep Dive: Understanding which Claude tools (Read, Write, Edit, Bash, Grep, Glob) to use when
Tier 3 — Advanced Flows
- Autonomous Tasks: Setting up longer-running Claude sessions with checkpoints
- Custom Instructions: CLAUDE.md patterns for project-specific behavior, persona configuration
- Agent Coordination: Sub-agent spawning, parallel task execution, delegation patterns
[04]Tips for Getting the Most Out of /powerup
After working through the curriculum, here's what actually matters:
1. Don't Skip the Early Lessons
Even if you're an experienced user, the Foundations tier often surfaces assumptions you didn't know you had. The "Context Craft" lesson in particular changes how most developers write prompts.
2. Track Your Progress Externally
Since /powerup doesn't persist progress between sessions, keep a simple checklist. Our Buddy Checker home has a companion tool planned for exactly this purpose.
3. Apply Lessons Immediately
The lessons that stick are the ones you apply within the same session. After completing "Multi-File Mastery," immediately try the technique on a real codebase task.
4. Revisit Advanced Lessons
The Tier 3 lessons have more depth on second pass. "Agent Coordination" especially makes more sense once you've hit the pain points it's designed to solve.
5. Compare Notes with the Community
The story of /powerup vs /buddy has sparked interesting community discussions about what gamification in developer tools should actually look like. These conversations often surface non-obvious ways to use /powerup.
[05]The Bigger Picture: /powerup in Claude Code's Gamification Story
/powerup represents Anthropic's answer to a fundamental question: what should gamification in developer tools actually do?
The Buddy system's removal showed that Anthropic is willing to cut features that don't serve a clear purpose. /powerup survives because it has a clear purpose: making developers more effective faster.
But the community's reaction to Buddy's removal — the petitions, the MCP restoration tools, the 136 stars in 48 hours — shows that emotional engagement has real value too. /powerup teaches skills. Buddy provided companionship. These aren't the same thing, and there's a case that developers need both.
Browse the complete Buddy species guide while you wait for your next /powerup session, and check your eternal Buddy — it's still there, algorithm-preserved, regardless of what Claude Code version you're running.