# 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. **The page (R1).** Build what `R1. The page` asks for, to the numbers in `design.md`. In particular: The file is a valid PDF. Opening it shows one page with the well, the title, a score, and the controls. Check: the `R1. The page` acceptance checks pass. 3. **Pieces (R2).** Build what `R2. Pieces` asks for, to the numbers in `design.md`. In particular: The `seven` set has the seven shapes in `design.md`, each a set of four cells. The `five` set is the first five of those. Check: the `R2. Pieces` acceptance checks pass. 4. **A driven game (R3).** Build what `R3. A driven game` asks for, to the numbers in `design.md`. In particular: The driver can start a game with the seed in `design.md`, spawn a documented first piece, slide it, rotate it, and hard-drop it. Check: the `R3. A driven game` acceptance checks pass. 5. **Screenshots and files (R4).** Build what `R4. Screenshots and files` asks for, to the numbers in `design.md`. In particular: Frames are rendered from the PDF or from the same renderer: first-page at spawn, piece-falling mid-drop, line-clear on the flash frame, after-lock after the clear. Check: the `R4. Screenshots and 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.