Front-end developer for 20+ years. Native JavaScript believer.
These days I'm chasing one question:
How far can HTML, CSS, and JavaScript go as a game engine — with AI as a co-developer?
A roguelike deckbuilder built on Hwatu (Korean flower cards), live on Steam in Early Access.
No game engine underneath — TypeScript, DOM, and CSS all the way down, wrapped in Electron. Designed, coded, and shipped side by side with AI agents, under the Joon x Jin Works label.
Building a game on pure web tech means building the missing tools too — most of them designed so AI agents can use them and verify their own work.
- spine-html — Spine skeletal animation rendered as plain DOM: one CSS matrix per slot, no canvas for the rigid tier
- rigc — rig compiler for Spine: declarative rig specs in, Spine 4.3 skeleton data out, verified by a spine-core round-trip
- byteguard — Vite plugin that encodes JS bundles into binary format for casual source code protection
- headerless — strips format-defining header fields from binary assets at build time; not encryption, not DRM
jandi · electron-react-devtools · struct.js · clog · swift
- Blog — firejune.io
- X — @firejune