# 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 field (R1).** Build what `R1. The field` asks for, to the numbers in `design.md`. In particular: One password field, a submit control, and a list of the rules that have been revealed so far. Check: the `R1. The field` acceptance checks pass. 3. **Each rule (R2).** Build what `R2. Each rule` asks for, to the numbers in `design.md`. In particular: Every rule has an id, a short statement, and a pure function of the current text (and, where `design.md` says so, of the current date used as a fixture). Check: the `R2. Each rule` acceptance checks pass. 4. **Revealing the next rule (R3).** Build what `R3. Revealing the next rule` asks for, to the numbers in `design.md`. In particular: A rule past the opening set is revealed only when every currently visible rule is satisfied. Check: the `R3. Revealing the next rule` acceptance checks pass. 5. **Messages (R4).** Build what `R4. Messages` asks for, to the numbers in `design.md`. In particular: If `show_why` is on, an unsatisfied visible rule includes its short statement and, after a failed check, a one-line reason from `design.md`. Check: the `R4. Messages` acceptance checks pass. 6. **Files (R5).** Build what `R5. Files` asks for, to the numbers in `design.md`. In particular: One command runs every unit test and a short UI test of the prefix fixture, and writes the screenshots in `design.md`. Check: the `R5. Files` 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.