About
The Bunny Game Arcade
A personal project by Gregory Ng — LinkedIn
Where it started
The Bunny Game Arcade began as an attempt to recreate Macigame — a classic Mac shareware puzzle game from the 1990s that Gregory played as a kid. The original mechanic was simple: a grid of tiles displaying various characters, and the goal was to click matching groups to clear them. It was satisfying in a way that's hard to explain — the snap of tiles disappearing, the cascade of new configurations, the quiet arithmetic of clearing a board.
Recreating that mechanic as a browser game turned out to be the easy part. What came next was less expected.
What it became
Once Classic was running, the obvious question was: what else could this mechanic do? Bomb Mode answered one version of that question. 86 Bunnies answered another. Hare Line introduced sliding. Shroom Mode explored pure visual transformation. Each experiment asked something different of the same underlying idea — and each one suggested three more.
That pattern accelerated into something larger. The arcade is now a growing library of browser-based games and puzzles spanning logic, word games, memory challenges, audio mechanics, daily shared puzzles, and physics simulations. As of this writing, the collection includes over 60 distinct games across more than 20 mechanic categories.
The real experiment
This project is Gregory Ng's personal laboratory for testing rapid prototyping workflows using AI-assisted development. Every game on this site was designed, built, iterated, and deployed through a workflow centered on Claude Code — Anthropic's agentic coding tool. The pace at which functional, playable games can be conceived, built, and shipped using these tools is the actual experiment. The games are the artifacts.
The questions driving the project:
- How quickly can a novel game mechanic go from concept to deployed, playable game?
- Which mechanics produce genuine replayability versus one-time novelty?
- What does a library of accelerator components for game development actually look like when built iteratively rather than planned upfront?
- How do usage patterns differ between daily-reset games, infinite-replay games, and finite level-progression games?
The developer layer
Because everything is built in vanilla JavaScript with no framework dependencies, the underlying implementations are unusually portable and readable. The DEV page documents the core mechanics as reusable code modules — from Hamiltonian path solvers to hex grid systems to daily shared puzzle architecture — available for other developers to learn from and build upon under an MIT License.
The goal isn't just a collection of games. It's a collection of solved problems, each one documented well enough that the next person who wants to build a sliding puzzle, a daily word game, or a logic puzzle generator doesn't have to start from scratch.
About Gregory Ng
Gregory Ng is a creative entrepreneur, designer, and technologist based in Raleigh, NC. He is EVP of Decision Science at MERGE, a health and wellness marketing agency, where he leads a team focused on data analytics, behavioral science, and strategic marketing. He is a RISD alumnus, serves on the board of Artspace Raleigh, and writes about authenticity and algorithmic optimization in his Substack newsletter The Human Thread.
This project sits at the intersection of his longstanding interests in game design, visual systems, rapid iteration, and the emerging question of what human creativity looks like when it works alongside — rather than against — AI tools.