Back to Brain Lab Skill · Teach Me · teach-me/
Skill Claude

Teach Me

teach-me/

3 views 0 downloads

An AI teacher that teaches any technical topic through interactive lessons and quizzes, adapts to your level as you go, and builds tutorial courses from repos or docs.

Teach Me: Brain Lab skill for Claude Code

An AI teacher that teaches any technical topic through interactive lessons and quizzes, adapts to your level as you go, and builds tutorial courses from repos or docs.

What it does

  • Studies before it teaches. A 6-stage pipeline: study, understand, map, plan, prepare, teach.
  • Interactive lessons that adapt to your level as you answer.
  • Teaches from anywhere: a topic, a documentation site (from URL) or a code repository (from this repo).
  • Quiz mode: say "quiz me" and the roles flip.
  • Remembers you. Saves your progress; say "continue" to pick up where you left off.
  • Builds courses: --course generates a full tutorial in Markdown, HTML or a Jekyll site.

Use

/teach-me React hooks
/teach-me Kubernetes from https://kubernetes.io/docs/
/teach-me this codebase from this repo --course --format=html

Install

Download this skill and copy the teach-me folder to .claude/skills/teach-me/ in your project, or to ~/.claude/skills/teach-me/ to use it in every project. Claude Code finds it on its own; you can also call it with /teach-me.

Part of the Teaching bundle.

Source: endorphin-ai/hasbrains-agent-kit. License: MIT.

Files (23)

Files

# Stage 3: MAP — Structure Knowledge for Teaching

You understand the material. Now organize it into a TEACHABLE structure.
The order YOU learned it is not the order you should TEACH it.

## The Mapping Principle

```
Knowledge structure:     Teaching structure:
(how experts think)      (how learners need it)

   Advanced               Simple
     ↑                      ↓
   Complex                Concrete
     ↑                      ↓
   Abstract      →        Familiar
     ↑                      ↓
   Foundational           Motivating
     ↑                      ↓
   Prerequisites          "Why should I care?"

Experts think top-down (abstract → specific).
Learners need bottom-up (concrete → abstract).
```

## Step 1: List All Concepts

From your Stage 2 understanding, list every concept. For each:

```
CONCEPT CARD:
├── Name: [clear, specific name]
├── One-sentence description: [what it IS]
├── Complexity: [1-5 scale]
├── Difficulty type: [counterintuitive / abstract / mechanical / gap / similar-but-different]
├── Prerequisites: [which concepts must come first]
├── Unlocks: [which concepts this enables]
└── Estimated teaching time: [minutes]
```

## Step 2: Build the Dependency Graph

Draw the "must come before" relationships:

```
EXAMPLE — Quantum Physics Concept Map:

                    [Why classical physics breaks] (5 min)
                         │
              ┌──────────┼──────────┐
              ↓          ↓          ↓
        [Wave nature] [Particle  [Probability
         of matter]   nature     replaces
                      of light]  certainty]
              │          │          │
              └──────┬───┘          │
                     ↓              │
              [Wave-particle        │
               duality]            │
                     │              │
                     └──────┬───────┘
                            ↓
                     [Wavefunctions]
                            │
                     ┌──────┼──────┐
                     ↓      ↓      ↓
              [Schrödinger [Super-  [Heisenberg
               equation]   position] uncertainty]
                     │
              ┌──────┼──────┐
              ↓      ↓      ↓
          [Particle [Tunneling] [Harmonic
           in box]              oscillator]
                                    │
                                    ↓
                            [Hydrogen atom]
```

### Dependency Rules

```
STRICT DEPENDENCY:   B literally cannot be understood without A
                     → A must be taught first, no exceptions

SOFT DEPENDENCY:     B is easier with A, but A isn't strictly required
                     → Teach A first if time allows, skip if audience is advanced

PARALLEL:            A and B don't depend on each other
                     → Teach in order of complexity (simpler first)
                     → Or teach the more "useful" one first

CIRCULAR:            A helps understand B, and B helps understand A
                     → Teach A at basic level → teach B → revisit A deeper
```

## Step 3: Design the Learning Sequence

Convert the dependency graph into a linear sequence:

```
SEQUENCING RULES:

1. MOTIVATION FIRST
   Start with WHY this topic matters, not WHAT it is.
   "You know how [everyday problem]? This topic solves that."

2. CONCRETE BEFORE ABSTRACT
   Show a specific example before the general rule.
   Show code/experiment before the theory that explains it.

3. SIMPLE BEFORE COMPLEX
   The minimal viable version first.
   Add complexity one layer at a time.

4. FAMILIAR BEFORE FOREIGN
   Anchor new concepts to things the learner already knows.
   "You know how X works? This is like that, but..."

5. MISCONCEPTION AT THE GATE
   If there's a common misconception about concept N,
   address it BEFORE or DURING concept N, not after.

6. CHECKPOINT AFTER EVERY MAJOR CONCEPT
   Don't teach 3 concepts and then check.
   Check after each one.
```

### Chunking Into Sessions

Group concepts into 15-45 minute teaching units:

```
CHUNK TEMPLATE:

Session N: "[Action-oriented title]"
├── Concepts: [c1, c2] (1 primary + 1 supporting max)
├── Time: [15-45 minutes]
├── Opens with: [bridge from previous session]
├── Core content: [primary concept with examples]
├── Checkpoint: [verify understanding of primary concept]
├── Supporting: [secondary concept if time allows]
├── Closes with: [bridge to next session]
└── Milestone: [what learner can DO after this session]
```

## Step 4: Define Milestones

Every session needs a VERIFIABLE milestone — something the learner
can DO, not just "know":

```
GOOD MILESTONES (verifiable):
✅ "Run this command and see output X"
✅ "Predict what happens when you change Y" (then verify)
✅ "Solve this problem using what we just learned"
✅ "Explain concept Z to an imaginary friend" (Feynman technique)
✅ "Modify this example to do something slightly different"

BAD MILESTONES (unverifiable):
❌ "You now understand quantum superposition"
❌ "You've learned about wavefunctions"
❌ "You know how middleware works"
```

## Step 5: Map Validation

Before proceeding to Stage 4, verify your map:

```
MAP VALIDATION CHECK:

□ Every concept has at least one prerequisite (except the very first)
□ No concept references something that comes LATER in the sequence
□ Every session has exactly ONE primary concept
□ Every session has a verifiable milestone
□ Complexity increases gradually (no sudden jumps)
□ The sequence starts with MOTIVATION, not definition
□ Common misconceptions are addressed BEFORE or DURING (not after)
□ Total estimated time is reasonable for the scope
□ A learner following this sequence could STOP at any session
  and still have usable knowledge up to that point
```