# 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. **Lists and colouring (R1).** Build what `R1. Lists and colouring` asks for, to the numbers in `design.md`. In particular: Guesses must be in the chosen list, five letters, A–Z, case-insensitive, stored uppercase. Check: the `R1. Lists and colouring` acceptance checks pass. 3. **The anti-word aim (R2).** Build what `R2. The anti-word aim` asks for, to the numbers in `design.md`. In particular: A guess that is the secret ends the run as a 'caught' result, with the number of guesses made. Check: the `R2. The anti-word aim` acceptance checks pass. 4. **Share text (R3).** Build what `R3. Share text` asks for, to the numbers in `design.md`. In particular: A finished run produces a five-line share card: title, day, result (`lasted 11` or `caught in 3`), and a row of colour marks per guess using the characters in `design.md`. Check: the `R3. Share text` acceptance checks pass. 5. **Files (R4).** Build what `R4. Files` asks for, to the numbers in `design.md`. In particular: One command runs colouring, dictionary, fixture-day, and share-text tests, and writes the four screenshots. The clock is injected. 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.