A 126-Card Kids Recognition Game Ships as One 2.3MB HTML File, No Build Step Required
Single-file, no-build apps are still a real deployment option for small clients: this one carries 126 images and interactive games in 2.3MB, works offline, and survives static publishing by putting every asset path in an <img> tag. The pattern also shows what AI-generated assets can and cannot handle without runtime corrections.
Eight prompt-driven iterations turned an initial two-word brief, "educational game", into a 126-card recognition toy for children aged 3 to 6. The deliverable is one HTML file plus an assets folder: 106KB of inlined CSS/JS and 2.2MB of compressed JPEG cards, with no framework and no npm step. The game's three modes cover identifying cards by category, tap-to-connect matching, and memory flip with 4/6/8/10 pairs.
Requirements were nailed down before layout: near-zero literacy means sparse text and sound-first interaction; parents vetoed countdowns, leaderboards, points, and combo effects. 80 physical-object cards use AI-generated art at 512px/JPEG q85, while 46 number, letter, and shape cards are drawn as inline SVG at runtime, so AI can't miscount dots and the vector set adds zero bytes.
Key mechanics worth copying include a hidden display:none image library whose src attributes are visible to static publishing scanners, an SVG dash-offset animation for draw-in connect lines, state that stores actual dealt pair counts to keep progress bars solvable, and a Web Audio layer that synthesizes every sound and starts muted under a user-gesture gate. The whole game works offline on a phone or tablet, and deployment reuses one app id so a family link stays stable.
The three clarifying questions asked after the first prompt did more design work than any model capability: a four-character brief became a concrete product only after audience, form, and target skill were pinned down.
Moving concept cards to inline SVG is a sound judgment call: AI art can put six or eight stars next to a 7, and a red apple teaches the color less clearly than a pure swatch, while vector cards cost zero bytes and cannot fail the count.
A static publishing pipeline that only scans src and url() imposes a real trade-off: every image must be pulled into the initial load block, and the resulting 2.2MB is the price of a deployment that never needs a server.
Traffic analytics stay off the table: the log feature only writes to localStorage because a true open count would require a backend, and that would break the static, offline deliverable.
The decision to drop the countdown timer earns strong praise as a child-friendly move; pressure and rushing lead to tears for young kids with unsteady hands. The single-file HTML format is also valued for its portability and ease of use for parents, and the overall simplicity is seen as thoughtful design. A side point suggests using AI tool directories for inspiration on similar utilities.
Removing the countdown is crucial. Adding a countdown to a game for 3–4 year olds just creates anxiety; their hands aren't steady yet, and being rushed makes them cry. This detail shows real understanding of parenting, it's touching.
Very cleverly done. A single-file HTML is super convenient for parents—just save it and it works. For inspiration on such small tools, I usually browse AI tool directories like ai345, which sort by scenario for quick discovery and update frequently with new tools.
The greatest simplicity—click to play. It's clear a lot of thought went into this.