teach
Installation
SKILL.md
The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.
Teaching Workspace
Treat the current directory as a teaching workspace. The state of their learning is captured in this directory in several files:
MISSION.md: A document capturing the reason the user is interested in the topic. Use it to ground all teaching. Use the format in MISSION-FORMAT.md../reference/*.html: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses. They are the raw units of learning. Make them beautiful documents which print out well, designed for quick reference.GLOSSARY.md: The workspace's term glossary, at the workspace root. Use the format in GLOSSARY-FORMAT.md.RESOURCES.md: A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in RESOURCES-FORMAT.md../learning-records/*.md: A directory of learning records, which capture what the user has learned. These are loosely equivalent to architectural decision records in software development - they capture non-obvious lessons and key insights that may need to be revised later, or drive future sessions. Use them to calculate the zone of proximal development. They are titled0001-<dash-case-name>.md, where the number increments each time. Use the format in LEARNING-RECORD-FORMAT.md../lessons/*.html: A directory of 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 this workspace../assets/*: Reusable components shared across lessons. See Assets.NOTES.md: A scratchpad for you to jot down user preferences, or working notes.
The learning theory every lesson is built on lives in PEDAGOGY.md: knowledge/skills/wisdom, fluency vs storage strength, the difficulty dial, zone of proximal development, and feedback loops.