Durability scores
A score of how long things last, aggregated from fixture reviews, with listing and search tests and a golden product page.
This is a small site 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/durability-scores- Version
- 0.2.1
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/durability-scores/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.Durability scores
What this builds
A listing that scores products on durability, from a fixture set of reviews, not from a live shop or a trademarked review site. Aggregation is documented (a mean, a count, a band). Search and listing are tested. A golden product page is taken. The product does not use another publication's name in its id or its title.
Read
spekkr.inputs.jsonfirst.titlelabels the listing.queryis the first search.corpuschooses the reviews.breakdownandquoteschange the product page.Out of scope
- A live shop, a trademarked review-aggregation name, or a scrape of either in the checks.
- A paid API in the checks.
- A legal warranty claim.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Aggregation and search
- A product's score is the mean of its review scores, rounded to one decimal, and its count is the number of reviews, as in
fixtures/durability-scores.json. - A search for
kettlereturns the documented list in the file's order. - A fetch hook fails if a known shop or review-host is contacted.
Accept when: every listed product's mean and count match, the kettle search matches, and the hook stays quiet.
R2. Frames and files
- Goldens: the default listing, the kettle search, a product page, and a breakdown bar.
- One command runs the aggregates, the search, the hook, and writes the frames. No network.
Accept when: the command passes for both corpora, 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
Score aggregation is tested on fixture reviews (mean, count, bands). Listing and search match documented lists. A golden product page is checked. A fetch hook fails if a live shop or review site is contacted. The product name does not use a trademarked review-site name.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to add a review, how the mean is rounded, and how to run the checks.
# Durability scores ## What this builds A listing that scores products on durability, from a fixture set of reviews, not from a live shop or a trademarked review site. Aggregation is documented (a mean, a count, a band). Search and listing are tested. A golden product page is taken. The product does not use another publication's name in its id or its title. Read `spekkr.inputs.json` first. `title` labels the listing. `query` is the first search. `corpus` chooses the reviews. `breakdown` and `quotes` change the product page. ## Out of scope - A live shop, a trademarked review-aggregation name, or a scrape of either in the checks. - A paid API in the checks. - A legal warranty claim. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Aggregation and search - A product's score is the mean of its review scores, rounded to one decimal, and its count is the number of reviews, as in `fixtures/durability-scores.json`. - A search for `kettle` returns the documented list in the file's order. - A fetch hook fails if a known shop or review-host is contacted. Accept when: every listed product's mean and count match, the kettle search matches, and the hook stays quiet. ### R2. Frames and files - Goldens: the default listing, the kettle search, a product page, and a breakdown bar. - One command runs the aggregates, the search, the hook, and writes the frames. No network. Accept when: the command passes for both corpora, 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 Score aggregation is tested on fixture reviews (mean, count, bands). Listing and search match documented lists. A golden product page is checked. A fetch hook fails if a live shop or review site is contacted. The product name does not use a trademarked review-site name. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to add a review, how the mean is rounded, and how to run the checks.
-
design.mdFixture review aggregation, search, and the product-page golden.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.
Score
Reviews are integers 1–5. The mean is rounded half-up to one decimal. Bands are 1–2, 3, 4–5, as in the breakdown fixture. The files are the authority.
Screenshot tolerance
8 levels, 98% of pixels. On-page scores must also match the file.
Inputs
Key Label Default Notes titleTitle How long does it last? Shown above the listing. queryDefault query kettle Used on first load. breakdownShow a score breakdown on A small bar of review counts per band. quotesShow a short quote on From the fixture reviews. corpusReview corpus sample A shipped set of product reviews. No live shop or review site. 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/durability-scores.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/listing.pngSearch “kettle”, four fixture products with median life and a score. 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.
- Score aggregation is tested on fixture reviews (mean, count, bands). Listing and search match documented lists. A golden product page is checked. A fetch hook fails if a live shop or review site is contacted. The product name does not use a trademarked review-site name.
# 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. ## Score Reviews are integers 1–5. The mean is rounded half-up to one decimal. Bands are 1–2, 3, 4–5, as in the breakdown fixture. The files are the authority. ## Screenshot tolerance 8 levels, 98% of pixels. On-page scores must also match the file. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | How long does it last? | Shown above the listing. | | `query` | Default query | kettle | Used on first load. | | `breakdown` | Show a score breakdown | on | A small bar of review counts per band. | | `quotes` | Show a short quote | on | From the fixture reviews. | | `corpus` | Review corpus | sample | A shipped set of product reviews. No live shop or review site. | ## 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/durability-scores.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/listing.png` | Search “kettle”, four fixture products with median life and a score. | ## 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. Score aggregation is tested on fixture reviews (mean, count, bands). Listing and search match documented lists. A golden product page is checked. A fetch hook fails if a live shop or review site is contacted. The product name does not use a trademarked review-site name.
-
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. - Aggregation and search (R1). Build what
R1. Aggregation and searchasks for, to the numbers indesign.md. In particular: A product's score is the mean of its review scores, rounded to one decimal, and its count is the number of reviews, as infixtures/durability-scores.json. Check: theR1. Aggregation and searchacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the default listing, the kettle search, a product page, and a breakdown bar. 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. **Aggregation and search (R1).** Build what `R1. Aggregation and search` asks for, to the numbers in `design.md`. In particular: A product's score is the mean of its review scores, rounded to one decimal, and its count is the number of reviews, as in `fixtures/durability-scores.json`. Check: the `R1. Aggregation and search` 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: the default listing, the kettle search, a product page, and a breakdown bar. 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/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
- small site
- Platforms
- web
- Tools
- TypeScript
What does it need?
- Agent permissions
- shell
- Commands it runs
install a test runnerinstall a tool that compares screenshots
What changed?
- 0.2.115 Nov 2026Names what it builds.
- 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.