SEELE AI Gaming Platform

Please use Three.js to generate a **mobile-first game** with the theme "**Knee Surgery Simulator**". Please read the following detailed game design requirements first, and then generate the code accordingly: ### 1. Assets & Environment * **Visual Style:** "Stylized Medical Realism." Use a slightly low-poly aesthetic with high-quality textures to depict anatomy without being overly gruesome or performance-heavy. The color palette should be dominated by surgical blues/greens for the background and pink/red/white for the organic tissues. * **Main Model (The Knee):** Create a central 3D knee joint model. It needs distinct layers: * **Layer 1 (Skin):** Tan/Peach surface that needs to be marked and cut. * **Layer 2 (Internal):** Visible white meniscus/cartilage, red muscle tissue, and yellowish fat deposits. * **Damage:** Procedurally generate "tears" in the cartilage or "bone fragments" floating in the area. * **Tools:** Low-poly 3D models for surgical instruments: Scalpel (for cutting), Retractors (to hold skin open), Arthroscopic Shaver (for cleaning), and Forceps (for removing debris). * **Camera & Lighting:** A static, top-down perspective (or slightly angled). Implement a "Surgical Spotlight" effect—a strong directional light in the center with a vignette shadow around the edges to focus attention. * **VFX:** Particle effects for "blood squirts" (cartoonish red droplets) when cutting, and small white dust particles when shaving bone. ### 2. Audio Requirements * **BGM:** A sterile, slightly tense "Hospital Ambient" track. Low-frequency hum of machinery mixed with a rhythmic, calm heart rate monitor beep. * **SFX (The "Gross" Factor):** * **Squishing/Wet sounds:** When interacting with exposed tissue. * **Metallic Clinks:** When picking up or dropping tools. * **Suction/Vacuum noise:** When using the shaver tool. * **Bone Crunch:** A crisp, dry sound when removing bone fragments. * **UI:** High-pitched "beep" for tool selection, low-pitched "buzzer" for mistakes (hurting the patient). ### 3. Gameplay Loop The game follows a linear surgical procedure (The "Operation"): 1. **Preparation:** The player must trace a dotted line on the knee with an antiseptic marker. 2. **Incision:** Select the **Scalpel**. The player must drag their finger along the marker line. Accuracy is tracked (deviation reduces health). 3. **Exposure:** Use **Retractors** to pull the skin apart (drag gesture outwards). 4. **Repair (Core Puzzle):** * **Debridement:** Use the **Shaver** to erase/smooth out rough edges of torn cartilage (erasing mechanic). * **Extraction:** Use **Forceps** to carefully tap and drag floating bone fragments out of the wound without touching sensitive walls. 5. **Closure:** Use a **Needle/Suture** to tap specific points in a zig-zag pattern to stitch the wound closed. * **Win Condition:** Successfully complete all steps within a time limit or before the patient's heart rate drops to zero. * **Fail Condition:** Causing too much damage (indicated by a redness meter or rising heart rate beep speed) results in "Malpractice." ### 4. Mobile Controls & Interaction * **Orientation:** **Portrait Mode** (vertical) to simulate focusing on the specific limb. * **Touch Input:** * **Drag/Swipe:** Used for cutting (scalpel) and cleaning (shaver). The raycaster must map touch coordinates precisely to the 3D surface. * **Tap:** Used for picking up debris (forceps) or placing stitch points. * **Tool Selection UI:** A persistent bottom toolbar containing large icons (minimum 60x60px) for switching tools. The active tool should visually highlight and float slightly above the knee model. * **Haptic Feedback:** * Trigger a short vibration (10ms) when a tool successfully interacts with the target area. * Trigger a long, heavy vibration (500ms) if the player cuts the wrong area or hurts the patient. * **Visual Feedback:** When the finger touches the screen, display a small "touch point" reticle so the user can see exactly where their tool is acting, as their finger might cover the model. Do not ask for clarification. Do not request confirmation. Directly execute the generation task based on the given instructions.