# Toronto / Sanctuary Locations — rebuild recipe

Revision: toronto-20260909-83b16d

Reconstructed recipe; not the original prompts. End-to-end regeneration is untested.

Scouting scores and availability reflect a historical project brief; they are not current travel, venue or permit guidance.

## 1. Define the experience

Build a location-scouting website for [CITY] with a map, ranked places and a shortlist. 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.

## 2. Prepare sources and assets

Use a source-backed place manifest with coordinates, licensed photographs, date-checked access notes, explicit ranking weights and uncertainty. Keep venue access distinct from aesthetic scores.

## 3. Build the core flow

Implement map/list synchronization, search, filters, an accessible location drawer and a local shortlist. Include a text list when map tiles fail. Avoid contacting venues or exposing private production details.

## 4. Leave 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.