SEELE AI Gaming Platform

Please use Three.js to generate a **mobile-first game** with the theme "**Red Runner - High Contrast Infinite Flyer**". Please read the following detailed game design requirements first, and then generate the code accordingly: ### 1. Assets & Environment * **Visual Style**: **Minimalist Silhouette Art Style**. The game must strictly adhere to a high-contrast color palette based on the reference: * **Background**: Intense, solid Red (`#D40000` or similar) with matching Fog to hide the far clipping plane. * **Foreground/Obstacles**: Pure Black (`#000000`) geometric shapes (cubes, moving pillars, jagged terrain). * **Player Character**: A stylistic, low-poly **Rocket** or Missile. White body with black stripes/accents (`#FFFFFF` & `#000000`) so it stands out clearly against the red background. * **Camera**: Use an **Orthographic Camera** to simulate a 2D side-scrolling perspective while using 3D assets. * **Particles**: Implement a particle system for the rocket's exhaust. It should emit small black or dark grey triangles/cubes that fade out, mimicking the "smoke trail" seen in the screenshot. * **Mobile Optimization**: Use `BoxGeometry` for obstacles to keep poly count low. Reuse geometries and materials. Shadow casting is not necessary due to the silhouette style; rely on ambient light and distinct colors. ### 2. Audio Requirements * **BGM (Background Music)**: A fast-paced, frantic **8-bit chiptune or Retro Synthwave** track. It should feel "funny" and urgent, encouraging a "just one more try" loop. * **Sound Effects (SFX)**: * **Thrust**: A continuous, buzzing noise or white noise loop when the player touches the screen (rocket engine firing). * **Explosion/Death**: A comical, loud "CRASH" or synthesized explosion sound when hitting an obstacle. * **Score**: A subtle "ding" or high-pitched blip every time the player passes a specific distance marker. ### 3. Gameplay Loop * **Core Mechanism**: "Flappy Bird" or "Jetpack Joyride" style physics. * The Rocket moves forward (right) automatically at a constant speed (which slowly increases over time). * Gravity constantly pulls the Rocket down. * **Input**: Touching/Holding the screen applies upward vertical force (Thrust). Releasing allows gravity to take over. * **Obstacles**: Randomly generated black structures coming from the right. These should include: * Static pillars (top and bottom). * Floating blocks. * Moving vertical gates (for the "Hard" tag). * **Scoring**: Score is based on distance traveled. Displayed in large, white, retro-style font at the top center. * **Fail State**: Collision with any black environment object triggers an immediate "Game Over". The rocket should break apart (simple particle explosion) and a "Try Again" button appears. ### 4. Mobile Controls & Interaction * **Control Scheme**: **One-Touch Gameplay**. * `touchstart` / `mousedown`: Activate thrusters (fly up). * `touchend` / `mouseup`: Deactivate thrusters (fall down). * **Orientation**: **Landscape Mode** is preferred for a wider view of upcoming obstacles, but the camera zoom should adapt if the user is in Portrait. * **UI & Feedback**: * **Start Screen**: A simple overlay with the title "RED RUNNER" and a "Tap to Launch" prompt. * **Haptic Feedback**: Trigger `navigator.vibrate(200)` upon collision/death for tactile impact. * **Hitboxes**: Make the player's hitbox slightly smaller than the visual model to make the game feel fair ("coyote time" collision logic). Do not ask for clarification. Do not request confirmation. Directly execute the generation task based on the given instructions.