Dorm Build

Build "Dorm Build" — 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
An empty isometric dorm room sits in the middle of the screen — bare mattress, bare desk, one window. Item cards slide up from the bottom edge. Drag a card into the room and the object grows into place with a spring, casting its own shadow; drag it to the left shelf and it greys out onto a 'left at home' rail. A floor-space meter fills as the room gets crowded, and once you are over capacity the next object bounces off and refuses to land.

RULES & STATES
- Direct play: the room is already lit and breathing on first paint — dust in the window light, a curtain moving — and the first card is already waiting. A drag hint traces once and dissolves on the first touch.
- Right / into the room = bring it: the object springs into a sensible spot (desk items on the desk, bedding on the bed) and the room re-composes itself so it never looks like a pile.
- Left / to the rail = leave it home: the card desaturates and slides onto a thin shelf at the left edge, still visible and still recoverable by tapping it.
- A floor-space bar and a budget bar both fill. Exceeding either makes the next object physically bounce off the floor and return to the deck — the room itself is the constraint, not an error message.
- When the deck empties the camera slowly orbits the finished room once and prints a tight dorm list card beside it. Replay clears the room with a wipe and reshuffles. Ambient: light from the window shifts continuously.

OPENING (no cover, direct play)
Open straight into the live interactive scene — interactive on the very first paint, no cover screen and no start button. A small floating title chip and one gesture hint dissolve on the first touch anywhere on the stage. The scene must already be in motion before the player does anything, and it must never reach an end state on its own 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.