vuxsussy/vibe-learning
Learn while you vibe code: Claude explains every step in 2-3 plain lines, shows what it did, tours the functions in a file, names the algorithms it finds, breaks down the hard bugs it solved, lets you write key lines and type the git/npm commands yourself, and has an ADHD-friendly mode.
Turn off ADHD-friendly mode (normal 2-3 line explanations stay on). Use when the user types $adhd-off.
Turn on ADHD-friendly mode — small chunks, less text, one thing at a time. Use when the user types $adhd-on.
Identify the algorithms, data structures and design patterns used in code (sorting, searching, recursion, hashing, caching/memoization, debounce/throttle, retry with backoff, BFS/DFS, dynamic programming, two pointers, observer, singleton, MVC...) and explain each in plain words with speed (Big-O) in everyday terms. Use when the user asks "what algorithm is this", "how does this work", "is this efficient", "why is it slow", or when you write code built on a notable algorithm. Invoke with a file, function or folder (defaults to the latest code discussed).
List every function, method and class in a file and explain each one in plain words (what it does, inputs → output, who calls it), plus how they connect; or explain one function step by step. Use when the user asks "what's in this file", "what does this file do", "explain these functions", "walk me through this code", or opens an unfamiliar file they vibe coded. Invoke with <file> for a tour or <file> <function> for a deep dive.
Explain a "hard case" the AI just solved so the vibe coder truly understands it. Use right after fixing a tricky bug, a confusing error, something that needed several attempts, or problems involving async/timing/memory/CORS/permissions/cache/library versions, or when the user asks "why did that fix it?", "what did you just change?", "explain this case". Invoke directly for a deep dive into the latest hard case (add save to keep it in LEARNING_NOTES.md).
Turn off automatic explanations (from the next session on; the current session stops explaining right away). Use when the user types $learn-off.
Turn learn-while-you-build mode back on. Use when the user types $learn-on.
Let the vibe coder write a small, meaningful piece of code (3-10 lines) themselves, with tiered hints and feedback. Use when the user says "let me write it", "I want to try", "don't do it all for me", or when practice mode is on. Invoke it for one task right now (optionally naming the spot).
Turn off practice mode — Claude writes everything as usual (still explains). Use when the user types $practice-off.
Turn on practice mode — Claude leaves 3-10 important lines of each new feature for you to write. Use when the user types $practice-on.
Hand terminal commands for tools the user wants to learn (git, npm, yarn, pnpm, pip...) to the user as a guided checklist instead of running them. Use when type-it mode is on, when a command was blocked by the VibeLearning guard, or when the user says "I want to learn git/npm", "let me type the commands", "don't run git for me".
Turn off type-it mode — the AI runs git/npm commands itself again (still explaining them). Use when the user types $type-it-off.
Where was I? A quick "you are here" when you're lost or just got back. Use when the user types $where.