Flower Factory

1. Prompt template — {FLOWER_NAME} gets replaced by each flower name. Optional {SCIENTIFIC_NAME} is filled in by the import list (section 7); if omitted there, the scientific name is appended to the common name automatically.

2. Flower names — one per line

count hint

3. Batch generate parallelism

4. Generated flowers
min max

5. Crossbreed test

parent A name

parent B name

6. Botanical metadata — resolve each common name to a species and pull family, genus & native range from GBIF (backbone: Kew's WCVP), with a link to the POWO page parallelism re-enrich already-done

7. Import list — paste rows of Common name | Scientific name (markdown tables ok). Renders each image from the scientific name and pulls its metadata automatically. Uses the template in section 1.

parallelism skip names already in gallery

8. Background removal — cut each flower out onto a transparent background with PhotoRoom, saved as a copy (the original image is kept) parallelism skip images already done

S1. Seasons — one weekly roster of 10 flowers, all free to everyone; the last three are step-gated (45k / 60k / 85k steps that week — they never ride the wheel), served centrally to every user. Seasons are database records; the serving instance picks the week that is current and rolls forward on its own. When editing locally, push seasons to prod as records (flowers must be synced there first). Badges are checked live against prod: on prod now is the week the app is serving, on prod ✓ is stored and waiting, not on prod (stale push) means the local "pushed" stamp is out of date (re-push it). current (local) only affects this machine's /api/season/current.

S2. Create / edit a season — pick exactly 10 flowers below. Pick order is roster order: slots 1–7 ride the spin wheel, slots 8–10 are the step-gated finale (45k / 60k / 85k steps within the week).

week start

filter hide flowers already in a season hide flowers without a goal

U1. Creator pages — password-gated "camera-ready" reset capability for UGC creators. The creator-facing page lives on the landing site; each row here is one creator's link + password. Every reset press: fresh 21-day step history + today pinned to 16–22k (arms the daily Reveal), the roster relocked with today's reveal handed back, the next reveal rigged to the wheel's best or worst flower (per press the creator either jumps to #1 or sinks — they find out on camera), one pending cosmetic gift, the book re-filled, and the leaderboard staged — a persistent squad of fake friends (from the U3 roster, each wearing their fixed random card cosmetics) with day boards boxed around the rigged reveal. Disable pauses the link; delete revokes it (the creator's already-applied state stays).

creator page base URL: (used for the copy-link buttons; saved in this browser)

U2. Pages

creator	username	link	password	resets	last used	status

U3. Fake-people roster — curated fictional friends (name + profile picture) the reset draws from when it stages a creator's leaderboard squad. Each person is assigned to at most one creator, so the same face never shows up in two creators' videos; squad size is random per creator (mostly 4–6 friends, sometimes 10–12) and sticks. Scores are re-dealt per press around the creator's book; people without photos fall back to a built-in name pool. Each person also carries fixed random card cosmetics (border, charms, background, font…) minted when they're created, so the same face wears the same card in every take. ugc-cleanup releases a creator's people back into the pool.

realistic mix: full names, first names, handles, random words

batch photos: each image goes to a person without a photo; downsized to 256px max side

photo	name	assigned to

C1. Upload a cosmetic — one unlockable card item the reward spins can deal. Art is a transparent PNG (the static look, and the poster frame of an animated item); add a short muted HEVC loop (.mov/.mp4) to make it animated. The kind decides which card dial it dresses: avatarBorder = ring drawn over the profile picture, accessory = charm perched on the ring, background = fills the card behind the ink, cardBorder = frame stretched over the card's edges. Bytes go to Firebase Storage and the catalog doc to Firestore (cosmetics/{id}) — this server is just the authority; nothing lives in PocketBase. Tick debug to test-drive the art first: the item upserts at a fixed debug-manual-… id, born inactive and stamped debug: true, so real players never get it — only "Pull debug cosmetics" in a DEBUG build's Debug menu fetches it. Re-uploading the same PNG filename overwrites the slot in place; once it looks right on-device, upload again with the box unticked to publish for real.

name kind PNG HEVC loop debug

C2. Items — the live Firestore catalog. Only active items reach the app (it reads cosmetics/{id} docs directly) and ride the reward spins (/api/cosmetics/deal, un-owned first). Thumbnails load from the items' Firebase Storage download links — the same URLs the app downloads. Ownership is accounted at users/{uid}.ownedCosmetics, written by this server on redeem — deleting an item never touches what users already own; the app just drops unresolvable ids.