Post-session programming tutor for a developer who wants to grow. Use after an AI-assisted coding session to learn from it — it picks the one load-bearing decision the AI made that you most likely don't truly understand, makes you predict why before it reveals (breaking the "I get it" illusion), teaches the why…
The requirements changed while someone is halfway through a learn-as-you-go guide — fold the change in WITHOUT rewriting the work they've already executed. Reads foundation/progress.md to find the frontier (and stops to have it confirmed if it's missing or stale), verifies any new fact online, then delivers an impact…
Reconcile the REAL project against the learn-as-you-go guide you have been following — does what you built actually contain what the steps you executed told you to write? Reads the milestone checkpoints (the complete-file sections of each NNverify.md), diffs them against your files while ignoring cosmetic differences…
A reader hit a real issue while following a learn-as-you-go guide — report it and fix the guide so the issue can't recur. Diagnoses the root cause, fixes the step where they got stuck, then sweeps the WHOLE guide for every other place the same class of defect appears and fixes those too, adds a failure-note guard…
Use when the user wants to be taught/walked through code one tiny step at a time — triggers like "teach me this code", "walk me through this", "hold my hand", "explain step by step", "tutor me", "guide me through", "I want to learn this", or asks for a safe practice exercise to learn a concept.
Use when working in a project with Codebase Memory available and the task requires understanding system architecture, component relationships, design decisions, or where code belongs. Activates automatically when debugging unfamiliar code, explaining system behaviour, tracing data flows, or reasoning about where a…
Use when reviewing AI-generated curriculum content in the human review queue. Activates when working through .codebase-mooc/memory/humanreviewqueue.jsonl or when asked to review, approve, or assess generated curriculum content. Trigger phrases: "review the curriculum", "check the review queue", "approve this content"…
Use when a developer wants to learn about the codebase, start a learning session, understand how something works, or progress through the curriculum. Activates when the intent is learning rather than doing. Trigger phrases: "I'm new here", "walk me through", "help me understand", "start a learning session", "what…