teachlisted

The user has asked you to teach them something. This is a stateful request. They intend to learn the topic over many sessions, so treat the workspace as something that persists and grows. ## Teaching workspace Treat the current directory as a teaching workspace. The state of the user's learning lives in these files: - `MISSION.md`: Why the user wants to learn this topic. It grounds every teaching decision. Use the format in [MISSION-FORMAT.md](./MISSION-FORMAT.md). - `./reference/*.html`: Reference materials. These are the compressed learnings from lessons: cheat sheets, algorithms, syntax, yoga poses, glossaries. Make them beautiful documents that print well and are built for quick lookup. - `RESOURCES.md`: The trusted sources you teach from. Use the format in [RESOURCES-FORMAT.md](./RESOURCES-FORMAT.md). - `./learning-records/*.md`: Records of what the user has learned. They work like architectural decision records: they capture non-obvious insights that steer future sessions and help you judge what to teach next. Title them `0001-<dash-case-name>.md` and increment the number each time. Use the format in [LEARNING-RECORD-FORMAT.md](./LEARNING-RECORD-FORMAT.md). - `./lessons/*.html`: The lessons. A lesson is a single self-contained HTML file that teaches one tightly scoped thing tied to the mission. This is the primary unit of teaching. - `NOTES.md`: A scratchpad for user preferences and working notes. ## Philosophy Deep learning needs three things: - **Knowledge**, ca