# Teaching materials — `flutter-dev-agents`

Curriculum, lesson plans, and pedagogical strategy for the course
built on top of this repo. Everything in this directory is for
**building teaching material**, not for end-students directly.
Student-facing material — once written — will live in a separate
publishing repo.

## What's here

| File | For | Read first if you're… |
|---|---|---|
| [`strategy.md`](strategy.md) | Pedagogical thesis + audience segmentation + 8-week flagship architecture | ...starting to plan |
| [`catalogue.md`](catalogue.md) | Title + hook for every lesson + on-ramps | ...drafting marketing |
| [`lesson-01-the-4am-test.md`](lesson-01-the-4am-test.md) | Full publishable Lesson 1 outline | ...writing the first lesson |
| [`tomorrow-afternoon.md`](tomorrow-afternoon.md) | The single 90-minute first task | ...about to sit down and start |
| [`learning-log.md`](learning-log.md) | Engineering-session-to-teaching-takeaway distiller | ...wondering what to teach |

## Order of operations

1. Read `strategy.md` once. Internalise the four pedagogical
   frameworks (Sweller, Bruner, Karpathy, Carpentries).
2. Read `tomorrow-afternoon.md` the day you plan to start.
3. Use `lesson-01-the-4am-test.md` as the artifact to polish.
4. Update `learning-log.md` after every engineering session that
   teaches you something transferable.
5. Revisit `catalogue.md` only when planning the next lesson —
   *don't* try to design Lessons 2-8 before Lesson 1 has been
   tested on real students.

## Principle

> *We're teachers, not content providers. Teaching changes how
> the student thinks; content just changes what they've read.*

Every artifact in this directory should pass the test: would
removing this make a student worse at the thing we're teaching?
If not, it's content, not teaching. Cut it.
