Learning to Code with AI
The guide for developers who want to use AI to accelerate their learning — without becoming dependent on it.
The hard truth: AI can make you 3x more productive or unemployable in 3 years. Which path you take depends entirely on how you use it.
Choose Your Path
Learning tracks adapted to your experience level and role. Pick yours before diving in.
Junior Developer
Foundation path for newcomers
- Read the Cheat Sheet
- Create your first CLAUDE.md
- Practice with simple tasks
- Learn diff review workflow
- Explore slash commands
- Take the beginner quiz
Senior Developer
Intermediate efficiency boost
- Skim Quick Start
- Set up custom hooks
- Configure MCP servers
- Create project-specific agents
- Master Plan Mode
- Build automation workflows
Power User
Full mastery path
- Read the full Ultimate Guide
- Build custom skills
- Create multi-agent systems
- Implement security hooks
- Design team workflows
- Contribute templates back
- Pass all quiz levels
Product Manager
Overview for non-technical roles
- Read Architecture overview
- Understand capabilities
- Review privacy guide
- Learn team integration
- Explore use cases
DevOps / SRE
Infrastructure and reliability focus
- Setup Claude for infrastructure
- Master the FIRE debugging framework
- Practice K8s troubleshooting
- Automate incident response
Product Designer
Design-to-code workflow with Figma MCP
- Learn image analysis basics
- Explore wireframing tools
- Setup Figma MCP
- Master design-to-code workflow ⭐
- Print cheat sheet
Quick Self-Check
Answer each question honestly. Your score appears after answering all 5.
The Three Developer Patterns
Which one are you? Be honest.
Dependent
Signs: Copy-paste without understanding, can't debug AI code, anxiety without AI
→ Read "Breaking Dependency" sectionAvoidant
Signs: Refuses AI "on principle", slower than peers, missing out on productivity gains
→ Read "Embracing AI Tools" sectionAugmented
Signs: Uses AI critically, understands everything, can work with or without AI
→ Read "Optimizing Your Flow" sectionConfigure Learning Mode
Claude Code can be configured to support your learning, alongside producing code.
CLAUDE.md Configuration
Add this to your project's CLAUDE.md to make Claude ask questions before generating code:
## Learning Mode
Before generating code, ask me:
1. What approaches have I considered?
2. What am I stuck on specifically?
3. What do I expect the solution to look like?
If I skip these, remind me to think first.
Slash Commands for Learning
/explain | Explain existing code (built-in) |
/learn:quiz | Test your understanding after implementing |
/learn:teach | Step-by-step explanation of a topic |
/learn:alternatives | Show other approaches & trade-offs |
The 70/30 Rule
Balance producing and learning each week:
- 70% Production: Use AI freely, focus on output
- 30% Learning: No AI, or AI as teacher only
The UVAL Protocol
Your framework for learning with AI without losing skills.
Understand First (15-min Rule)
Before asking AI: State the problem in ONE sentence. List 3 possible approaches. Identify what you DON'T know. Then ask AI with context.
Before generating code, ask me:
1. What approaches have I considered?
2. What specifically am I stuck on?
Verify (Explain It Back)
If you can't explain the code to a colleague, you don't really understand it.
Claude asks YOU to explain what the code does
Apply (Transform, Don't Copy)
Never copy-paste raw. Modify at least one element (variable name, structure, or edge case) to force genuine understanding.
Required: Adapt to your context
Learn (Capture the Insight)
End each session by capturing one thing you learned. A single insight, not a full journal.
"What's ONE thing you learned today?"
→ Logs to ~/claude-learnings.md
30-Day Progression Plan
Week-by-week guide to mastering AI-assisted development.
| Week | Focus | AI Ratio | Exercise |
|---|---|---|---|
| Week 1 | Foundations | 20% AI | Build feature WITHOUT AI, then compare |
| Week 2 | Understanding | 40% AI | Use AI, but explain every line |
| Week 3 | Critical Use | 60% AI | Challenge AI suggestions, find bugs |
| Week 4 | Augmented | 70% AI | Full productivity with verification |
Ready-to-Use Templates
Configure Claude Code to support both learning and producing.
Learning Mode CLAUDE.md
Configuration that makes Claude explain the reasoning before generating the code. Includes challenge mode and interview prep.
/learn: Commands
Quiz, teach, and explore alternatives. Namespaced commands for learning workflows.
Learning Capture Hook
Session-end hook that prompts for ONE learning insight. Builds a learning journal with zero friction.
Choose Your Methodology
AI amplifies both good and bad code, so structuring your workflow matters.
TDD
Critical business logic
Red-Green-Refactor with AI. Write the test first, let Claude implement the minimum code to pass. Catches regressions before they ship.
Test-DrivenSDD
Architecture upfront
Design before code. Spec the interfaces, validate with Plan Mode, then generate implementation. Best for complex systems.
Spec-DrivenBDD
PM/dev collaboration
User stories become tests. Given/When/Then scenarios that both PMs and developers understand. Bridge the communication gap.
Behavior-DrivenGSD
Throwaway prototypes
Ship fast and verify later, for situations where speed beats perfection. Refactor or delete once you've validated the concept.
Get-Stuff-DoneStart With Interactive Onboarding
Claude asks 2-4 questions about your profile, then guides you through personalized content
claude "Fetch and follow the onboarding instructions from: https://raw.githubusercontent.com/FlorianBruniaux/claude-code-ultimate-guide/main/tools/onboarding-prompt.md" Choose your language
English or French
Select your goal
Learn, audit setup, or explore
Pick your level
Junior, Senior, or Power User
Get personalized path
Curated content for you
Ready to Learn the Right Way?
The full guide includes: Red flags checklist, breaking dependency strategies, case studies, and more.