Day One Nerves

Build "Day One Nerves" — a polished mobile-first portrait web app for the Eazo community, built from a live TikTok trend, in the swipe-to-decide card family.

CONCEPT
One handwritten worry sits on a slip of lined paper in the middle of a quiet dusk-blue screen — finding the classroom, introducing yourself, where to sit at lunch, the walk home. Swipe it left and the slip folds itself in four crisp animated steps into a paper crane and lifts off the top of the screen. Swipe it right and it flies to a corkboard on the left and pins itself there to practise later.

RULES & STATES
- First action is the start: no button, no cover. The first slip is already lying there with the paper texture breathing, and a small swipe glyph dissolves on the first touch.
- Left = already ready: a real four-stage origami fold animation (fold, fold, wings out, lift) then the crane rises and drifts off the top edge, leaving a faint trail.
- Right = want to practise: the slip flies to the corkboard, rotates a few degrees and pins itself with a coloured pin; the board fills up as a visible, honest record of what still feels hard.
- Cards never disappear from the corkboard and tapping a pinned slip sends it back into the deck, so nothing is ever locked away.
- When the deck empties the flock of cranes returns and circles once above the board, and a READY FOR DAY ONE badge is stamped with the crane count and the practise count. Replay writes a new set of slips. Ambient: paper grain shimmer and a slow drift on the pinned slips.

OPENING (no cover, first action is the start)
Open straight into the live scene with no button at all: the player's first gesture IS the start of the round. A small floating title chip and one animated gesture hint sit over the scene and dissolve on the first touch. Nothing may auto-advance, auto-fail or auto-end while the player is idle.

GLOBAL REQUIREMENTS
- Language: ship a lightweight built-in i18n layer with exactly two locales, English (en) and Chinese (zh). The app ALWAYS opens in English — hardcode the default locale to en and never call navigator.language or otherwise detect the system or browser language. Provide one small, comfortably tappable EN / 中文 toggle placed top-right, about 56px down from the top edge, clear of the device status bar. Chinese appears only after the user actively switches. The cover, onboarding, defaults, generated content and all share output stay English regardless of locale. Never mix two languages on one screen. Declare one shared TypeScript interface whose fields are all string, annotate both dictionaries with it and look them up as Record<'en'|'zh', T> — never let the two dictionaries infer incompatible literal types, and run a production type check before you call it done.
- Fully self-contained: absolutely no external APIs of any kind — no AI calls, no third-party data, media or font services, no remote backend, no login. Embed every item of data, copy and content in the app code. Draw all artwork procedurally in code; no image assets, no camera and no photo import.
- Share: integrate a Share feature using the @eazo/sdk community share interface so the player can post the result directly to the Eazo Community. Follow the SDK's own current best practices for composing and attaching the result — do not invent custom share plumbing. The attachment must be something the community server can fetch over the network. Place Share on the result state, keep Replay available, no placeholder buttons, and never claim the post was shared when it was not (in a plain browser the share cannot actually publish, so the button must reflect the real return value).
- SSR determinism: the initial render must be deterministic. No Math.random(), no Date.now(), no locale-dependent number or date formatting during first paint — move all of it into a client effect or drive it from a fixed seed. Hydration must produce zero console errors.
- Mobile-first portrait, touch-only, no hover dependence. The app root must follow the host container height (position: fixed; inset: 0; height: 100%) — never 100dvh or 100svh. Size any canvas from its PARENT element using a ResizeObserver and run the fit once on mount; convert every touch event through getBoundingClientRect() read at event time — never cache the rect and never use window.innerWidth/innerHeight for canvas sizing. Clamp every derived geometry value to a legal range at the point it is computed, so no radius, size or index can ever go negative or non-finite.
- Safe areas: keep all top UI at least 56px from the top edge. Keep every core interactive control AND every self-drawn bottom UI element (HUD text, counters, legends, hints) fully above the bottom 88px of the viewport — the Eazo mobile app overlays a native toolbar there that your code cannot detect. Verify at 393x852 portrait.
- Fill the screen: the layout must stretch to the full host height. No dead colour band in the lower half — if the stage has a fixed aspect ratio, give the leftover vertical space a designed extension (gradient, ambient particles, scene ground), never a bare block.
- No background music and no autoplay audio.
- Complete real states: loading, empty, success and error where relevant. Every control must actually work — no alerts, console-log placeholders or fake results.
- Visual bar: exactly ONE core rule understood within 3 seconds, with rich generous visual response on every touch (motion, particles, deformation, colour, light). Canvas 2D preferred for effects; do not use the canvas roundRect API (older iOS Safari lacks it). Never hardcode light text colours onto possibly-light backgrounds — derive text colour from the theme. Keep some ambient motion at all times so no screen is ever a still image.