For Kiroween 2026 — AWS's spooky-season hackathon — I built PhantomCard: a resurrection of Apple's HyperCard that runs entirely in your browser. Stack of cards, buttons, fields, a working HyperTalk interpreter, System-7 monochrome chrome — no build step, no dependencies, just ES modules.
Try it live: https://till3005.github.io/phantomcard/ · Code: https://github.com/Till3005/phantomcard
Why HyperCard, and why "resurrection"?
Kiroween's Resurrection category asks you to bring dead technology back to life. HyperCard (1987) was the first mass-market hypermedia tool: a stack of "cards" holding buttons, fields and paint, scripted in HyperTalk — English-ish code like answer "Hello" with "OK" and go to next card. Entire generations learned programming by clicking around someone else's stack. Apple killed it in 2004, and browsers never quite replaced the magic of "open a stack, flip through cards, tweak a button's script."
PhantomCard resurrects that loop: you can flip through bundled demo stacks (a welcome tour, a séance deck, a haunted-house adventure), then hit Authoring mode and add a button, type its HyperTalk script, and watch it actually run.
How Kiro shaped the build
This is where Kiro stopped being a code generator and started being a collaborator:
-
Spec-driven development. Before a line of app code existed, we wrote the spec in
.kiro/specs/phantomcard/: requirements (data model, HyperTalk grammar surface, interaction modes), a design doc, and a task list. When the agent drifted — proposing a React scaffold or a build step — the spec pulled it back. Every judgment call I made later traced to a spec decision, not a chat message. -
Steering rules.
.kiro/steering/holds the rules Kiro worked under: zero build step, ES modules only, System-7 visual fidelity, no dependencies beyond lz-string. Those constraints are the reason the app loads instantly on GitHub Pages and the codebase stays readable end-to-end. -
The HyperTalk interpreter — the hardest part — was co-written with Kiro CLI: a lexer, a recursive-descent parser, and an async interpreter with re-entrant
send/dispatchsemantics. Kiro wrote the grammar tests that caught edge cases (e.g.item idx of omensafterput c + 1 into c).
What's in the box
- 512×342 canvas-rendered cards with dissolve transitions (faithful to the original)
- Buttons, fields, paint layers, custom Chrome menus and dialogs — all monochrome System 7
- A real HyperTalk runtime: handlers,
put/get/go/answer/ask, item/line chunks,the number of cards - URL-shareable stacks (state compressed into the link via lz-string)
- Three demo stacks authored as HyperCard docs: Welcome, The Séance Deck, The Haunted House
What I'd do differently
The trickiest bug: a "dissolve" animation re-fired on every render, not just card changes — the fix was a one-line guard on the card id, found by watching a screen recording of the app in frame-by-frame. Retro-faithful doesn't mean stateless.
PhantomCard is MIT-licensed and in the running for Kiroween 2026's Resurrection category. If you grew up on HyperCard — or never got to — go flip a stack.
Top comments (0)