# Design in minutes ## What this builds A short lesson. On the left, a page. On the right, steps of writing. Each step adds or changes documented CSS on the page, live. The sample page and the lesson text are original. Tests assert that each step applies the documented CSS, and they take screenshots at the start, a midpoint, and the end. Read `spekkr.inputs.json` first. `title` is the lesson heading. `page_name` is the sample h1. `lesson` chooses the step list. `notes` and `reset` change the chrome. ## Out of scope - A general CSS course or a video. - Network or a paid lesson catalogue. - A live edit of the person's own site in this version. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Steps and CSS - Each step has an id, a short text, and a CSS fragment. Applying steps 0..n in order produces the computed styles in `fixtures/lesson-styles.json` for listed selectors. - The midpoint is step 4 of `type-and-colour`. The end is the last step. - A reset, if on, returns computed styles to step 0. Accept when: every listed selector at steps 0, 4, and the end matches the file, and reset returns to step 0. ### R2. Frames and files - Goldens at start, midpoint, end, and the midpoint with notes on. - One command applies the steps, checks the styles, and writes the frames. No network. Accept when: the command passes for both lessons, and the frames match the goldens. ### R3. Inputs - 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. - A value outside a stated range, or a swap that is not one of its choices, is refused before the app starts its checks, with a message that names the key. Accept when: the default inputs render, an illegal swap is refused by name, and changing a visible setting (for example the title) shows up in a later check. ### R4. Checks and report - One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. - Checks do not need a network, a paid API, or physical hardware. Accept when: the command passes at the defaults, and a deliberately broken fixture or a wrong price fails it. ## Verification Each lesson step applies documented CSS, checked as computed styles for listed selectors. Screenshots are taken at the start, a midpoint, and the end. A reset returns to step 0. No network. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to walk the lesson, how to add a step, and how to run the checks.