Selected work / Singapore / art
Which Collection?
A two-image art guessing game pairing Singapore Open Art with The Met.

The idea
Recognise a collection through its art.
This selection keeps the opening, a practice round and the artwork explorer. The stills document the public interface as captured in September 2026.
Artworks are documented as public domain or CC0 by the original project. Scores and collection counts describe the captured version.
Three selected moments
A closer look.
Move through the selected stills.

01 / Selected moment
The opening
The opening from the captured Which Collection? interface.
Open full image ↗
02 / Selected moment
A practice round
A practice round from the captured Which Collection? interface.
Open full image ↗
03 / Selected moment
The artwork explorer
The artwork explorer from the captured Which Collection? 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 Which Collection?: A two-image art guessing game pairing Singapore Open Art with The Met. 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
Use provenance records, rights evidence, and locally cached open artworks from both collections. Preserve catalogue IDs and distinguish Singapore-linked works from artist nationality.
03InteractionBuild the core flow
Build a ten-round comparison, practice mode, keyboard answers, and a searchable artwork explorer. Show labels and source links after an answer. Keep shared-score persistence optional and never imply that a local score is globally ranked.
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.