Design in minutes
An interactive lesson that restyles a page as you read, with each step applying documented CSS and goldens at start, mid and end.
This is a creative tool spec on Spekkr, published by lume. It is listed with the other specs. Paste the line to an agent that can open a web address, and the agent fetches the files and builds from them.
- Spec
lume/design-in-minutes- Version
- 0.2.2
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/design-in-minutes/start.md.
Paste this to your AI agent. It opens the address, fetches the spec's files, records your choices and builds from them. Nothing to install, no account.
Published by lume.
What does the result look like?
What can I customize?
Your choices go into the line you copy. Anything else is yours to edit, but it leaves the tested path.
What do I get?
-
spec.mdRequirements and acceptance checks.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.jsonfirst.titleis the lesson heading.page_nameis the sample h1.lessonchooses the step list.notesandresetchange 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.jsonfor 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.
# 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.
-
design.mdLesson steps, computed-style fixtures, and the three-plus-one goldens.Design
This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold.
Lesson
lessons/type-and-colour.jsonlists the steps. The style fixtures are the authority for computed colour, font-size, and spacing ofh1,body,.hero, and.price.Screenshot tolerance
8 levels, 98% of pixels.
Inputs
Key Label Default Notes titleLesson title Four minutes on a page Shown at the start. page_nameThe page's heading The Harbour Cafe The sample page's h1. notesShow a teacher note on A short aside next to each step. resetA reset control on Returns the page to step 0. lessonLesson type-and-colour type-and-colour is the full set of steps. short is the first four. Acceptance at the defaults
The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins.
Fixture Role fixtures/lesson-styles.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.lessons/type-and-colour.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.spekkr.inputs.jsonA shipped fixture. The build may move it, but then design.mdmust name the new path.Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy.
Screenshots
These pictures are headless-Chrome captures of the working reference in
reference/preview.html, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel.File What it shows shots/lesson.pngStep two of the lesson, restyling The Harbour Cafe as you read. How to verify
- Run the checks at the default inputs, without a network.
- Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file.
- Repeat once at the person's inputs when they differ from the defaults.
- 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.
# Design This file fixes the parts that are easy to get wrong. The language and tools are up to you, as long as the numbers here hold. ## Lesson `lessons/type-and-colour.json` lists the steps. The style fixtures are the authority for computed colour, font-size, and spacing of `h1`, `body`, `.hero`, and `.price`. ## Screenshot tolerance 8 levels, 98% of pixels. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Lesson title | Four minutes on a page | Shown at the start. | | `page_name` | The page's heading | The Harbour Cafe | The sample page's h1. | | `notes` | Show a teacher note | on | A short aside next to each step. | | `reset` | A reset control | on | Returns the page to step 0. | | `lesson` | Lesson | type-and-colour | type-and-colour is the full set of steps. short is the first four. | ## Acceptance at the defaults The numbers, names and fixture paths already in this file are the authority. Where a later table or a shipped fixture file disagrees with prose, the table or the fixture wins. | Fixture | Role | | --- | --- | | `fixtures/lesson-styles.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `lessons/type-and-colour.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | | `spekkr.inputs.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. | Golden frames are compared at 1400 by 1000 CSS pixels unless a requirement names another size. Tolerance, unless a tighter figure is given above: 8 levels, 98% of pixels, with motion, cursors and clocks frozen as this file says. A build's goldens are of that build; they do not have to match a shipped reference preview pixel-for-pixel if the tool or the type is different, but they do have to match this file's layout, counts and copy. ## Screenshots These pictures are headless-Chrome captures of the working reference in `reference/preview.html`, at the default inputs. They are not drawings of a product that has not been built. The first picture is the one Spekkr shows on the spec's card. A build may ship its own goldens; those goldens are of that build and do not have to match these frames pixel-for-pixel. | File | What it shows | | --- | --- | | `shots/lesson.png` | Step two of the lesson, restyling The Harbour Cafe as you read. | ## How to verify 1. Run the checks at the default inputs, without a network. 2. Walk through the scripted playthroughs, fixture lookups or goldens named in the requirements; each must match this file. 3. Repeat once at the person's inputs when they differ from the defaults. 4. 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.
-
tasks.mdBuild tasks in order, each with a check.Tasks
Work in order. Finish a task's check before starting the next.
- 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.jsonfirst. Check: a blank or heading page loads, and an empty test run passes. - Steps and CSS (R1). Build what
R1. Steps and CSSasks for, to the numbers indesign.md. In particular: Each step has an id, a short text, and a CSS fragment. Applying steps 0..n in order produces the computed styles infixtures/lesson-styles.jsonfor listed selectors. Check: theR1. Steps and CSSacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens at start, midpoint, end, and the midpoint with notes on. Check: theR2. Frames and filesacceptance checks pass. - Inputs (R3). Build what
R3. Inputsasks for, to the numbers indesign.md. In particular: The build readsspekkr.inputs.json. Settings label the UI, options turn features on or off, and a swap must be one of its choices. Check: theR3. Inputsacceptance checks pass. - Checks and report (R4). Build what
R4. Checks and reportasks for, to the numbers indesign.md. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: theR4. Checks and reportacceptance checks pass. - Goldens. Capture the frames named in
design.mdat 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. - 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.mdis true.
# 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. **Steps and CSS (R1).** Build what `R1. Steps and CSS` asks for, to the numbers in `design.md`. In particular: 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. Check: the `R1. Steps and CSS` acceptance checks pass. 3. **Frames and files (R2).** Build what `R2. Frames and files` asks for, to the numbers in `design.md`. In particular: Goldens at start, midpoint, end, and the midpoint with notes on. Check: the `R2. Frames and files` acceptance checks pass. 4. **Inputs (R3).** Build what `R3. 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 `R3. Inputs` acceptance checks pass. 5. **Checks and report (R4).** Build what `R4. Checks and report` asks for, to the numbers in `design.md`. In particular: One command runs every acceptance check at the defaults and at the person's inputs, including golden frames where a requirement asks for them. Check: the `R4. Checks and report` acceptance checks pass. 6. **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. 7. **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.
- 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
-
reference/preview.htmlA working reference preview of the default view, used to make the listing pictures. A build does not have to start from this file. -
reference/fonts/fonts.cssWebfont faces for the reference preview. -
reference/fonts/Geist.ttfGeist variable typeface for the reference preview. -
reference/fonts/GeistMono.ttfGeist Mono variable typeface for the reference preview. -
reference/fonts/Newsreader.ttfNewsreader variable typeface for the reference preview. -
reference/fonts/Newsreader-Italic.ttfNewsreader italic variable typeface for the reference preview. -
reference/fonts/Fraunces.ttfFraunces variable typeface for the reference preview. -
reference/fonts/Fraunces-Italic.ttfFraunces italic variable typeface for the reference preview.
Is it for me?
- Kind
- creative tool
- Platforms
- web
- Tools
- HTML, CSS
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshots
What changed?
- 0.2.215 Nov 2026Names what it builds.
- 0.2.114 Nov 2026Add animated loop to the listing shots.
- 0.2.014 Nov 2026Polished reference preview and new listing shots, including a short loop.
- 0.1.014 Nov 2026First version.
For agents: start.md says how to build this spec, spec.json holds everything on this page, and bundle.tar.gz holds its files.