Teach Me
teach-me/
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.

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:
--coursegenerates 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
-
- analysis-schema.md
- course-builder.md
- example.md
- format-github-pages.md
- format-html-interactive.md
- format-markdown.md
- knowledge-store.md
- learning-pipeline.md
- mit-ocw.md
- quiz-mode.md
- roadmap-builder.md
- stage-1-study.md
- stage-2-understand.md
- stage-3-map.md
- stage-4-plan.md
- stage-5-prepare.md
- stage-6-teach.md
- student-model.md
- teaching-examples.md
- workflows.md
- SKILL.md
# Markdown Output Format
## File Structure
```
course/
├── INDEX.md # Landing page + tutorial table
├── 01-tutorial-title.md
├── 02-tutorial-title.md
├── 03-tutorial-title.md
└── ...
```
## Naming Convention
Files: `NN-kebab-case-title.md` (e.g., `01-write-your-first-test.md`)
## INDEX.md Template
```markdown
# [Course Title]
[1-2 paragraph summary: what this course teaches, what learners will build]
## Who Is This For?
[Target audience, prerequisites, what they DON'T need to know]
## What You'll Build
[Describe the progressive project across all tutorials]
## Tutorials
| # | Title | Time | Difficulty | What You'll Learn |
|---|-------|------|------------|-------------------|
| 1 | [Title](./01-title.md) | 20 min | Beginner | Short description |
| 2 | [Title](./02-title.md) | 30 min | Beginner | Short description |
| 3 | [Title](./03-title.md) | 25 min | Intermediate | Short description |
**Total time**: ~X hours
## Getting Started
[Setup instructions or link to Tutorial 1]
```
## Per-Tutorial Template
```markdown
# Tutorial N: [Action-Oriented Title]
> **Time**: X min | **Difficulty**: Beginner/Intermediate/Advanced
> **Prerequisites**: [Tutorial 1](./01-title.md), [Tutorial 2](./02-title.md)
<!-- For docs-sourced courses only -->
> **Official Docs**: [Page Title](url) — we go deeper below
## What You'll Learn
- Specific skill 1
- Specific skill 2
- Specific skill 3
## Why This Matters
[2-3 paragraphs: real-world context, connection to previous/next tutorials]
## Walkthrough
### Step 1: [Action Verb — Create / Configure / Write / Add]
[Show code block with file path]
```typescript
// src/auth/middleware.ts
export function authMiddleware(req, res, next) {
// ...
}
```
[Explain AFTER showing the code]
### Step 2: [Action Verb]
...
## Common Mistakes
### ❌ [Mistake Description]
```typescript
// DON'T do this
page.waitForTimeout(3000);
```
### ✅ Do This Instead
```typescript
// Playwright auto-waits
await expect(locator).toBeVisible();
```
**Why**: [Explanation of why the mistake is bad]
---
## Try It Yourself
[Challenge description — specific, extends the tutorial]
<details>
<summary>💡 Hint</summary>
[Hint text]
</details>
<details>
<summary>✅ Solution</summary>
```typescript
// Solution code
```
</details>
## Key Takeaways
- Transferable principle 1
- Transferable principle 2
- Transferable principle 3
## What's Next
[1-2 sentences bridging to the next tutorial]
---
## Further Reading
- [Official Docs: Topic](url)
- [Blog Post: Related Topic](url)
---
[← Previous: Tutorial Title](./NN-title.md) | [Next: Tutorial Title →](./NN-title.md)
```
## Writing Rules for Markdown
1. Use standard GitHub-Flavored Markdown (GFM)
2. Use `<details>` tags for collapsible hints/solutions
3. Always include language tags on code fences (```typescript, ```bash, etc.)
4. Use relative links between tutorial files
5. Include a horizontal rule `---` before the Previous/Next nav
6. Use blockquotes `>` for the metadata header
7. File paths in code blocks go as comments on the first line