Week, huh
A wry week calendar: frozen dates render the documented weekday and caption, with a golden image.
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/week-huh- Version
- 0.2.1
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/week-huh/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.Week, huh
What this builds
A one-week calendar with a dry caption, as if the week itself were a character. The date is injectable, so tests freeze it. A frozen date must render the documented weekday and caption. A golden image is taken. The captions are original. This is a calendar toy, not a scheduler.
Read
spekkr.inputs.jsonfirst.titleis above the week.dateis the frozen day (the week is the one containing it, starting Monday).voicechooses the caption table.captionandweekendchange the chrome.Out of scope
- A live holiday API or a personal calendar account.
- Network in the checks.
- A booking or a reminder service.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Frozen dates
2026-01-15is a Thursday. The week is Monday 12 to Sunday 18 January- The weekday labels match that.
- The caption for that Thursday,
dryvoice, is the exact string infixtures/captions-dry.json. A second date in the file (a Saturday) matches too. - The week starts on Monday, not Sunday, in this version.
Accept when: both fixture dates show the documented weekday and caption, and the week bounds match.
R2. Frames and files
- Goldens: the week of 2026-01-15, a close caption, a weekend mark, and another fixture date.
- One command runs the date table and writes the frames. No network. The clock is the frozen date, not wall time.
Accept when: the command passes for both voices, 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
Frozen dates render the documented weekday and caption, including a mid-week day and a weekend day. A golden image is taken. The date is injected, not wall-clock today. No network and no personal calendar.
Definition of done
- Every acceptance check above runs from one command, and all pass at the person's inputs.
- A README says how to pin a date, how to edit a caption, and how to run the checks.
# Week, huh ## What this builds A one-week calendar with a dry caption, as if the week itself were a character. The date is injectable, so tests freeze it. A frozen date must render the documented weekday and caption. A golden image is taken. The captions are original. This is a calendar toy, not a scheduler. Read `spekkr.inputs.json` first. `title` is above the week. `date` is the frozen day (the week is the one containing it, starting Monday). `voice` chooses the caption table. `caption` and `weekend` change the chrome. ## Out of scope - A live holiday API or a personal calendar account. - Network in the checks. - A booking or a reminder service. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Frozen dates - `2026-01-15` is a Thursday. The week is Monday 12 to Sunday 18 January 2026. The weekday labels match that. - The caption for that Thursday, `dry` voice, is the exact string in `fixtures/captions-dry.json`. A second date in the file (a Saturday) matches too. - The week starts on Monday, not Sunday, in this version. Accept when: both fixture dates show the documented weekday and caption, and the week bounds match. ### R2. Frames and files - Goldens: the week of 2026-01-15, a close caption, a weekend mark, and another fixture date. - One command runs the date table and writes the frames. No network. The clock is the frozen date, not wall time. Accept when: the command passes for both voices, 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 Frozen dates render the documented weekday and caption, including a mid-week day and a weekend day. A golden image is taken. The date is injected, not wall-clock today. No network and no personal calendar. ## Definition of done - Every acceptance check above runs from one command, and all pass at the person's inputs. - A README says how to pin a date, how to edit a caption, and how to run the checks.
-
design.mdFrozen dates, weekday captions, and the week grid.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.
Captions
Each voice is a table of weekday captions, plus an optional map of special dates. The files are the authority. 2026-01-15 is Thursday, week of 12–18 January 2026.
Screenshot tolerance
8 levels, 98% of pixels. Caption text must also match exactly.
Inputs
Key Label Default Notes titleTitle What a week, huh? Shown above the week. dateFrozen date 2026-01-15 A calendar date. Checks use this, never wall-clock today alone. captionShow a caption on A short line from the caption table for that weekday or date. weekendMark the weekend on A different wash on Saturday and Sunday. voiceCaption voice dry Two shipped caption tables. 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/captions-dry.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/week.pngThe week of 15 January 2026, Thursday captioned “What a week, huh?” 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.
- Frozen dates render the documented weekday and caption, including a mid-week day and a weekend day. A golden image is taken. The date is injected, not wall-clock today. No network and no personal calendar.
# 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. ## Captions Each voice is a table of weekday captions, plus an optional map of special dates. The files are the authority. 2026-01-15 is Thursday, week of 12–18 January 2026. ## Screenshot tolerance 8 levels, 98% of pixels. Caption text must also match exactly. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | What a week, huh? | Shown above the week. | | `date` | Frozen date | 2026-01-15 | A calendar date. Checks use this, never wall-clock today alone. | | `caption` | Show a caption | on | A short line from the caption table for that weekday or date. | | `weekend` | Mark the weekend | on | A different wash on Saturday and Sunday. | | `voice` | Caption voice | dry | Two shipped caption tables. | ## 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/captions-dry.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/week.png` | The week of 15 January 2026, Thursday captioned “What a week, huh?” | ## 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. Frozen dates render the documented weekday and caption, including a mid-week day and a weekend day. A golden image is taken. The date is injected, not wall-clock today. No network and no personal calendar.
-
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. - Frozen dates (R1). Build what
R1. Frozen datesasks for, to the numbers indesign.md. In particular:2026-01-15is a Thursday. The week is Monday 12 to Sunday 18 January 2026. The weekday labels match that. Check: theR1. Frozen datesacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: the week of 2026-01-15, a close caption, a weekend mark, and another fixture date. 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. **Frozen dates (R1).** Build what `R1. Frozen dates` asks for, to the numbers in `design.md`. In particular: `2026-01-15` is a Thursday. The week is Monday 12 to Sunday 18 January 2026. The weekday labels match that. Check: the `R1. Frozen dates` 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 week of 2026-01-15, a close caption, a weekend mark, and another fixture date. 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/Newsreader.ttfNewsreader variable typeface for the reference preview. -
reference/fonts/Newsreader-Italic.ttfNewsreader 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.