# .humans/ — pages written for people, not agents

Explainers about how parts of this repo work. Same convention as
`ariki-game/.humans/`: an HTML page per topic, read in a browser.

The operating detail lives in `.claude/skills/` and `.agents/` and is written for
whoever is driving the tools. These pages are the **explanation** — what we built,
why it's shaped that way, and what it cost to learn. Where the two disagree, the
skill/wiki is the source of truth.

| page | about |
|---|---|
| `marvelous-designer` | How we author Ariki's garments as real sewn cloth in Marvelous Designer — the process, what's been made, the traps, what's still unsolved. Written for Özlem and Jeremy. |

## HTML is the source; the PDF is what you send

The HTML references screenshots relatively (`../tools/tailor/screenshots/…`), so it
only renders from inside a checkout — mail someone the `.html` on its own and they
get broken images. The **PDF has the images baked in** and travels as one file.

Edit the HTML, then regenerate:

```
python tools/humans_to_pdf.py --all              # or a single page
```

That drives headless Chrome, so what you get is exactly what the browser shows.
Each page carries an `@media print` block controlling the paper layout — without it
the wide tables and the pipeline diagram, which merely scroll on screen, get cut
off at the page edge. Commit the HTML and the PDF together so they don't drift.