SEELE AI Gaming Platform

Please use Three.js to generate a **mobile-first game** with the theme "Fat Slice 2". Please read the following detailed game design requirements first, and then generate the code accordingly: ### 1. Assets & Environment * **Visual Style**: Adapt the original 2D Flash aesthetic into a **2.5D Flat-Shaded style**. The game should look like paper cutouts or flat vectors floating in 3D space. * **The "Fat" Shape**: Use `THREE.ExtrudeGeometry` or `THREE.ShapeGeometry` to create the main sliceable object. It should be a bold, fleshy color (Orange/Red like the screenshot) with a slight depth (z-axis thickness). * **Hazards**: The bouncing balls should be simple high-contrast White Spheres (low poly count) or flat white circles. * **Background**: A dark, solid contrasting color (e.g., Dark Maroon or Deep Grey) to ensure the bright white balls and orange shape pop on small mobile screens. * **Effects**: * **Slice Trail**: A glowing particle trail or line rendered following the user's finger swipe. * **Cut Feedback**: When a piece is sliced off, it should flash briefly and then fall downwards off-screen using simple physics (gravity). * **Optimization**: Use a single shared material for all debris pieces to minimize draw calls. Avoid complex lighting; use `MeshBasicMaterial` or `MeshLambertMaterial` with a simple ambient light. ### 2. Audio Requirements * **BGM**: A quirky, looped "Sneaky Jazz" or "Pizzicato Strings" track that feels slightly mischievous and tense, matching the "annoying puzzle" description. * **Sound Effects (SFX)**: * **Slice**: A sharp, satisfying "Schwing" or "Paper Tear" sound. * **Bounce**: A cartoonish "Boing" or high-pitched "Ping" when balls hit the walls of the shape. * **Failure/Collision**: A harsh "Buzz" or "Splat" sound if the slice line touches a ball. * **Success/Drop**: A crumbling or sliding sound when a sliced chunk falls away. ### 3. Gameplay Loop * **Objective**: The player must reduce the total surface area of the main shape to a target percentage (e.g., < 20%) to win the level. * **Mechanics**: * **The Slice**: The player draws a line across the shape. The code must calculate the intersection points. * **The Split**: Upon release, the geometry is mathematically split into two separate polygons. * **Ball Check**: The game logic must determine which of the two new polygons contains the white bouncing balls. * **Physics**: The polygon *containing* the balls stays fixed. The polygon *empty* of balls becomes a dynamic physics object, falls off the screen, and its area is added to the "Score/Removed" total. * **Fail State**: If the slice line intersects with a white ball during the swipe, the slice is cancelled, and the player loses a life or restarts. * **Constraint**: Balls bounce continuously inside the changing shape boundaries. As the shape gets smaller, the balls bounce faster or become harder to avoid. ### 4. Mobile Controls & Interaction * **Touch Controls**: * **Swipe-to-Slice**: Use `touchstart` to begin the cut, `touchmove` to draw the cut line (visualized by a red dashed line), and `touchend` to execute the slice. * The slice is valid only if the line enters and exits the shape (cuts all the way through). * **Orientation**: **Portrait Mode** is preferred for one-handed play, keeping the shape centered in the upper 2/3rds of the screen. * **UI Layout**: * Top Bar: Progress bar showing "Current Size" vs "Target Size". * Bottom Area: A clear zone for fingers to start swipes so the hand doesn't obscure the main gameplay area. * **Haptic Feedback**: Trigger a distinct vibration pattern (using `navigator.vibrate`) when a slice is successfully executed, and a jarring vibration on failure. * **Visual Cues**: If a slice is invalid (doesn't go through, or hits a ball), the cut line should turn red and fade out. If valid, it turns green before executing. Do not ask for clarification. Do not request confirmation. Directly execute the generation task based on the given instructions.