Kinda Chic

Build "Kinda Chic" — 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
Swatch cards show one style trait at a time rendered as material rather than clothing — a weave, a colour, a silhouette outline, a mood word set in a matching typeface. Swipe right and the swatch tears free and pins itself into a moodboard grid that reflows to fit; swipe left and it curls up and drops out of frame. The board is a real layout that recomposes every single time.

RULES & STATES
- Traits are grouped into colour, silhouette and mood, and the board reserves a region for each so it can never become nine swatches of the same kind.
- Right = would wear it: the swatch tears with a real fibre edge, pins in with a shadow, and the grid animates as it reflows around it.
- Left = not my style: the swatch curls from one corner and falls away; nothing is stored.
- The board caps at three colours, two silhouettes and one mood word — a new keep in a full slot bumps the weakest, visibly, so the trade-off is always on screen.
- Result: a style board card with the three colours as a palette strip, the two silhouettes as line drawings and the mood word as the headline. Replay clears the pins. Ambient: the swatch edges always lift slightly as if in a draught.

OPENING (cover mode)
Open with a full-bleed opening artwork unique to this app, drawn procedurally in code: A moodboard of nine torn-edge swatches pinned in an irregular grid — herringbone, washed denim, oxblood leather, raw linen — one swatch lifted at the corner casting a shadow; the title is stamped across three swatches at once in a thin uppercase so it breaks over the torn edges. The title must be integrated into the artwork itself — never the generic "title + tagline + how-to card + Enter button" layout. Any text drawn on the canvas needs a contrasting stroke outline so it can never blend into the art beneath it, and the main title must sit at least 20 percent down from the top so it clears the language toggle. The artwork must fill the frame — no empty single-colour field with one line of text. Below the artwork show at most ONE short tutorial line, then exactly ONE text button that starts play. Nothing else on the opening screen.

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.