Invented store
A store that invents a product from a search: fixture prompts yield a stub listing and a golden page, with no paid API in CI.
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/invented-store- Version
- 0.2.1
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/invented-store/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.Invented store
What this builds
A shop that, given a search, invents a product listing: a name, a short pitch, a fake price, a picture. In CI the generator is a deterministic stub (or a template), not a paid language-model API. Fixture prompts produce a structured listing that matches a file, and a golden product page is taken. The inventedness is obvious in the copy. Nothing is for sale.
Read
spekkr.inputs.jsonfirst.titleis the store name.queryis the first search.generatorchooses the stub or the template.priceandimagechange the card. No paid API is used in the checks.Out of scope
- A paid language-model API in the checks.
- A real checkout, a real payment, or a scrape of a shop.
- A claim that the product exists.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Fixture prompts
- Each prompt in
fixtures/invented-prompts.jsonproduces a listing with the keysname,pitch,sku, and optionalpriceandimagealt, matching the file (the stub is deterministic). - The default query produces the listing in that file. A fetch hook fails if a known paid model or shop host is contacted.
- The page says the goods are invented, in a documented line of copy.
Accept when: every prompt matches the structured listing, the disclaimer line is present, and the hook stays quiet.
R2. Frames and files
- Goldens: the search box, a listing card, the default product page, and a template-generator page.
- One command runs the prompts, the hook, and writes the frames. No network and no paid API.
Accept when: the command passes for both generators, 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
Fixture prompts produce a structured listing from a deterministic stub or template, matching a file. A golden product page is checked. A fetch hook fails if a paid API or a shop host is contacted. No checkout and no network are required in CI.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how the stub works, how a later model hook could be added, and how to run the checks.
# Invented store ## What this builds A shop that, given a search, invents a product listing: a name, a short pitch, a fake price, a picture. In CI the generator is a deterministic stub (or a template), not a paid language-model API. Fixture prompts produce a structured listing that matches a file, and a golden product page is taken. The inventedness is obvious in the copy. Nothing is for sale. Read `spekkr.inputs.json` first. `title` is the store name. `query` is the first search. `generator` chooses the stub or the template. `price` and `image` change the card. No paid API is used in the checks. ## Out of scope - A paid language-model API in the checks. - A real checkout, a real payment, or a scrape of a shop. - A claim that the product exists. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Fixture prompts - Each prompt in `fixtures/invented-prompts.json` produces a listing with the keys `name`, `pitch`, `sku`, and optional `price` and `image` alt, matching the file (the stub is deterministic). - The default query produces the listing in that file. A fetch hook fails if a known paid model or shop host is contacted. - The page says the goods are invented, in a documented line of copy. Accept when: every prompt matches the structured listing, the disclaimer line is present, and the hook stays quiet. ### R2. Frames and files - Goldens: the search box, a listing card, the default product page, and a template-generator page. - One command runs the prompts, the hook, and writes the frames. No network and no paid API. Accept when: the command passes for both generators, 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 Fixture prompts produce a structured listing from a deterministic stub or template, matching a file. A golden product page is checked. A fetch hook fails if a paid API or a shop host is contacted. No checkout and no network are required in CI. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how the stub works, how a later model hook could be added, and how to run the checks.
-
design.mdThe deterministic stub, fixture prompts, and the no-paid-API rule.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.
Stub
The stub fills a template from the query words, with a sku hashed from the query, and a price from a documented formula if that option is on. The fixture file is the authority for outputs.
Screenshot tolerance
8 levels, 98% of pixels. The name and pitch on the page must also match the file.
Inputs
Key Label Default Notes titleStore name The Invented Goods Co. Shown on the header and the listing. queryDefault query a kettle that whistles in thirds Used on first load. priceShow a made-up price on A price from the stub, clearly marked as invented. imageShow a made-up picture on A generated still from the stub, not a scraped photo. generatorGenerator stub stub is a deterministic local generator used in CI. template is a more fixed layout with slotted words. 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/invented-prompts.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.pngThe Invented Goods Co. listing for a kettle that whistles in thirds. 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.
- Fixture prompts produce a structured listing from a deterministic stub or template, matching a file. A golden product page is checked. A fetch hook fails if a paid API or a shop host is contacted. No checkout and no network are required in CI.
# 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. ## Stub The stub fills a template from the query words, with a sku hashed from the query, and a price from a documented formula if that option is on. The fixture file is the authority for outputs. ## Screenshot tolerance 8 levels, 98% of pixels. The name and pitch on the page must also match the file. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Store name | The Invented Goods Co. | Shown on the header and the listing. | | `query` | Default query | a kettle that whistles in thirds | Used on first load. | | `price` | Show a made-up price | on | A price from the stub, clearly marked as invented. | | `image` | Show a made-up picture | on | A generated still from the stub, not a scraped photo. | | `generator` | Generator | stub | stub is a deterministic local generator used in CI. template is a more fixed layout with slotted words. | ## 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/invented-prompts.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` | The Invented Goods Co. listing for a kettle that whistles in thirds. | ## 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. Fixture prompts produce a structured listing from a deterministic stub or template, matching a file. A golden product page is checked. A fetch hook fails if a paid API or a shop host is contacted. No checkout and no network are required in CI.
-
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. - Fixture prompts (R1). Build what
R1. Fixture promptsasks for, to the numbers indesign.md. In particular: Each prompt infixtures/invented-prompts.jsonproduces a listing with the keysname,pitch,sku, and optionalpriceandimagealt, matching the file (the stub is deterministic). Check: theR1. Fixture promptsacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the search box, a listing card, the default product page, and a template-generator page. 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. **Fixture prompts (R1).** Build what `R1. Fixture prompts` asks for, to the numbers in `design.md`. In particular: Each prompt in `fixtures/invented-prompts.json` produces a listing with the keys `name`, `pitch`, `sku`, and optional `price` and `image` alt, matching the file (the stub is deterministic). Check: the `R1. Fixture prompts` 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 search box, a listing card, the default product page, and a template-generator page. 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.