Aurora Jarvis

Cinevva's analyzer read this game's design doc and its source, then wrote the brief below. "Make your own" hands it to the game creator as your opening message, so you start from a real spec rather than a one-line idea.

Create a browser-based interactive sci-fi command-console simulation titled “AURORA // JARVIS CORE,” subtitled “MULTIMODAL SIMULATION COMMAND DECK.” Build a single-screen dashboard in a dark navy/black environment with subtle blue radial glows and a faint technical grid background. Use rounded rectangular glassy panels with thin cyan-blue borders, soft blue shadows, compact uppercase typography, cyan/violet/green highlights, and muted blue-gray supporting text.

Layout: a top header spans the screen, with a glowing cyan circular orb logo on the left, the title and subtitle beside it, and a green status dot with “SYSTEM ONLINE” on the right. The main area is a three-column dashboard on desktop. Left column: a “VISION INPUT” panel with an initialization/status label, a camera/video area with a mirrored live webcam feed when permission is granted, dark overlay, horizontal cyan scan-line effect, “HAND TRACK // 01,” FPS placeholder, a large glowing circular reticle, and readouts including “PINCH = SELECT.” Below it, a “NEURAL TELEMETRY” panel marked LIVE showing four metrics: CONFIDENCE, LATENCY, ACTIVE NODES (08), and POWER LOAD (initially 42%, periodically fluctuating around 38–49%). Include explanatory text that camera hand control is available and pointer/touch are fallbacks, plus a gesture status line. If camera access is denied, clearly enter FALLBACK MODE, show POINTER, and instruct the user to use pointer or touch.

Center column: make the main “ORBITAL PHYSICS SIMULATION” panel the largest element. Its central stage has a dark blue radial glow, a bright pulsing cyan/blue spherical core, two thin elliptical orbital rings rotating in animation, and two tiny glowing satellites orbiting the core (one amber and one green). The panel status starts as RUNNING. Beneath the stage show live info: PARTICLES 12,480, FIELD STABLE, and a simulation clock starting at 00:42:18 that advances once per second while running. Below this, add a “QUANTUM THROUGHPUT” panel marked REALTIME with ten vertical animated gradient bars in cyan/blue, violet/blue, and green/blue, with varied starting heights.

Right column: add a “SIMULATION BANK” panel marked “04 READY,” listing Orbital mechanics (RUNNING), Climate lattice (READY), Drone swarm (STANDBY in amber), and Material stress (READY). Under it add a “COMMAND ACTIONS” panel labeled “TOUCH / PINCH” with a two-column grid of six large buttons: ORBITAL FIELD, CLIMATE MAP, DRONE SWARM, MATERIAL TEST, PAUSE CORE, and RESET ALL. Add a command log below reading “AURORA: Awaiting operator intent.”

Interaction and mechanics: clicking/tapping a simulation button selects it, highlights the corresponding button, sets the simulation status to RUNNING, updates the central FIELD and PARTICLES values, and writes a log message. Use these exact mappings: Orbital field/orbital mechanics = FIELD STABLE and 12,480 particles; Climate map/climate lattice = FIELD DYNAMIC and 8,240 particles; Drone swarm = FIELD FORMATION and 64 UNITS; Material test/material stress = FIELD LOADED and 3,840 CELLS. PAUSE CORE toggles between RUNNING and PAUSED and logs either “Core simulation paused by operator.” or “Core simulation resumed.” RESET ALL returns to orbital mechanics, RUNNING, STABLE, 12,480, and logs “All simulation nodes reset to baseline.” Clicking or tapping the orbital simulation stage should select orbital mechanics and log “Pointer intent accepted. Orbital field selected.”

Provide optional webcam hand tracking using MediaPipe Hands if available: request one user-facing camera, mirror the video, track one hand, and map the index fingertip to the reticle position (mirrored horizontally). Display SEARCHING with a searching gesture when no hand is visible, TRACKING and HAND LOCK when detected, confidence percentage, randomized latency around 18–30 ms, and gesture labels OPEN PALM, POINT STEER, or PINCH SELECT. A pinch is index-thumb distance below a small threshold and triggers selection on the pinch’s transition; an open palm while on orbital mode changes the central status to FIELD SCAN and logs “Open palm detected. Scanning orbital field.” Pointer movement over the simulation stage should also move the reticle, and pointer/touch button input must work without a camera. Keep the visual experience as a polished monitoring console rather than an action game: no enemies, weapons, lives, or invented win condition.

At the bottom, add a footer reading “AURORA OS v7.4.1 // LOCAL SIMULATION MODE” on the left and “HAND CONTROL” with the current hand state on the right. Make the layout responsive: compress to two columns at medium widths and a vertically scrollable single-column dashboard on small mobile screens while retaining all panels and controls. Animate the orbital rings, core pulse, throughput bars, scan lines, and subtle glows continuously, but pause only the simulation clock and simulation running state when PAUSE CORE is active.