# Mirage

## Motion implementation and acceptance

Implement the interactions specified in the brief. The catalogue recording is a visual reference and the poster is a loading, error or reduced-motion fallback. Implement the moving scene separately from both.
- Catalogue recording (reference only): https://media.scrollhaus.ai/previews/mirage.stream-f2a789a1.mp4
- Poster (still fallback only): https://scrollhaus.ai/thumbs/mirage.webp
- Scene source · mirage-plate-720p.mp4: https://media.scrollhaus.ai/sites/mirage/assets/video/mirage-plate-720p.mp4
- Frame sequence: https://media.scrollhaus.ai/sites/mirage/assets/sequence/{frame}.webp (frames 1–96, zero-pad to 3 digits)

Additional source assets. For each grouped list, prepend its base URL to each filename or path exactly as written.
- https://media.scrollhaus.ai/sites/mirage/assets/sequence/001.webp

For scroll-scrubbed video, use a muted inline video, wait for loaded metadata, and map section progress in both directions to the video timeline. Seek when the target changes and coalesce seeks while one is pending. For a frame sequence, draw the indexed frame to canvas as scroll progress changes. For scripted, CSS or 3D motion, recreate the triggers and transforms in the brief. Use normal playback for clips described as loops.

Test at two different scroll positions and then scroll back. Confirm the video time and visible frame change, or confirm the specified canvas, CSS or 3D state changes. If a required source fails, report its URL and the missing motion before calling the build complete.

Create a responsive React + TypeScript + Vite + Tailwind CSS website. Use small components for navigation, hero, interactive stage, content sections and footer. Put media URLs in src/lib/assets.ts and animations in cleaned-up hooks. Do not output a giant HTML file, an iframe, or a screenshot pretending to be the website.

## Design direction
A studio that shoots impossible scenes in one continuous take. Everything is fixed to the viewport and a 900vh empty runway drives it. Three stacked canvases play the same 96-frame film, each one second ahead of the layer below. At one third of the scroll a second film layer opens as a widening box that rotates to −45° (a diagonal wipe) while its picture counter-rotates to stay upright. Between .43 and .77 a "Selected work" strip slides up, and its rows fly apart sideways. At two thirds a third layer wipes open full-frame. The "MIR*A*GE®" wordmark (script A) flies toward the viewer in 3D and is gone within the first 8% of the scroll, then returns at the end. A "Takes (01)" counter flies in and out the same way near the end.

Palette and type: --font-display: 'Anton', sans-serif` (wordmark, logo, section title, counter number), uppercase.; --font-script: 'Pinyon Script', cursive` (the A in MIRAGE, "(cut)"): always `line-height:0; --font-ui: 'Inter Tight', sans-serif` 400/500 (body and chrome)..
Font families: Anton, sans-serif` (wordmark, logo, section title, counter number), uppercase. / Pinyon Script, cursive` (the A in MIRAGE, (cut)): always `line-height:0 / Inter Tight, sans-serif` 400/500 (body and chrome)..
Font stylesheet: https://fonts.googleapis.com/css2?family=Anton&family=Pinyon+Script&family=Inter+Tight:wght@400;500&display=swap

## Layout and copy
“Nothing staged, nothing (cut)®”
Preserve that section order (for a one-screen concept, preserve that one-screen composition), real text and distinctive composition. Use the asset map below for additional labels, body copy, colors and asset roles. Do not add unrelated dashboard sections or generic filler.

## Motion and interaction
## 5.stage#stage (inset 0): video#vid0 + canvas#cv0, each centred 100vw × 100vh, object-fit cover.reveal--a#revealA (aria-hidden): centred box, overflow hidden, --span-w = --span-h = calc(72vw + 72vh), --angle −45deg; width = --reveal · --span-w, height --span-h, transform: translate3d(−50%, −50%, 0) rotate(--reveal · −45deg).01 scale hides Chrome's 1–2px clip fringe. Contains video#vid1 + canvas#cv1 (100% × 100%, cover).sec2#sec2 (inset 0, flex-centred, pointer-events none, opacity 0).01) translateZ(0); video#vid2 + canvas#cv2.chrome#chrome (inset 0, pointer-events none, perspective:1200px; perspective-origin:50% 50%): header, title, about line, counter.runway#runway: height 900vh, width 1px, pointer-events none — the only thing that scrolls.
Use React refs for canvas/video/3D and effects with cleanup for listeners and animation frames. Keep scroll progress reversible and independent of React rerenders. Match the demonstrated interaction, not just its opening still.

## Exact media
Asset and content map (JSON, not HTML): https://scrollhaus.ai/build-assets/mirage.json
Visual demo: https://media.scrollhaus.ai/previews/mirage.stream-f2a789a1.mp4
Thumbnail / loading poster: https://scrollhaus.ai/thumbs/mirage.webp
- asset: https://media.scrollhaus.ai/sites/mirage/assets/video/mirage-plate-720p.mp4
- Sequence: https://media.scrollhaus.ai/sites/mirage/assets/sequence/{frame}.webp; frames 1–96, 3-digit zero padding (001, 002…). Load the first frame immediately, then progressively fill the range; do not wait for every frame.
Read the JSON map before implementing; its referenceNotes contain the full design and motion details. Follow this React/TypeScript instruction when historical notes mention a different stack or standalone HTML. Keep source media at neutral saturation and contrast; do not add colour boosts. Use its exact URLs, including query strings. Resolve every asset independently; do not turn the thumbnail into the full-screen hero. Do not replace missing media with stock pictures. Report a failed URL and keep a useful loading/error state.

## Responsive behavior and finish
At 1440×900 keep the reference's text/image balance. At 390×844 stack content deliberately, use touch equivalents for hover/drag, keep faces/products uncropped, and avoid horizontal overflow. Videos that loop must be muted and playsInline; do not hide real scroll motion behind an autoplay loop. Honor reduced motion, keep keyboard access, and pause offscreen/hidden-tab rendering.

Run the production build. Check desktop and phone layouts, every supplied image/video/model, the main interaction in both directions, navigation and CTAs. Keep demo-only forms/cart UI local unless a backend is explicitly requested. Compare against the reference; report any unverified differences rather than claiming a guaranteed match.