Timezone meet
A meeting-time comparer with conversion tests around DST fixtures, and a golden comparison view.
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/timezone-meet- Version
- 0.2.1
- Published by
- lume
- Updated
- 15 Nov 2026
Build this spec
Build the spec at https://spekkr.com/lume/timezone-meet/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.Timezone meet
What this builds
A table that compares a proposed meeting time across a few time zones. Conversions use a shipped timezone database (or the platform's, pinned in tests) and are checked against DST fixtures, not against a live 'now' alone. A golden comparison view is taken. This is a meeting helper, not a calendar product.
Read
spekkr.inputs.jsonfirst.titlelabels the table.homeis the first zone.zoneschooses the list.weekanddst_notechange the view. The proposed instant is an input on the page; tests inject it.Out of scope
- A live calendar or a mail-merge into a real invite, in this version.
- Network or an account.
- A claim of legal working-hours advice.
Requirements
Each requirement has an id. Checks name the id they cover.
R1. Conversions and DST
- The fixture instants in
fixtures/tz-cases.json(including at least one spring-forward and one fall-back in a listed zone) convert to the documented local times and offsets in every listed zone. - A proposed time of
2026-03-08T12:00:00Z(or the file's spring case) shows the DST mark on the zone that changes that week, ifdst_noteis on. - An invalid IANA name in
homeis refused before the table renders.
Accept when: every conversion case matches, the DST mark appears on the listed day, and a bad home zone is refused.
R2. Frames and files
- Goldens: a day table, a week grid, a DST mark, and a suggested overlap (a highlighted hour that is inside a documented 09:00–18:00 local window in every zone, if one exists; otherwise a 'no overlap' state).
- One command runs the cases, the mark, the refusal, and writes the frames. No network. The clock is the fixture instant, not wall time.
Accept when: the command passes for both zone sets, 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
Conversion tests cover DST fixtures (spring-forward, fall-back, and a no-DST zone) against a file of civil times and offsets. A golden comparison view is taken. The proposed instant is injected, not wall-clock 'now'. No network and no calendar account.
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 zone, how to pin an instant, and how to run the checks.
# Timezone meet ## What this builds A table that compares a proposed meeting time across a few time zones. Conversions use a shipped timezone database (or the platform's, pinned in tests) and are checked against DST fixtures, not against a live 'now' alone. A golden comparison view is taken. This is a meeting helper, not a calendar product. Read `spekkr.inputs.json` first. `title` labels the table. `home` is the first zone. `zones` chooses the list. `week` and `dst_note` change the view. The proposed instant is an input on the page; tests inject it. ## Out of scope - A live calendar or a mail-merge into a real invite, in this version. - Network or an account. - A claim of legal working-hours advice. ## Requirements Each requirement has an id. Checks name the id they cover. ### R1. Conversions and DST - The fixture instants in `fixtures/tz-cases.json` (including at least one spring-forward and one fall-back in a listed zone) convert to the documented local times and offsets in every listed zone. - A proposed time of `2026-03-08T12:00:00Z` (or the file's spring case) shows the DST mark on the zone that changes that week, if `dst_note` is on. - An invalid IANA name in `home` is refused before the table renders. Accept when: every conversion case matches, the DST mark appears on the listed day, and a bad home zone is refused. ### R2. Frames and files - Goldens: a day table, a week grid, a DST mark, and a suggested overlap (a highlighted hour that is inside a documented 09:00–18:00 local window in every zone, if one exists; otherwise a 'no overlap' state). - One command runs the cases, the mark, the refusal, and writes the frames. No network. The clock is the fixture instant, not wall time. Accept when: the command passes for both zone sets, 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 Conversion tests cover DST fixtures (spring-forward, fall-back, and a no-DST zone) against a file of civil times and offsets. A golden comparison view is taken. The proposed instant is injected, not wall-clock 'now'. No network and no calendar account. ## 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 zone, how to pin an instant, and how to run the checks.
-
design.mdDST conversion fixtures, the home zone, and the comparison 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.
Cases
The file lists UTC instants, IANA zones, and expected civil times plus offsets. It includes Asia/Calcutta (no DST), a zone with a spring-forward in March 2026, and a zone with a fall-back in 2025 or 2026, as dated in the file.
Screenshot tolerance
8 levels, 98% of pixels. On-screen times must also match the file exactly.
Inputs
Key Label Default Notes titleTitle When can we talk? Shown above the table. homeHome zone Asia/Calcutta An IANA name. Used as the first column. dst_noteNote a DST change on A mark on a day when a zone's offset changes in the range. weekShow a week grid on Otherwise a single-day table. zonesZone set work work is a shipped list of a few IANA zones. tiny is two, for quicker checks. 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/tz-cases.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/grid.pngAda in Asia/Calcutta compared with London and New York, DST fixture applied. 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.
- Conversion tests cover DST fixtures (spring-forward, fall-back, and a no-DST zone) against a file of civil times and offsets. A golden comparison view is taken. The proposed instant is injected, not wall-clock 'now'. No network and no calendar account.
# 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. ## Cases The file lists UTC instants, IANA zones, and expected civil times plus offsets. It includes Asia/Calcutta (no DST), a zone with a spring-forward in March 2026, and a zone with a fall-back in 2025 or 2026, as dated in the file. ## Screenshot tolerance 8 levels, 98% of pixels. On-screen times must also match the file exactly. ## Inputs | Key | Label | Default | Notes | | --- | --- | --- | --- | | `title` | Title | When can we talk? | Shown above the table. | | `home` | Home zone | Asia/Calcutta | An IANA name. Used as the first column. | | `dst_note` | Note a DST change | on | A mark on a day when a zone's offset changes in the range. | | `week` | Show a week grid | on | Otherwise a single-day table. | | `zones` | Zone set | work | work is a shipped list of a few IANA zones. tiny is two, for quicker checks. | ## 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/tz-cases.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/grid.png` | Ada in Asia/Calcutta compared with London and New York, DST fixture applied. | ## 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. Conversion tests cover DST fixtures (spring-forward, fall-back, and a no-DST zone) against a file of civil times and offsets. A golden comparison view is taken. The proposed instant is injected, not wall-clock 'now'. No network and no calendar account.
-
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. - Conversions and DST (R1). Build what
R1. Conversions and DSTasks for, to the numbers indesign.md. In particular: The fixture instants infixtures/tz-cases.json(including at least one spring-forward and one fall-back in a listed zone) convert to the documented local times and offsets in every listed zone. Check: theR1. Conversions and DSTacceptance checks pass. - Frames and files (R2). Build what
R2. Frames and filesasks for, to the numbers indesign.md. In particular: Goldens: a day table, a week grid, a DST mark, and a suggested overlap (a highlighted hour that is inside a documented 09:00–18:00 local window in every zone, if one exists; otherwise a 'no overlap' state). 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. **Conversions and DST (R1).** Build what `R1. Conversions and DST` asks for, to the numbers in `design.md`. In particular: The fixture instants in `fixtures/tz-cases.json` (including at least one spring-forward and one fall-back in a listed zone) convert to the documented local times and offsets in every listed zone. Check: the `R1. Conversions and DST` 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: a day table, a week grid, a DST mark, and a suggested overlap (a highlighted hour that is inside a documented 09:00–18:00 local window in every zone, if one exists; otherwise a 'no overlap' state). 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.