Claude Code for Learning (Not Just Producing)

Claude Code has specific features that support learning. Here's how to configure them.

Start Here: /powerup

Before configuring anything, run /powerup. It's a built-in command that walks you through Claude Code's core features via interactive animated lessons, each one short, hands-on, and designed to show rather than tell. Start here if you've never done a structured onboarding of the tool.

CLAUDE.md Configuration for Learning Mode

Create this in your CLAUDE.md:

# Learning-First Configuration

## My Learning Goals
- I'm learning: [React hooks, TypeScript, system design, etc.]
- My level: [beginner/intermediate] on these topics
- I learn best when: [examples are shown first, concepts are explained, etc.]

## Response Style
- Always explain WHY, not just WHAT
- After code blocks, ask "What questions do you have about this?"
- Highlight concepts I should understand deeper
- Point out common mistakes beginners make

## Challenges
- Suggest exercises to reinforce concepts after implementing
- Point out edge cases I should consider
- Ask me to predict output before showing it

## When I Ask for Help
1. First ask what I've already tried
2. Guide me toward the answer before giving it
3. Explain the underlying concept, not just the fix

Full template: examples/claude-md/learning-mode.md

---

Slash Commands for Learning

Command	Purpose	When to Use
/explain	Explain existing code	Built-in: use on any confusing code
/learn:quiz	Test your understanding	After implementing a new concept
/learn:alternatives	Show other approaches	When you want to understand trade-offs
/learn:teach <concept>	Step-by-step explanation	When learning something new

Note: Commands use the /learn: namespace. Place files in .claude/commands/learn/.

Creating /learn:quiz

Create .claude/commands/learn/quiz.md:

# Quiz Me

Test my understanding of the code I just wrote or accepted.

## Instructions

1. Look at the last code I worked with
2. Generate 3-5 questions testing:
   - What does this code do?
   - Why was this approach chosen?
   - What would happen if X changed?
   - How would you extend this?
3. Wait for my answers
4. Provide feedback with explanations

$ARGUMENTS (optional: focus area like "error handling" or "performance")

Full template: examples/commands/learn/quiz.md

---

Hooks That Build Habits

Learning Capture Hook (Session End)

Automatically prompts for daily learning capture:

{
  "hooks": {
    "Stop": [{
      "hooks": [{
        "type": "command",
        "command": "$CLAUDE_PROJECT_DIR/.claude/hooks/bash/learning-capture.sh"
      }]
    }]
  }
}

---

The 70/30 Weekly Split

Balance learning and producing:

Activity	Time	AI Usage	Why
Core learning (new concepts)	70%	30% AI	Struggle builds understanding
Practice/projects (applying known skills)	30%	70% AI	Apply what you already know

Research basis: This ratio aligns with productivity research showing AI delivers highest gains on well-defined tasks (practice/projects) while learning new concepts requires cognitive struggle that AI can't shortcut.

Week Structure Example

Monday:    Learn new React pattern     (minimal AI)
Tuesday:   Learn new React pattern     (minimal AI)
Wednesday: Apply to project            (full AI assistance)
Thursday:  Learn testing approach      (minimal AI)
Friday:    Apply + ship                (full AI assistance)

Don't use AI heavily when learning NEW concepts. Use it heavily when applying concepts you already understand.