|
| 1 | +# AI-Learn Plugin |
| 2 | + |
| 3 | +**Socratic learning mode for Claude Code.** Transform Claude into a patient coding mentor that guides you through problem-solving instead of just writing code for you. |
| 4 | + |
| 5 | +--- |
| 6 | + |
| 7 | +## What This Plugin Does |
| 8 | + |
| 9 | +Switches Claude from code-generation mode to teaching mode. Instead of giving you solutions, Claude asks probing questions, provides hints, and guides you toward discovering answers yourself. The result: you actually learn and retain the knowledge rather than passively consuming AI-generated code. |
| 10 | + |
| 11 | +## Available Commands |
| 12 | + |
| 13 | +### `/learn` |
| 14 | + |
| 15 | +Activate Socratic teaching mode for your next coding problem. |
| 16 | + |
| 17 | +**What it does:** |
| 18 | + |
| 19 | +- Assesses your current knowledge before diving in |
| 20 | +- Asks guiding questions instead of providing answers |
| 21 | +- Offers hints when you're stuck rather than solutions |
| 22 | +- Helps you trace through logic and discover bugs yourself |
| 23 | +- Reinforces learning by having you explain solutions in your own words |
| 24 | + |
| 25 | +**Usage:** |
| 26 | + |
| 27 | +``` |
| 28 | +/learn |
| 29 | +# Then describe what you want to learn: |
| 30 | +"I want to understand how to implement a binary search tree" |
| 31 | +
|
| 32 | +# Claude will ask about your current knowledge |
| 33 | +# Guide you through the implementation step by step |
| 34 | +# Let you write the code yourself |
| 35 | +# Help you debug through questions, not answers |
| 36 | +``` |
| 37 | + |
| 38 | +### `/learn-review` |
| 39 | + |
| 40 | +Get a Socratic code review - Claude asks questions to help you spot issues yourself. |
| 41 | + |
| 42 | +**What it does:** |
| 43 | + |
| 44 | +- Reviews your code through targeted questions |
| 45 | +- Helps you discover bugs by tracing through edge cases |
| 46 | +- Probes design decisions to deepen understanding |
| 47 | +- Builds your self-review and debugging skills |
| 48 | + |
| 49 | +**Usage:** |
| 50 | + |
| 51 | +``` |
| 52 | +/learn-review |
| 53 | +# Then paste your code |
| 54 | +
|
| 55 | +# Claude will ask you to explain what it does |
| 56 | +# Guide you through edge cases with questions |
| 57 | +# Help you discover issues yourself |
| 58 | +# Build lasting debugging intuition |
| 59 | +``` |
| 60 | + |
| 61 | +--- |
| 62 | + |
| 63 | +## Quick Start |
| 64 | + |
| 65 | +### Installation |
| 66 | + |
| 67 | +``` |
| 68 | +/plugin install ai-learn@claude-code-plugins-dev |
| 69 | +``` |
| 70 | + |
| 71 | +### Usage |
| 72 | + |
| 73 | +``` |
| 74 | +# Activate teaching mode |
| 75 | +/learn |
| 76 | +
|
| 77 | +# Describe what you want to learn |
| 78 | +"Help me understand async/await in JavaScript" |
| 79 | +
|
| 80 | +# Claude guides you through it with questions |
| 81 | +# You write the code, Claude provides hints |
| 82 | +# You actually learn instead of copy-pasting |
| 83 | +``` |
| 84 | + |
| 85 | +--- |
| 86 | + |
| 87 | +## Why Use Teaching Mode? |
| 88 | + |
| 89 | +### The Problem with Code Generation |
| 90 | + |
| 91 | +When Claude writes code for you: |
| 92 | +- You get a working solution immediately |
| 93 | +- But you may not understand why it works |
| 94 | +- You can't reproduce it without asking again |
| 95 | +- Your fundamental skills may atrophy over time |
| 96 | + |
| 97 | +### The Teaching Mode Approach |
| 98 | + |
| 99 | +When Claude teaches you: |
| 100 | +- You struggle productively with the problem |
| 101 | +- You build mental models that stick |
| 102 | +- You develop intuition for similar problems |
| 103 | +- You retain knowledge for future use |
| 104 | + |
| 105 | +### When to Use Each |
| 106 | + |
| 107 | +**Use teaching mode (`/learn`) for:** |
| 108 | +- Unfamiliar libraries or frameworks |
| 109 | +- Complex patterns you want to deeply understand |
| 110 | +- Skills you're rusty on and need to refresh |
| 111 | +- Concepts you keep having to look up |
| 112 | + |
| 113 | +**Use standard Claude for:** |
| 114 | +- Boilerplate you understand but don't want to type |
| 115 | +- Quick fixes in areas you're confident |
| 116 | +- Time-sensitive tasks where speed matters |
| 117 | +- Repetitive tasks that don't need deep understanding |
| 118 | + |
| 119 | +--- |
| 120 | + |
| 121 | +## The Teaching Flow |
| 122 | + |
| 123 | +### Phase 1: Assessment |
| 124 | +Claude asks what you already know to meet you where you are. |
| 125 | + |
| 126 | +### Phase 2: Foundation |
| 127 | +Fills in prerequisite knowledge gaps before tackling the main problem. |
| 128 | + |
| 129 | +### Phase 3: Guided Implementation |
| 130 | +You write code while Claude asks questions and provides hints. |
| 131 | + |
| 132 | +### Phase 4: Error Discovery |
| 133 | +When bugs appear, Claude guides you to find them through questions. |
| 134 | + |
| 135 | +### Phase 5: Reinforcement |
| 136 | +You explain the solution in your own words to solidify understanding. |
| 137 | + |
| 138 | +--- |
| 139 | + |
| 140 | +## Example Interaction |
| 141 | + |
| 142 | +``` |
| 143 | +User: /learn |
| 144 | +User: I want to implement debouncing in JavaScript |
| 145 | +
|
| 146 | +Claude: Before we dive in, what's your understanding of |
| 147 | + closures in JavaScript? Debouncing relies heavily |
| 148 | + on them. |
| 149 | +
|
| 150 | +User: I know closures let inner functions access outer |
| 151 | + variables even after the outer function returns. |
| 152 | +
|
| 153 | +Claude: Perfect. And what about setTimeout - how does |
| 154 | + that work with closures? |
| 155 | +
|
| 156 | +User: The callback can access variables from when |
| 157 | + setTimeout was called. |
| 158 | +
|
| 159 | +Claude: Exactly. So here's the core puzzle: if you want |
| 160 | + a function that only runs after the user stops |
| 161 | + typing for 300ms, what would you need to track? |
| 162 | +
|
| 163 | +User: The timer ID so I can cancel it? |
| 164 | +
|
| 165 | +Claude: Right! And where would you store that ID so it |
| 166 | + persists between calls but isn't global? |
| 167 | +
|
| 168 | +User: In a closure! |
| 169 | +
|
| 170 | +Claude: Now you're getting it. Try writing the skeleton |
| 171 | + of a debounce function. What parameters would it |
| 172 | + take? |
| 173 | +``` |
| 174 | + |
| 175 | +--- |
| 176 | + |
| 177 | +## Escape Hatch |
| 178 | + |
| 179 | +Teaching mode respects your autonomy. If you hit genuine frustration: |
| 180 | + |
| 181 | +- Say "just show me" and Claude will provide the solution with explanation |
| 182 | +- Say "I give up" and Claude will walk through the answer |
| 183 | +- You can always return to teaching mode for the next problem |
| 184 | + |
| 185 | +Learning requires agency. Forced struggle past the point of productivity isn't helpful. |
| 186 | + |
| 187 | +--- |
| 188 | + |
| 189 | +## Plugin Details |
| 190 | + |
| 191 | +- **Name:** AI-Learn Plugin |
| 192 | +- **Type:** AI Instruction Plugin (Slash Commands) |
| 193 | +- **Commands:** `/learn`, `/learn-review` |
| 194 | +- **Version:** 1.0.0 |
| 195 | +- **License:** MIT |
| 196 | +- **Author:** Charles Jones |
| 197 | + |
| 198 | +--- |
| 199 | + |
| 200 | +## Contributing |
| 201 | + |
| 202 | +Found a bug or have a suggestion? [Open an issue](https://github.com/charlesjones-dev/claude-code-plugins-dev/issues) or submit a pull request! |
| 203 | + |
| 204 | +--- |
| 205 | + |
| 206 | +## License |
| 207 | + |
| 208 | +MIT License - See [LICENSE](LICENSE) file for details. |
| 209 | + |
| 210 | +--- |
| 211 | + |
| 212 | +**Built for developers who want to learn, not just ship.** |
0 commit comments