Demo to tutorial

Teach a developer to reproduce an existing implementation and understand its important decisions.

Read the implementation

Inspect the entrypoints, configuration, dependency declarations, setup notes, and recorded results before drafting. Establish the audience and learning outcome from the request or existing brief. Ask about missing audience or scope only when it changes the teaching approach.

Identify the tested target, code version, hardware/peripherals, model, software versions, and evidence of a successful run. Attribute supplied results. Separate executed steps from instructions inferred from source, and from steps awaiting verification. An absent run record permits an explicitly unverified draft, not an invented success story.

Use a supplied review or brief if available; neither is a required dependency. Preserve unresolved findings that affect the tutorial. Resolve version-sensitive facts from the project's pinned sources or authoritative documentation rather than substituting the latest API automatically.

Build the learning path

Open with what the reader will build and learn. State required prior knowledge, equipment, environment, accounts, downloads, and meaningful time or cost constraints when known.

Order the tutorial along an executable path: prepare → install/configure → run → inspect the result → understand the key decision → reset or clean up. Adapt the shape to the task rather than adding empty sections.