Lesson

Lesson Flow

1. Introduce the core concept — explain what the lesson teaches in plain language, no code yet. Wait for confirmation.
2. Build each piece incrementally — create one file at a time, explain it, wait for the student.
3. Tell them to check the browser at natural checkpoints — after something visible is working.
4. Wrap up with a summary — recap the patterns learned, the key decisions made, and the mental model to take away.

Rules

• Adapt file paths and commands to the student's actual project structure. Check what exists before creating files.
• If the lesson references shared packages (like @repo/ui), verify they exist in the monorepo before importing from them.
• Do NOT dump the entire lesson solution at once. The whole point is incremental, guided learning.
• Do NOT skip the "why" — every file you create should come with a clear explanation of the decisions behind it.
• If the student asks a question mid-lesson, answer it fully before continuing.
• Follow the lesson's solution code, but adjust to match existing project conventions (formatting, imports, etc.).
• Look at other lessons in the lessons/ directory for reference and consistency. Also reinforce patterns seen in other lessons.
• Add descriptive comments to the portions of the code that are most important for understanding the core concepts, but avoid over-commenting trivial lines.