Iron Man Interface

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 control interface titled “IRON MAN INTERFACE,” presented as a full-screen, fixed dashboard rather than a conventional level. Use a dark near-black background, cyan monospace typography and borders, yellow section headings, and green status text. Split the main area vertically into two roughly equal panes beneath a 48px header, with a thin cyan divider.

Header: show “IRON MAN SUIT v7.4”, an ARC percentage readout that continuously oscillates around 94–99%, and “BODY TRACK: ACTIVE”. Include a cyan-outlined pause-tracking toggle labeled “PAUSE TRACKING”; visually include the control, but it does not need to alter behavior unless implementing the visible code behavior exactly (the original declares it without wiring a handler).

Left pane: render a Three.js-style 3D inspection room. It has a dark blue-gray floor, a dark blue-gray wall behind it, soft cool hemisphere lighting and a white directional light. Place a human-shaped modular suit/character model toward the left/front of the room, colored uniformly deep red with subtle dark red emissive accents, standing in an idle animation. Use a fixed perspective camera positioned in front of and slightly above the character; the character is initially rotated slightly toward the viewer/right. Do not use first-person view, pointer lock, combat, enemies, or a free camera. The left pane should have an overlaid cyan-bordered “BODY TRACKING” panel near its top-left showing Pose: STANDING, Arms: IDLE, Head: CENTER, plus small help text “Drag on left view to track” and a CALIBRATE button.

Left interaction: pressing and dragging with the primary mouse button over the 3D view changes the suit’s yaw and a small vertical pitch/offset, clamped to approximately yaw -1.2 to 1.2 and pitch -0.7 to 0.7. Update the HUD based on those values: head is RIGHT or LEFT when absolute yaw exceeds 0.5, otherwise CENTER; pose is LEANING when absolute pitch exceeds 0.3, otherwise STANDING; arms are RAISED when absolute yaw exceeds 0.8, otherwise IDLE. A double-click or CALIBRATE resets the tracking to yaw 0.4 and pitch 0 and logs “Body tracking calibrated” for the button action. Keep the character in the room and preserve the fixed camera.

Right pane: create a “DESKTOP SHARING — LIVE” header with an Objects counter, then a large clickable canvas representing a live desktop stream. Draw a dark navy desktop with an inset panel, a narrow top bar reading “DESKTOP SHARE — LIVE FROM CAMERA,” and a subtle blue grid. Display five moving desktop application windows that bounce within the desktop bounds: Chrome (blue title bar), Explorer (orange), VS Code (green), Terminal (purple), and Spotify (pink/red). Each window has a dark frame, border and shadow, a colored title bar with its label, and small monospace content appropriate to the app: Chrome shows “🔍 12 tabs open” and “youtube.com”; Explorer shows “📁 Documents” and “📄 game.js”; VS Code shows “function animate()” and “  renderer.render()”; Terminal shows “$ whoami” and “jarvis”; Spotify shows “♫ Now Playing” and “Iron Man OST”. Animate the five windows continuously with their own slow horizontal/vertical velocities and reverse direction when reaching the bounded desktop area.

Right interaction: clicking the desktop canvas attempts to identify the nearest application window whose center is within about 65 canvas pixels of the click. If one is found, append a JARVIS log entry containing its label and database description: “CHROME — Web browser, 12 tabs open”; “FILE EXPLORER — Accessing Documents folder”; “VS CODE — Editing game.js (unsaved changes)”; “TERMINAL — bash running (user@jarvis)”; or “SPOTIFY — Playing: Iron Man soundtrack”. Mark identified apps, update the Objects counter to the number of unique identified apps, and briefly highlight the selected object if desired. If no nearby object is found, append “No clear object at clicked position”.

At the bottom of the right pane, reserve a compact approximately 110px-high system-log strip with cyan top border. Put SCAN ALL and CLEAR buttons at the top. SCAN ALL logs “Scanning desktop stream...” and shortly afterward logs the database description of all five applications and marks all five identified. CLEAR resets the identified count to 0 and replaces the log with “Log cleared”. Keep a scrollable SYSTEM LOG area showing only the most recent roughly eight entries. On startup, log “System ready. Drag on left view for body tracking.” and “Click on right desktop to identify moving objects.”

Make the interface responsive: the two panes fill the viewport below the header, the 3D renderer resizes with the left pane, and the desktop canvas resizes with the right pane. The intended experience is a non-combat Iron Man/JARVIS monitoring console focused on rotating/inspecting the red suit and identifying moving desktop applications, with no score, health, ammunition, enemies, or win/lose state.