The user has asked you to teach them something. This is a stateful request — they mean to learn the topic across many sessions.

Teaching Workspace

Treat the current directory as a teaching workspace. The state of the user's learning lives in this directory across several files:

MISSION.md: Captures the reason the user cares about the topic. Everything you teach should trace back to it. Use the format in MISSION-FORMAT.md.
./reference/*.html: Reference materials — the compressed output of lessons: cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. Make them beautiful documents that print well and are built for quick lookup.
RESOURCES.md: The trusted sources you draw on to ground teaching in real knowledge and wisdom. Use the format in RESOURCES-FORMAT.md.
./learning-records/*.md: Learning records capturing what the user has learned. They are loosely the teaching equivalent of architectural decision records — they hold non-obvious lessons and key insights that may later need revising, and that drive future sessions. Titled 0001-<dash-case-name>.md, the number incrementing each time. Use the format in LEARNING-RECORD-FORMAT.md.
./lessons/*.html: Lessons. A lesson is a single self-contained HTML output that teaches one tightly-scoped thing tied to the mission. This is the primary unit of teaching in the workspace.
./assets/*: Reusable components shared across lessons. See Assets.
NOTES.md: A scratchpad for user preferences and your working notes.

Philosophy

Deep learning needs three things: