<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dirtboi</title>
    <description>The latest articles on DEV Community by Dirtboi (@till3005).</description>
    <link>https://dev.to/till3005</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257375%2F76c54770-fd2f-40f0-8a19-cdb645d58e01.jpg</url>
      <title>DEV Community: Dirtboi</title>
      <link>https://dev.to/till3005</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/till3005"/>
    <language>en</language>
    <item>
      <title>Resurrecting HyperCard for the browser with Kiro — PhantomCard</title>
      <dc:creator>Dirtboi</dc:creator>
      <pubDate>Sat, 21 Nov 2026 13:06:51 +0000</pubDate>
      <link>https://dev.to/till3005/resurrecting-hypercard-for-the-browser-with-kiro-phantomcard-2odp</link>
      <guid>https://dev.to/till3005/resurrecting-hypercard-for-the-browser-with-kiro-phantomcard-2odp</guid>
      <description>&lt;p&gt;For &lt;strong&gt;Kiroween 2026&lt;/strong&gt; — AWS's spooky-season hackathon — I built &lt;strong&gt;PhantomCard&lt;/strong&gt;: 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.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Try it live:&lt;/strong&gt; &lt;a href="https://till3005.github.io/phantomcard/" rel="noopener noreferrer"&gt;https://till3005.github.io/phantomcard/&lt;/a&gt; · &lt;strong&gt;Code:&lt;/strong&gt; &lt;a href="https://github.com/Till3005/phantomcard" rel="noopener noreferrer"&gt;https://github.com/Till3005/phantomcard&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Why HyperCard, and why "resurrection"?
&lt;/h2&gt;

&lt;p&gt;Kiroween's &lt;em&gt;Resurrection&lt;/em&gt; 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 &lt;code&gt;answer "Hello" with "OK"&lt;/code&gt; and &lt;code&gt;go to next card&lt;/code&gt;. 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."&lt;/p&gt;

&lt;p&gt;PhantomCard resurrects that loop: you can flip through bundled demo stacks (a welcome tour, a séance deck, a haunted-house adventure), then hit &lt;strong&gt;Authoring mode&lt;/strong&gt; and add a button, type its HyperTalk script, and watch it actually run.&lt;/p&gt;

&lt;h2&gt;
  
  
  How Kiro shaped the build
&lt;/h2&gt;

&lt;p&gt;This is where Kiro stopped being a code generator and started being a collaborator:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Spec-driven development.&lt;/strong&gt; Before a line of app code existed, we wrote the spec in &lt;code&gt;.kiro/specs/phantomcard/&lt;/code&gt;: 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.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Steering rules.&lt;/strong&gt; &lt;code&gt;.kiro/steering/&lt;/code&gt; holds the rules Kiro worked under: &lt;em&gt;zero build step, ES modules only, System-7 visual fidelity, no dependencies beyond lz-string&lt;/em&gt;. Those constraints are the reason the app loads instantly on GitHub Pages and the codebase stays readable end-to-end.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The HyperTalk interpreter&lt;/strong&gt; — the hardest part — was co-written with Kiro CLI: a lexer, a recursive-descent parser, and an async interpreter with re-entrant &lt;code&gt;send&lt;/code&gt;/&lt;code&gt;dispatch&lt;/code&gt; semantics. Kiro wrote the grammar tests that caught edge cases (e.g. &lt;code&gt;item idx of omens&lt;/code&gt; after &lt;code&gt;put c + 1 into c&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What's in the box
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;512×342 canvas-rendered cards with dissolve transitions (faithful to the original)&lt;/li&gt;
&lt;li&gt;Buttons, fields, paint layers, custom Chrome menus and dialogs — all monochrome System 7&lt;/li&gt;
&lt;li&gt;A real HyperTalk runtime: handlers, &lt;code&gt;put&lt;/code&gt;/&lt;code&gt;get&lt;/code&gt;/&lt;code&gt;go&lt;/code&gt;/&lt;code&gt;answer&lt;/code&gt;/&lt;code&gt;ask&lt;/code&gt;, item/line chunks, &lt;code&gt;the number of cards&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;URL-shareable stacks (state compressed into the link via lz-string)&lt;/li&gt;
&lt;li&gt;Three demo stacks authored as HyperCard docs: &lt;em&gt;Welcome&lt;/em&gt;, &lt;em&gt;The Séance Deck&lt;/em&gt;, &lt;em&gt;The Haunted House&lt;/em&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What I'd do differently
&lt;/h2&gt;

&lt;p&gt;The trickiest bug: a "dissolve" animation re-fired on &lt;em&gt;every&lt;/em&gt; 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.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>opensource</category>
      <category>showdev</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
