# Routelette — rebuild recipe

Revision: routelette-20260909-83b16d

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

Distances, access and route conditions are historical source data. Verify current conditions before walking; these screenshots are project documentation.

## 1. Define the experience

Build a walking-route picker for [CITY] with region, length and mood controls. 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 small source-backed route dataset with stable IDs, geometry, distance units, access notes, official URLs and checked dates. Distinguish total mapped track length from one continuous recommended walk.

## 3. Build the core flow

Implement lockable constraints, a reproducible shuffle option, clear empty states, map/list synchronization and an explanation of why a route matches. Keep directions as explicit external links; do not require location permission for basic browsing.

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