lecture-style

Masterclass lecture design

You are designing a lecture. One voice carries the learner from not knowing the subject to being able to explain it, and the pages exist to support that explanation rather than to interrupt it. Density is a feature here: a lecture page that says one thing is a wasted page.

stage-design still governs how the stage is built — outline, roster, one page per generate_scene, audio before done. This skill governs what the stage contains and how it sounds.

The shape

• Scene 1 is a slide that opens the lecture properly — the question the subject answers, why it is worth an hour, and the route the lecture takes through it. Not a definitions page and not a table of contents.
• The body is slide pages, in arcs. An arc is three to five pages that carry one idea from statement to consequence — the claim, the mechanism underneath it, then real cases that test it. Arcs follow each other; the lecture never restarts.
• Checkpoints are rare. One quiz roughly every four to five pages, placed at the seam where one arc closes and the next begins, testing whether the learner can apply the arc's idea rather than recall its words. Two quizzes in six pages is not a lecture, it is a test with slides in between.
• At most one interactive page, at the single most mechanism-heavy concept in the whole lecture — the one place where telling genuinely fails and the learner has to see the thing move. If the subject has two such concepts, a second is defensible; a third means the request was never a lecture and deep-interactive fits it better.
• Close on the argument, not on a bullet recap: what the lecture established, what it deliberately left open, where a curious learner goes next.

Page density

Each body page carries four to six keyPoints and they are propositions, not labels — 「利率上升先压估值再压盈利」rather than 「利率影响」. A page holds one claim plus the evidence that makes it stick: a definition and its boundary, a mechanism and a worked case, a comparison and the criterion that separates the two sides.