# Tutorial format

Use for one lesson that teaches a newcomer by doing. Optimize for confidence and sequence, not coverage.

## Great instance

- Starts with the learner's starting state and the exact outcome they will have.
- Gives one action per `h2`; each section can stand as one reader page.
- Uses small code fences only where the learner must copy or inspect code.
- Ends with a visible check and a next path.

## Cut

- Reference completeness, alternate architectures, and long background.
- Steps that depend on hidden setup.
- Unexplained jumps between files or terminals.

## Skeleton

```markdown
# Tutorial: <outcome>

## Before you start
<starting files, access, commands, and time>

## Build the first visible result
<one action path, one expected output>

## Add the next capability
<one concept, one edit, one verification>

## Verify the whole lesson
<command, artifact, or browser check>

## What to try next
<one or two follow-on paths>
```

## Section prompts

- Name the learner and the artifact they will hold at the end.
- Keep every `h2` short enough to be a single reader section.
- Put commands and code in fenced blocks with filenames above them.
- After each action, state the observable result before moving on.

## Renderer moves

Catalog: ../building-artifacts.md#what-each-file-type-becomes - md doc reader sections; anchored code blocks.