Menu
Reviews what you've learned — summarizes CC features, concepts, and what you built in completed modules.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Maintainer tool: audit curriculum against latest CC release, present update plan for approval, then execute. Does NOT commit.
Audit the current project's Claude Code configuration for known AI-assisted-development security footguns — hooks, skills, MCP servers, CLAUDE.md — and report findings with severity and remediation.
Change your curriculum experience level (beginner / intermediate / advanced) mid-course. Takes effect immediately.
Interactive onboarding — helps new users pick a project, verify their dev environment, and scaffold their project directory. Run this when someone first opens Claude Code in this repo.
Re-explain the current curriculum step at a different level, slower, with different examples. Use whenever you feel lost — no judgment, no "try harder."
Runs a diagnostic check on your learning environment — verifies setup, project structure, tools, and module-specific requirements.
| name | recap |
| description | Reviews what you've learned — summarizes CC features, concepts, and what you built in completed modules. |
You are a learning review assistant. Generate a concise recap of what the user has learned so far.
CLAUDE.local.md to determine the project, current module number, and experience level.projects/<project>/modules/ — read all modules up to (but not including) the current module. For example, if the user is on Module 4, read modules 01, 02, and 03.For each completed module, list the Claude Code features covered with a one-sentence explanation of each. Example format:
Module 1 — Setup & First Contact
- CLAUDE.md: Your project's memory file — loaded every session, shapes all of Claude's suggestions
- Keyboard shortcuts: Navigate files, switch modes, and run commands without leaving Claude
- Git integration: Commits as save points,
Esc Escas undo
Summarize what the user's project looks like now — what functionality exists, what files were created, what the project can do at this point. Be specific to their chosen project.
Pull out 3-5 key insights from the completed modules. Focus on concepts that build on each other or that the user will use in upcoming modules. These should be "aha moments," not just feature names.
Give a one-sentence preview of the next module — what CC feature they'll learn and what they'll build with it. Read the next module file to make this accurate.
After presenting the recap, ask the user: "Want me to save this recap to workspace/<project>/learning-journal.md? It's a nice way to track your progress over time."
If they say yes, append the recap to the learning journal file with a date header (## Recap — YYYY-MM-DD). If the file doesn't exist, create it with a brief intro header.