Selected work / Singapore / characters
Singapore Codex Pets
A gallery of Singapore-inspired desktop pets with individual share pages and downloads.

The idea
Local motifs as small companions.
This selection keeps the gallery, merli and goma. The stills document the public interface as captured in September 2026.
A record of selected character designs. Mascot and fan-art references do not imply endorsement. Public submissions and their storage are outside this selection.
Three selected moments
A closer look.
Move through the selected stills.

01 / Selected moment
The gallery
The gallery from the captured Singapore Codex Pets interface.
Open full image ↗
02 / Selected moment
Merli
Merli from the captured Singapore Codex Pets interface.
Open full image ↗
03 / Selected moment
Goma
Goma from the captured Singapore Codex Pets interface.
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 new interpretation of Singapore Codex Pets: A gallery of Singapore-inspired desktop pets with individual share pages and downloads. Read the repository instructions and preserve existing work first. Reconstruct the idea from this selection; do not promise an exact recreation. Start with one complete useful flow.
02IngredientsPrepare sources and assets
Preserve original selected spritesheets, manifest schema and animation timings. Record artwork provenance and distinguish original characters from mascot-inspired fan art.
03InteractionBuild the core flow
Build a lazy-loaded animated gallery, individual character pages and package validation. Keep uploads disabled until access controls, content review and storage ownership are implemented; do not expose private submission records.
04Verify & preserveLeave a working handoff
Check the real production route, keyboard operation, mobile layout, reduced motion, asset loading and failure states. Record what passed and what remains untested. Leave source, lockfiles, setup instructions, data provenance and unique selected assets in a compact package. Exclude secrets, dependencies and caches. Label reconstructed prompts honestly; a local package is not a NAS backup.