Selected work / Singapore / events
SGWeek.ly
A Singapore events desk with weekly issues, an archive and source-checking notes.
The idea
A dated guide with a route back to the source.
This selection keeps the events desk, a historical issue and the checking rules. The stills document the public interface as captured in September 2026.
Event dates, prices and availability in these captures are historical. This page is project documentation, not a current events recommendation.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The events desk
The events desk from the captured SGWeek.ly interface.
Open full image ↗
02 / Selected moment
A historical issue
A historical issue from the captured SGWeek.ly interface.
Open full image ↗
03 / Selected moment
The checking rules
The checking rules from the captured SGWeek.ly 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 SGWeek.ly: A Singapore events desk with weekly issues, an archive and source-checking notes. 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
Retain issue snapshots, organizer URLs, source registry, venue records, Singapore time zones and rights/correction notes. Never crawl private journals or personal calendars.
03InteractionBuild the core flow
Build weekly sections, an archive and a calendar with explicit coverage dates. Deduplicate listings and keep original event links. Separate factual extraction from editorial selection and require review before publishing a new issue.
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.