๐ cindyzhu.com.au/trip-palette
Type in a destination, your dates, and what you'll be doing. You get back:
No sign-up, no keys, nothing to install. It runs on free, no-key APIs (Open-Meteo weather + geocoding, Wikimedia photos).
The complete React project Claude built, with a README that walks you through everything. Inside:
npm install then npm run dev (no Node.js? just ask Claude: "check if Node is installed and install it if not")npx vercel with a free vercel.com account, Claude walks you through the login when the CLI asksThis is the fun part, and the real lesson from the reel. Open the folder in Claude and ask for upgrades:
๐ท Closet mode (my favourite).
Add a "my closet" step: I'll drop photos of clothes I own into a folder. Read them, tag each item by type and color, and rewrite the packing list to reference my actual clothes (like "your rust linen shirt works with swatch 2"), plus a short "gaps worth shopping" list.
๐ซ Shareable palette card.
Add a share button that renders a boarding-pass style image: destination, dates, the four swatches with hex codes, and the top five packing items, sized for an Instagram story.
๐งณ Carry-on mode.
Add a carry-on toggle that trims the list to carry-on limits and checks that every top pairs with every bottom inside the palette.
And when you restyle it, don't say "make it pretty". Find ONE design you genuinely love (editorial travel journals, vintage luggage tags, boarding passes), screenshot it, and tell Claude exactly what to take from it. Then iterate with a screenshot of every version:
Here's a screenshot of the current version.
KEEP: [what's working]
FIX: [what feels off, be visual and specific: spacing, size, color, alignment]
CUT: [anything unnecessary]
Only touch what I listed, then show me the updated version.
Anthropic's own Claude Code best practices recommend exactly this screenshot-driven loop, and Nielsen Norman Group found that visual references beat vague words like "clean" or "modern" every time. That loop is the difference between a build that looks designed and one that looks generated.
The build order that works (each step is one prompt to Claude): sample-data version first, deploy the skeleton early, design pass on stable data, then make weather + location real, then photos + palette, then a human test. Start with this and build up:
Build a working first version of a React website called Trip Palette.
Goal: turn a trip into a packing plan.
Inputs: a destination, start and end dates, and optional activities (like hiking, safari, city walking).
Outputs: a weather summary for the dates, a four-color palette drawn from the destination's landscape, and a packing list with quantities.
First, check that Node.js 20+ is installed and install it if not. Then use realistic sample data for everything so the complete flow works end to end.
Keep it focused: no accounts, no checkout, no dashboard, nothing I didn't ask for. Run it locally and show me.
๐งณ The app: cindyzhu.com.au/trip-palette
๐พ The code: trip-palette-source.zip
๐ค Claude: claude.com (Desktop Code tab or Claude Code, from the Pro plan)
๐ฆ Open-Meteo: open-meteo.com (weather + geocoding, free, no key)
๐ Vercel: vercel.com (free hosting for your own copy)