Cursed font

A generator of typographic crimes: exported fonts parse, named glyphs match fixture metrics or outlines, and a preview is goldened.

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/cursed-font
Version
0.2.2
Published by
lume
Updated
15 Nov 2026

Build this spec

Build the spec at https://spekkr.com/lume/cursed-font/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?

Cursed font: heroCursed font: loop

What can I customize?

Crime The typographic crime applied to a regular starting outline.

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.md Requirements and acceptance checks.

    Cursed font

    What this builds

    A small type workshop that starts from a shipped, original, permissively licensed outline and applies a documented typographic crime: an i that is too narrow, a comma that is too tall, a pair of letters that look like another letter. The result can be previewed and downloaded as a font file. Exported fonts must parse. Named glyphs must match fixture outlines or metrics. This is not someone else's font, and it is not a piracy tool.

    Read spekkr.inputs.json first. title labels the preview. family_name is written into the font. crime chooses the transform. lowercase and kerning change the exported set.

    Out of scope

    • A full professional font editor.
    • Copying or ripping a commercial typeface.
    • Network or a marketplace of fonts in the checks.

    Requirements

    Each requirement has an id. Checks name the id they cover.

    R1. Export and parse
    • The export is a valid OpenType or TrueType file, as chosen by the build (one format is enough). A parser reads the family name as family_name.
    • Glyphs A–Z (and a–z if lowercase is on) exist. Metrics for a listed set match fixtures/font-metrics.json within 1 unit.
    • The crime narrow-i makes the i (and I) advance width the documented fraction of a regular n.

    Accept when: the file parses, the family name matches, the metrics match, and the narrow-i fraction holds.

    R2. Outlines and preview
    • For each crime, a glyph listed in fixtures/font-outlines.json matches the fixture outline within 0.5 units at a set of sample points, or a hashed path matches the file.
    • A preview of The rain in millstead at 72 px, seed ignored, matches the preview golden.
    • If kerning is on, the pair list in the file is present in the font.

    Accept when: outlines or hashes match, the kern pairs are present when on, and the preview matches the golden.

    R3. Files
    • One command builds three fonts (one per crime), parses them, checks metrics, and writes the four screenshots. No network.

    Accept when: the command passes with lowercase on and off.

    R4. 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.

    Verification

    Exported fonts parse, the family name is written, and named glyphs match fixture metrics (and outlines or path hashes). A preview screenshot is checked. The starting outlines are original and licensed. No commercial font is ripped. 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 export, how the starting outlines are licensed, and how to run the checks.
    # Cursed font
    
    ## What this builds
    
    A small type workshop that starts from a shipped, original, permissively
    licensed outline and applies a documented typographic crime: an i that is
    too narrow, a comma that is too tall, a pair of letters that look like
    another letter. The result can be previewed and downloaded as a font file.
    Exported fonts must parse. Named glyphs must match fixture outlines or
    metrics. This is not someone else's font, and it is not a piracy tool.
    
    Read `spekkr.inputs.json` first. `title` labels the preview. `family_name`
    is written into the font. `crime` chooses the transform. `lowercase` and
    `kerning` change the exported set.
    
    ## Out of scope
    
    - A full professional font editor.
    - Copying or ripping a commercial typeface.
    - Network or a marketplace of fonts in the checks.
    
    ## Requirements
    
    Each requirement has an id. Checks name the id they cover.
    
    ### R1. Export and parse
    
    - The export is a valid OpenType or TrueType file, as chosen by the build
      (one format is enough). A parser reads the family name as `family_name`.
    - Glyphs A–Z (and a–z if `lowercase` is on) exist. Metrics for a listed
      set match `fixtures/font-metrics.json` within 1 unit.
    - The crime `narrow-i` makes the i (and I) advance width the documented
      fraction of a regular n.
    
    Accept when: the file parses, the family name matches, the metrics match,
    and the narrow-i fraction holds.
    
    ### R2. Outlines and preview
    
    - For each crime, a glyph listed in `fixtures/font-outlines.json` matches
      the fixture outline within 0.5 units at a set of sample points, or a
      hashed path matches the file.
    - A preview of `The rain in millstead` at 72 px, seed ignored, matches the
      `preview` golden.
    - If `kerning` is on, the pair list in the file is present in the font.
    
    Accept when: outlines or hashes match, the kern pairs are present when on,
    and the preview matches the golden.
    
    ### R3. Files
    
    - One command builds three fonts (one per crime), parses them, checks
      metrics, and writes the four screenshots. No network.
    
    Accept when: the command passes with lowercase on and off.
    
    ### R4. 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.
    
    ## Verification
    
    Exported fonts parse, the family name is written, and named glyphs match
    fixture metrics (and outlines or path hashes). A preview screenshot is
    checked. The starting outlines are original and licensed. No commercial
    font is ripped. 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 export, how the starting outlines are licensed, and
      how to run the checks.
    

    Open spec.md as plain text

  • design.md Crimes, metrics, outlines, and the preview text.

    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.

    Starting outlines

    A shipped original source, licensed in LICENCE.md. Crimes are deterministic functions of those outlines, described in fixtures/font-crimes.json.

    Screenshot tolerance

    8 levels, 98% of pixels. Metrics are exact to 1 font unit.

    Inputs

    KeyLabelDefaultNotes
    titleTitleA slightly wrong typefaceShown above the preview.
    family_nameFamily nameSlightlyWrongThe name written into the exported font.
    lowercaseInclude lowercaseonIf off, only A–Z, 0–9 and basic punctuation are exported.
    kerningInclude a few kern pairsonA small shipped list, not a full kerning class system.
    crimeCrimenarrow-iThe typographic crime applied to a regular starting outline.

    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.

    FixtureRole
    LICENCE.mdA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/font-crimes.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/font-metrics.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    fixtures/font-outlines.jsonA shipped fixture. The build may move it, but then design.md must name the new path.
    spekkr.inputs.jsonA 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.

    FileWhat it shows
    shots/specimen.pngSlightlyWrong, a specimen and a glyph set with fixture metrics.

    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. Exported fonts parse, the family name is written, and named glyphs match fixture metrics (and outlines or path hashes). A preview screenshot is checked. The starting outlines are original and licensed. No commercial font is ripped. 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.
    
    ## Starting outlines
    
    A shipped original source, licensed in `LICENCE.md`. Crimes are
    deterministic functions of those outlines, described in
    `fixtures/font-crimes.json`.
    
    ## Screenshot tolerance
    
    8 levels, 98% of pixels. Metrics are exact to 1 font unit.
    
    ## Inputs
    
    | Key | Label | Default | Notes |
    | --- | --- | --- | --- |
    | `title` | Title | A slightly wrong typeface | Shown above the preview. |
    | `family_name` | Family name | SlightlyWrong | The name written into the exported font. |
    | `lowercase` | Include lowercase | on | If off, only A–Z, 0–9 and basic punctuation are exported. |
    | `kerning` | Include a few kern pairs | on | A small shipped list, not a full kerning class system. |
    | `crime` | Crime | narrow-i | The typographic crime applied to a regular starting outline. |
    
    ## 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 |
    | --- | --- |
    | `LICENCE.md` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/font-crimes.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/font-metrics.json` | A shipped fixture. The build may move it, but then `design.md` must name the new path. |
    | `fixtures/font-outlines.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/specimen.png` | SlightlyWrong, a specimen and a glyph set with fixture metrics. |
    
    
    ## 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. Exported fonts parse, the family name is written, and named glyphs
    match fixture metrics (and outlines or path hashes). A preview screenshot
    is checked. The starting outlines are original and licensed. No commercial
    font is ripped. No network.
    

    Open design.md as plain text

  • tasks.md Build tasks in order, each with a check.

    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. Export and parse (R1). Build what R1. Export and parse asks for, to the numbers in design.md. In particular: The export is a valid OpenType or TrueType file, as chosen by the build (one format is enough). A parser reads the family name as family_name. Check: the R1. Export and parse acceptance checks pass.
    3. Outlines and preview (R2). Build what R2. Outlines and preview asks for, to the numbers in design.md. In particular: For each crime, a glyph listed in fixtures/font-outlines.json matches the fixture outline within 0.5 units at a set of sample points, or a hashed path matches the file. Check: the R2. Outlines and preview acceptance checks pass.
    4. Files (R3). Build what R3. Files asks for, to the numbers in design.md. In particular: One command builds three fonts (one per crime), parses them, checks metrics, and writes the four screenshots. No network. Check: the R3. Files acceptance checks pass.
    5. Inputs (R4). Build what R4. 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 R4. Inputs 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.
    # 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. **Export and parse (R1).** Build what `R1. Export and parse` asks for,
    to the numbers in `design.md`. In particular: The export is a valid
    OpenType or TrueType file, as chosen by the build (one format is enough).
    A parser reads the family name as `family_name`.
       Check: the `R1. Export and parse` acceptance checks pass.
    
    3. **Outlines and preview (R2).** Build what `R2. Outlines and preview`
    asks for, to the numbers in `design.md`. In particular: For each crime, a
    glyph listed in `fixtures/font-outlines.json` matches the fixture outline
    within 0.5 units at a set of sample points, or a hashed path matches the
    file.
       Check: the `R2. Outlines and preview` acceptance checks pass.
    
    4. **Files (R3).** Build what `R3. Files` asks for, to the numbers in
    `design.md`. In particular: One command builds three fonts (one per
    crime), parses them, checks metrics, and writes the four screenshots. No
    network.
       Check: the `R3. Files` acceptance checks pass.
    
    5. **Inputs (R4).** Build what `R4. 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 `R4. Inputs` 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.
    

    Open tasks.md as plain text

  • reference/preview.html A 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.css Webfont faces for the reference preview.
  • reference/fonts/Geist.ttf Geist variable typeface for the reference preview.
  • reference/fonts/Fraunces.ttf Fraunces variable typeface for the reference preview.
  • reference/fonts/Fraunces-Italic.ttf Fraunces italic variable typeface for the reference preview.

Is it for me?

Platforms
web
Tools
TypeScript

What does it need?

Agent permissions
shell
Commands it runs
install a test runner install a font parser install 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.