Selected work / Play / Singapore
Pagar Fowl
A small Three.js rooster game set around a kopitiam: kaya toast, startled neighbours and a growing flock.
The idea
A little mischief in the estate.
Keyboard movement, crowing and a heat meter turn an ordinary food-court setting into a playful game loop. The selected captures show the scene, a crow objective and the surrounding game world.
This preserves selected game moments, not a playable copy. Local prototype source remains available; exact restoration has not been tested.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The kopitiam
A rooster moves between tables in a low-poly estate scene.
Open full image ↗
02 / Selected moment
A successful crow
Crowing marks the startle objective complete and raises the heat meter.
Open full image ↗
03 / Selected moment
After the mischief
The rooster returns to a quiet moment with the crow objective marked complete.
Open full image ↗Make something of your own
Build your own.
Take the idea into Codex and adapt it to your own subject, sources and audience.
Reconstructed recipe · Not the original prompts
An end-to-end recreation has not been tested.
01BriefDefine the experience
Build a small Three.js rooster-mischief game in a [NEIGHBOURHOOD] setting. Inspect the repository and its instructions first, preserve existing work, and ask for the intended audience and available source material. Recreate the interaction idea rather than promising an exact copy of the original. Start with one complete, useful flow.
02IngredientsPrepare sources and assets
Build a small low-poly world with original character assets, tables, food, a nest and a few NPCs. Keep movement, collision, objectives and camera logic separate.
03InteractionBuild the core flow
Implement one complete loop first: grab food, attract attention, escape, bank food. Then add crowing, flock followers and a photo mode. Support readable keyboard instructions, pause, mobile alternatives and adjustable motion. Do not promise multiplayer or persistence without implementing them.
04Verify & preserveLeave a working handoff
Use a restrained layout with readable typography and clear navigation. Check the production build, keyboard access, mobile layout, reduced motion, missing assets and network failures. Keep all key information available in HTML. Record what actually passed. Leave source, a lockfile, setup instructions, data provenance and unique assets in a small rebuild kit. Exclude secrets, dependency folders and caches. Capture a few representative moments for a showcase. Do not claim an exact backup or tested regeneration unless a restore was performed.