Rebuild 1980s arcade typing games as a keyboard trainer from specs

Earl Grey had Kiro build Dead Keys, a typing trainer with a missed-key heat map, from 19 specs in about 35 hours over three days, ending with 949 passing tests and a live deploy.

Done withKiroClaudeinVercelGitHub· Nov 21, 2026

What they did

For the Kiroween 2026 hackathon, Earl Grey, who runs court operations for a California county, set out to bring back the falling-word typing games of the early 1980s as a trainer that tracks missed keys and drills them. Claude (Opus 5.5) wrote the specs and reviewed each block. Kiro built the engine, storage, screens, gameplay, drills and a small MCP server from 19 specs, each split into requirements, a design and a task list. Kiro also made the commits, pushes and Vercel deploys from its own terminal. The build used hooks, including one that keeps every source file under 150 lines, and two custom agents. An optional AI layer on Amazon Bedrock writes practice lines, with code checking every line it returns.

How it went

The game shipped and is playable online. The repo counted 19 specs, 279 requirement lines, 165 finished tasks and 949 unit and property tests passing, with 15 accessibility scans and no issues. A spec rule to flag gaps instead of guessing made Kiro come back with ten questions in the first block, which the author says saved rework. A property test caught a words-per-minute bug that returned NaN for very short times. Things went wrong too: the line-cap hook never fired because of the wrong trigger, the first real screens did not match the locked design because the spec only called the mock a reference, and the first deploy went straight to production.

Worth knowing

Passing checks only showed the code matched the spec, not that the spec was right; the fix was a side-by-side screenshot check against each mock. On a new project the Vercel CLI made the first deploy production even without the production flag. The author checks that a hook actually runs before trusting it. Claude built some later features to save Kiro credits.

Try it

With Kiro· 5 parts to fill in

Build [app or game idea] spec first. For each block, write a requirements file, a design and a task list with one file per task in [spec folder], then build it. When the spec leaves something open, stop and list the gaps as questions instead of guessing. Add a hook that enforces [rule, such as a max file length] and prove it fires before counting it. Write property-based tests for [core logic]. Treat [design mock] as something each screen must match, and show me screenshots side by side for approval. Deploy only as a preview unless I say production. Stop at the end of each block for my review.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related