You star a course on GitHub. You read the first three lessons. Then life happens, and you never go back. We’ve all been there.

Here’s the thing — you don’t need to read 136 lessons. You need Claude Code to read them for you, then teach you the right lesson at the right moment while you’re actually coding.

Why This Works Better Than Reading

Claude Code is already smart. It knows programming, it knows patterns, it knows best practices. But its knowledge is generic. Ask it “what’s the best way to handle errors in Claude Code?” and you’ll get a textbook answer that could come from any documentation page.

Now imagine Claude Code has access to 136 battle-tested lessons covering everything from installation to multi-agent workflows. Ask the same question and it pulls from a specific lesson about meta-debugging patterns, gives you the exact command sequence, and warns you about the three pitfalls that trip up most developers.

That’s the difference between a generic AI and a specialized mentor.

The approach is dead simple: clone the Claude Code Mastery course repo to your machine, then tell Claude Code to reference it. One git clone, one line in CLAUDE.md. Five minutes of setup for months of better coaching.

And the best part? Learning by doing beats reading every time. Instead of front-loading 136 lessons and hoping you remember them later, you learn each concept exactly when you need it — in the middle of real work.

Step-by-Step Setup

Step 1: Clone the Course

Terminal window
git clone https://github.com/ShipWithAI/claude-code-mastery.git ~/claude-course

This puts the entire course — 16 phases, 64 modules, 136 lessons — on your local machine. About 50MB, takes seconds.

Step 2: Add One Line to Your CLAUDE.md

In the project you’re working on, open (or create) CLAUDE.md in the root directory and add:

Reference ~/claude-course for Claude Code best practices and patterns.
When I ask for help, suggest relevant lessons from the course.

That’s it. Claude Code reads CLAUDE.md at the start of every session. Now it knows about the course and will pull from it when relevant.

Step 3: A Complete CLAUDE.md Example

Here’s what a full CLAUDE.md might look like with the course reference integrated:

CLAUDE.md
## Project
E-commerce API built with Node.js + TypeScript + PostgreSQL.


## Conventions
- Files: kebab-case
- Routes → Services → Repositories pattern
- All business logic in services/
- TypeScript strict mode


## AI Mentor
Read ~/claude-course/COURSE-INDEX.md first to understand the course structure.
Reference ~/claude-course for Claude Code best practices.
When I ask about prompting, context management, or debugging strategies,
check the course for specific techniques and patterns.
Always cite the specific phase and module name when answering.

Step 4: Create a Mentor Slash Command

This is where it gets powerful. Create a file at .claude/commands/mentor.md in your project:

Read @~/claude-course/COURSE-INDEX.md to understand the course structure.


You are my Claude Code mentor. I want to learn by DOING, not reading.
Give me ONE practical task related to: $ARGUMENTS


RULES:
1. The task must be something I DO right now (run a command, write a prompt,
   edit a file). No theory.
2. After I complete it, tell me WHAT I learned and WHICH course lesson
   covers it (cite phase + module from COURSE-INDEX.md).
3. If I'm stuck, give me the exact command to type.
4. Keep it SHORT — max 10 lines.
5. After every 5 tasks, give me a scorecard of what I've learned.


Give me the first task now. Wait for my response before the next one.

Now you can type /mentor build a todo app and Claude Code becomes a hands-on coach — giving you one task at a time, checking your work, then citing which lesson you just practiced.

Other examples:

/mentor debug this API endpoint
/mentor refactor this component using best practices
/mentor set up a new project from scratch

Step 5: Or Paste This Mega Prompt Directly

If you prefer not to set up a slash command, just paste this at the start of any Claude Code session:

Read @~/claude-course/COURSE-INDEX.md to understand the course structure.


You are my Claude Code mentor. Teach me by guiding me to BUILD a real
Todo app from scratch. Don't give me a learning path or lecture me.
Give me ONE small task at a time, I do it, you check, then next task.


RULES:
1. Every task = something I DO (type a command, write a prompt, edit a file).
2. After each task, tell me WHAT I learned + WHICH lesson from COURSE-INDEX.md.
3. Start easy (install Claude Code), then gradually harder.
4. If I'm stuck, give the exact command. Don't make me guess.
5. Max 10 lines per response.
6. Scorecard every 5 tasks.
7. Todo app: HTML + CSS + vanilla JS. No frameworks.
8. By the end: working app + I know how to use Claude Code for my own projects.


Ask what OS I'm using, then give me the install command. Wait for my response.

Type this once and Claude Code walks you through ~25 tasks — from zero to a deployed Todo app. Each task takes 2-5 minutes, and after each one, Claude cites the exact course lesson you just practiced.

What You’ll Learn (Without Knowing It)

You don’t plan anything. Claude handles the progression:

  • Tasks 1-3: Install Claude Code, first conversation, create project folder
  • Tasks 4-12: Build HTML/CSS with Claude Code — learn prompting naturally
  • Tasks 13-22: Add JavaScript, multi-file editing, debugging, refactoring
  • Tasks 23-25: Add localStorage, polish, deploy

After each task, Claude tells you which course lesson applies. By the end, you’ve covered Phase 1 through Phase 8 without reading a single page.

Tips

  • Stay updated. The course gets new lessons regularly. A quick cd ~/claude-course && git pull keeps your mentor current.

  • Star the repo on GitHub to get notified when new phases and lessons are added. The course is actively maintained and growing.

Ready? The whole thing takes 5 minutes:

  1. Clone the course repo
  2. Add the AI Mentor section to your CLAUDE.md
  3. Create .claude/commands/mentor.md or paste the mega prompt
  4. Type /mentor build a todo app and start building

Star the repo if you find it useful — it helps other developers discover it too.