# Tasks Work in order. Finish a task's check before starting the next. 1. **Set up.** Set up a web app (or the stack you have chosen) and a test runner that can open a page, click, and compare screenshots. Read `spekkr.inputs.json` first. Check: a blank or heading page loads, and an empty test run passes. 2. **Tiles and places (R1).** Build what `R1. Tiles and places` asks for, to the numbers in `design.md`. In particular: Each city is a folder of tiles and a `places.json` of named points in tile coordinates. Check: the `R1. Tiles and places` acceptance checks pass. 3. **Distance and score (R2).** Build what `R2. Distance and score` asks for, to the numbers in `design.md`. In particular: Distance is Euclidean in metres, from the tileset's stated metres-per-pixel. Check: the `R2. Distance and score` acceptance checks pass. 4. **A golden round (R3).** Build what `R3. A golden round` asks for, to the numbers in `design.md`. In particular: Round 1 of seed 3, millstead, with the fixture guess, is screenshotted at the clue, after the pin, after the reveal, and on the final score card after five rounds of the fixture tape. Check: the `R3. A golden round` acceptance checks pass. 5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in `design.md`. In particular: One command runs the seed, fetch-hook, distance, and tape tests, and writes the screenshots. No network. Check: the `R4. Files` acceptance checks pass. 6. **Inputs (R5).** Build what `R5. Inputs` asks for, to the numbers in `design.md`. In particular: The build reads `spekkr.inputs.json`. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: the `R5. Inputs` acceptance checks pass. 7. **Goldens.** Capture the frames named in `design.md` at the defaults, with motion frozen where the file says so. Compare them within the stated tolerance. Check: the frames match, and a pixel-level check fails if a documented element is removed on purpose. 8. **Finish.** Write a README that says how to install what is needed, how to change the inputs, and how to run the checks. Run the one command from a clean folder. Check: every item under Definition of done in `spec.md` is true.