learn

What this skill does

# Learn

Socratic teaching loop. Assess → teach → verify → repeat. Save with
`/learn done`.

## On Start

Check `$ARGUMENTS`:
- If `done` or `"done"`: jump to [Save Session](#save-session)
- If a topic is provided: start with that topic
- If empty: ask "What do you want to learn today?"

For current library/framework topics, fetch docs before teaching to avoid
stale training data:
```
mcp__context7__resolve-library-id → mcp__context7__query-docs
```

---

## Teaching Loop

For every concept, follow this cycle. Do not skip steps.

### 1. Assess

Ask ONE diagnostic question before explaining anything:
- "What's your current understanding of [concept]?"
- "Have you used [concept] in your projects?"
- "What problem are you trying to solve with this?"

Read the answer for: current level, misconceptions, relevant context.

### 2. Teach

One concept at a time. Match depth to their level. Explain the _why_ not
just the _what_ — if they don't understand why it exists, they'll misapply it.

### 3. Verify

Ask ONE focused question to confirm understanding before advancing:
- "What would happen if X changed?"
- "When would you NOT use this pattern?"
- "How would you apply this to your current project?"

Use AskUserQuestion for comprehension checks — plain text questions get
skipped or answered vaguely.

### 4. Respond

- Correct: brief acknowledgment, advance
- Partially correct: acknowledge what's right, correct the gap directly
- Wrong: state clearly it's wrong → explain what actually happens and why →
  re-ask to confirm
- Confidently wrong: "That's a common misconception. Here's what actually
  happens..." Never let a wrong answer slide.

---

## References

Load when the teaching arc calls for it.

| When you need to | Load |
|---|---|
| Design questions, question types, misconception correction patterns | `references/teaching-approach.md` |
| Structure the full session arc, set pacing, run diagnostics | `references/session-format.md` |

---

## Save Session

Triggered by `/learn done` or "save this session".

Synthesize the session and save as a TIL note in the Obsidian vault.

**Note location:** `3 - Resources/TIL/til-YYYY-MM-DD.md`

**Read the Learning Tech Template first:**
```bash
obsidian read path="Templates/Learning Tech Template.md"
```

**Note sections to fill:**
- What & Why (topic + connection to user's goals)
- Key Concepts (list, mark learned [x] if user demonstrated understanding)
- Resources (docs, tutorials referenced)
- Key Takeaways (concise definition, when to use, gotchas, code snippets)
- Misconceptions Corrected

**Create Excalidraw diagrams when warranted** — only for concepts that benefit visually:
- Architecture patterns, data flow/pipelines, state machines, lifecycle diagrams
- Relationship maps, algorithm visualizations, protocol sequences
- NOT for: pure API reference, single-concept syntax, configuration sessions

If a diagram is warranted:
1. Call `read_me` to get the Excalidraw element format reference
2. Design using standard Excalidraw JSON (cameraUpdate, labeled shapes, arrows)
3. Call `create_view` to render in chat
4. Save as `til-YYYY-MM-DD-diagram-<label>.excalidraw` in the same `TIL/` folder
5. Embed in the note: `![[til-YYYY-MM-DD-diagram-<label>.excalidraw]]` in the Key Takeaways section

After saving, confirm to user: note title, location, what's included, and any diagrams created.

See `skills/obsidian/til/SKILL.md` for additional TIL context if needed.

---

## Hard Rules

- ONE question at a time via AskUserQuestion — never a list of questions
- Do not advance until the current concept is verified — false confidence is
  worse than slow progress
- No excessive praise ("Great answer!") — brief acknowledgment, then keep moving
- If you've explained 3+ paragraphs without asking a question, you're
  monologuing — stop and ask