tutorial_format

Summary

Production bar — every episode idea below must carry all of:
- Audience, Outcome, Runtime ( always present — including advanced packs )
- Demo — explicit pre-state of `reqlan-tutorials-demo` at cold open ( files present, caret, UI already open )
- Related — feature requirement links the episode proves; `@todo` if a demoed surface is not `@status done`
- `@example` — full recreateable fixture ( multi-file when the beat needs it ), fenced as opaque snippets when the sample itself contains braces
- `@script` — caption-ready spoken VO plus screen directions ( VO = voiceover; SCR = what to show ).
Structure: cold open → teach beats → misconception or recovery beat → try-this → end card.
Use exact Command Palette / chat paths. VS Code is primary; note Cursor skill / chat alternate when AI tools differ.
Use SCR: / VO: labels, not bracket tags, so they are not parsed as reference links.
Prefer denser beats over stretching runtime.
- `@slides` — one slide per major SCR beat ( ~ 7 – 10 ). Title, teach, try-this / end. `notes` = VO lines from `@script`.
Authored Reveal JSONC under decks is derived from `@slides` and may add JSONC-only fields
( `code_label`, dual-pane `code` / `code_b` ) for contrast beats.
Episodes are self-contained; series order is recommended: get-started → concepts → advanced.
After get-started 01 – 02, later get-started episodes can be sampled; concepts packs assume the loop was felt at least once.
Prefer 1080 p screen capture with a small inset face cam optional; logo end-card with site / marketplace links from phonebook.
Stay inside stated runtimes where possible ( get-started ~ 4 – 7 min, concepts ~ 8 – 12 min, advanced ~ 8 – 12 min ).

Jump to outbound references

Jump to inbound references