tutorial_philosophy

Producers may cite mission_statement, llm_first, vsc_first, general_purpose, simplicity, and inspiration as constraints on what an episode must prove. These shape production choices — they are never spoken to, or shown to, the learner.
Production guidance per constraint:
- llm_first: demonstrate focused context — search, local slice, add-to-context — by doing it on camera before pasting a whole workspace. Never let VO or a slide label the workflow as a philosophy.
- vsc_first: primary demos live in VS Code / compatible editors with the extension installed.
- general_purpose: at least one get-started beat and one advanced beat use a non- " enterprise software " framing ( personal knowledge, ops checklist, or creative brief ).
- simplicity: start with one-liners and one file; introduce braces, imports, and attributes only when the viewer feels the need.
Show, then name: write a real idea, link it, create a base, open the activity bar — then put names to what the learner already did in concepts_series.
Hard rule — learner-facing surfaces must never lecture. VO, any on-screen text the viewer reads ( title cards, end cards, callouts, quiz prompts ), slide heading / body / fragments / notes, try-this prompts, and fixture prose inside `@example` must NOT name:
- product philosophy or constitution principles ( " llm-first ", " mission ", " semantic requirements as code ", " token discipline " );
- design lineage ( Obsidian, industrial control, " ontology " as a brand concept );
- syllabus pedagogy ( " verbs then nouns ", " teaches judgement " );
- taste lectures ( " simplicity over scaffolding ", " calm tiles, not a laundry list ", " keep copy short " ).
Instead: show the workflow and the result, and name only surfaces and actions the user can perform.
Producer teaching-order note ( guidance for planning, not copy for the screen ): get-started demonstrates the core actions; concepts puts names to the building blocks; advanced shows judgement.

Interactive page: tutorial_philosophy