explanatory-output-style
claudeAdds educational insights about implementation choices and codebase patterns (mimics the deprecated Explanatory output style)
hooks
Learn while you vibe code: Claude reads what you're really asking, explains every step as Doing / Why / How-to-do-it-yourself, remembers what you've learned across sessions, teaches you to rebuild features from scratch, breaks down the hard bugs it solved, tours functions and algorithms, lets you write key lines and type git/npm commands yourself, and has an ADHD-friendly mode.
Plugin vibe-learning from marketplace vibe-learning-marketplace in VuxSussy/VibeLearning. Commands read from the repo's manifest — 19 days ago.
This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.
activityShow everything the AI did in this session — files read and changed, commands run — explained in plain words. Use when the user types $activity (optionally followed by: [last N | files | commands]).
adhd-offTurn off ADHD-friendly mode (normal 2-3 line explanations stay on). Use when the user types $adhd-off.
adhd-onTurn on ADHD-friendly mode — small chunks, less text, one thing at a time. Use when the user types $adhd-on.
algorithmsIdentify 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) i
explainExplain a file, snippet, command or concept in plain words (defaults to the latest change). Use when the user types $explain (optionally followed by: [file | snippet | concept]).
functionsList 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
glossaryList and define the programming terms that came up in this session. Use when the user types $glossary (optionally followed by: [specific term - optional]).
hard-caseExplain 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
i-have-adhdADHD-friendly mode for people who have ADHD or struggle to focus while learning to code: small chunks, one step at a time, few words, lots of visual anchors. Use when the user says "I have ADHD", "I can't focus", "too much text", "this is overwhelming", "I'm lost", or when VibeLearning's ADHD mode i
interviewPractice explaining your project as in a job interview or project defense, to make sure you understand what you vibe coded. Use when the user types $interview (optionally followed by: [practice - for a mock interview, one question at a time]).
learn-offTurn off automatic explanations (from the next session on; the current session stops explaining right away). Use when the user types $learn-off.
learn-onTurn learn-while-you-build mode back on. Use when the user types $learn-on.
learnTeach vibe coders what is happening while you build and how to make it themselves: every step gets a plain Doing / Why / How explanation. Use when the user is a beginner, says "explain", "I don't understand", "teach me", "why", or while creating/editing code, running commands or installing libraries
mapA plain-language map of the project — what each folder and key file is for, and how a request flows through it. Use when the user types $map (optionally followed by: [folder - optional]).
practice-offTurn off practice mode — Claude writes everything as usual (still explains). Use when the user types $practice-off.
practice-onTurn on practice mode — Claude leaves 3-10 important lines of each new feature for you to write. Use when the user types $practice-on.
practiceLet 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).
progressWhat you've learned so far, across every session — terms, concepts you were unsure about, hard cases — and what to review next. Use when the user types $progress (optionally followed by: [project name - optional]).
quizA quick 3-question quiz about what was just built, to check you really understood it. Use when the user types $quiz (optionally followed by: [topic - optional]).
rebuildTeach the user how to build something themselves from an empty file, using the real code in their project - the core idea, a blueprint of the parts and the order to build them, then milestones with the key code, how a developer would figure each one out, and how to check it works. Use when the user
recapSummarize what you learned this session as study notes. Use when the user types $recap (optionally followed by: [save - to write it to LEARNING_NOTES.md]).
type-it-offTurn off type-it mode — the AI runs git/npm commands itself again (still explaining them). Use when the user types $type-it-off.
type-it-onTurn on type-it mode — the AI lists the git/npm/pip commands with a guide for each, and you type them. Use when the user types $type-it-on (optionally followed by: [tools to learn, e.g. "git" or "git npm" - default: git, npm, npx, yarn, pnpm, bun, pip]).
type-itHand 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 comm
whereWhere was I? A quick "you are here" when you're lost or just got back. Use when the user types $where.
whyWhy this approach? Compare it with the alternatives. Use when the user types $why (optionally followed by: [decision to explain]).
/vibe-learning:activityShow everything the AI did in this session — files read and changed, commands run — explained in plain words
/vibe-learning:adhd-offTurn off ADHD-friendly mode (normal 2-3 line explanations stay on)
/vibe-learning:adhd-onTurn on ADHD-friendly mode — small chunks, less text, one thing at a time
/vibe-learning:explainExplain a file, snippet, command or concept in plain words (defaults to the latest change)
/vibe-learning:glossaryList and define the programming terms that came up in this session
/vibe-learning:interviewPractice explaining your project as in a job interview or project defense, to make sure you understand what you vibe coded
/vibe-learning:learn-offTurn off automatic explanations (from the next session on; the current session stops explaining right away)
/vibe-learning:learn-onTurn learn-while-you-build mode back on
/vibe-learning:mapA plain-language map of the project — what each folder and key file is for, and how a request flows through it
/vibe-learning:practice-offTurn off practice mode — Claude writes everything as usual (still explains)
/vibe-learning:practice-onTurn on practice mode — Claude leaves 3-10 important lines of each new feature for you to write
/vibe-learning:progressWhat you've learned so far, across every session — terms, concepts you were unsure about, hard cases — and what to review next
/vibe-learning:quizA quick 3-question quiz about what was just built, to check you really understood it
/vibe-learning:recapSummarize what you learned this session as study notes
/vibe-learning:type-it-offTurn off type-it mode — the AI runs git/npm commands itself again (still explaining them)
/vibe-learning:type-it-onTurn on type-it mode — the AI lists the git/npm/pip commands with a guide for each, and you type them
/vibe-learning:whereWhere was I? A quick "you are here" when you're lost or just got back
/vibe-learning:whyWhy this approach? Compare it with the alternatives
sh "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/context.py"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/log-activity.py"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/type-it-guard.py"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/learner.py"
Adds educational insights about implementation choices and codebase patterns (mimics the deprecated Explanatory output style)
hooks
Agentic QE (external: maintained in proffesor-for-testing/agentic-qe, pinned to v3.15.17): a quality-engineering fleet with 11 QE agents, 9 skills, 9 commands, the agentic-qe MCP server pinned to the plugin version, and the aqe-mod guard that refuses destructive operations on AQE learning data
9 skills · 9 commands · 11 agents · 1 MCP server
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Full Domino Data Lab platform support — workspaces, jobs, model deployment, experiment tracking, GenAI tracing, Spark/Ray/Dask, and app deployment for data science teams
26 skills · 4 commands · 3 agents · 1 MCP server
Claude Code native multi-agent orchestration with intelligent model routing across agents and skills. Zero learning curve. Maximum power.
85 skills · 20 commands · 19 agents · 1 MCP server · hooks
Turn any learning intent into a personalized Coursera experience. Asks three quick questions (topic, familiarity, preferred format), searches Coursera's catalog, and delivers the right next step — a course, hands-on project, short video, or live roleplay — then maps a path forward. Requires the Coursera connector for catalog tools.
1 skill
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.