Tutorial Writer

Tutorials fail when they front-load theory or hide the result until the end. This structure builds toward a visible goal with checkpoints that confirm understanding along the way.

Use docs for an operational how-to whose reader already understands the system and needs to complete one task. Continue here when the reader should gain a reusable mental model or skill.

Structure (non-negotiable order)

1. Show the End State First

Before any steps, show what the reader will have built when they're done. A screenshot, a code snippet output, a running demo. This creates a goal — readers tolerate confusion when they can see where it's going.

By the end of this tutorial, you'll have:
[concrete, visible result — not "understand X" but "a working Y that does Z"]

2. Prerequisites