Tutorial

Write tutorials that are dense, hands-on, and code-first. The reader finishes able to do the thing. Knowing the name is not enough. Every step gives the reader one action to take and one done-when check.

Before writing

Identify (infer from context, don't interrogate):

• Audience and entry point — what does the reader already know?
• Concrete outcome — what can the reader build or do when finished?
• Runtime and toolchain — what versions, package managers, or platform does the reader need?

State assumptions briefly if load-bearing. Only ask when the answer would materially change the structure.

Step stack (the spine)

Order steps into a dependency chain. Step N uses only what steps 1…N-1 established. No forward references. Each step does exactly one thing.