Cloud Lab

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 full-screen, fixed-camera 2D top-down arcade collection game titled “Cloud Lab.” Use an HTML canvas that fills the viewport and scales responsively, with crisp pixel-art rendering and a dark navy-to-blue vertical gradient background. The playfield is an enclosed storm laboratory: a thin cyan horizontal boundary near the top, a dark blue floor strip along the bottom with repeating cyan marks, drifting pale pixel clouds, small twinkling yellow/blue atmospheric pixels, and a central raised lab platform around the middle of the arena. The platform is a dark indigo horizontal rectangle with yellow end markers, two cyan equipment blocks with dark inset windows, and small pink components beneath it.

The player is a small pixel-art weather laboratory robot in the arena: a dark navy rectangular body, bright cyan face/screen, two dark square eyes, yellow feet, and a pink antenna topped with a tiny pale-blue tip. Start the robot near the center of the screen. Move it with ArrowUp, ArrowDown, ArrowLeft, and ArrowRight on keyboard; movement accelerates toward the selected direction and has friction when released. Also provide an on-screen D-pad in the bottom-left with ▲, ◀, ▼, and ▶ buttons for touch/pointer controls. Keep the player inside the arena boundaries.

Place exactly 10 collectible weather sparks at random positions within the play area, avoiding the HUD region and edges. Render each uncollected spark as a rotating yellow pixel cross with a lighter center. When the robot comes within collection range, mark the spark collected, increment the counter, fill the progress meter proportionally, and emit a burst of small yellow particles. The objective is to collect all 10 sparks. On collecting the tenth, stop gameplay, show the win state, change the sector label to “CLOUD CORE ONLINE,” and display the centered message “☁ CLOUD CORE STABILIZED ☁” with “Press R to run the lab again” beneath it.

Create recurring storm bolts as pink jagged lightning segments traveling from a point near the upper boundary toward a random point lower in the arena. Fade bolts out over about one second. If a bolt comes within collision range of the robot while the pulse is inactive, damage the robot and emit pink particles. The robot has 3 health points; health is not shown in the visible HUD, but losing all three ends the run. On defeat, stop gameplay, change the sector label to “SYSTEM OFFLINE,” and show “⚠ STORM OVERLOAD ⚠” with “Press R to reboot the lab” beneath it. Press R after either terminal state to restart with a fresh arrangement and reset score and health.

Give the player an ability called PULSE, activated with the Space key or by pressing a large circular pink “PULSE” button in the bottom-right. PULSE should create a brief expanding gold ring around the robot, emit gold particles, and remove nearby storm bolts within roughly 110 pixels. It should not operate after winning or losing. The pulse button and all touch controls must prevent page scrolling and support pointer input.

Use a minimal retro-futurist HUD over the canvas. At the top-left, show a cyan-outlined dark panel reading “CLOUD LAB SECTOR 01” (with the sector/status text changing in terminal states). At the top-right, show a matching panel reading “SPARKS 0/10” and a horizontal outlined meter whose gold fill grows from 0 to 100 percent as sparks are collected. Center near the upper portion of the playfield, show the instruction text: “Collect the 10 weather sparks · PULSE clears nearby storm bolts.” Use a monospaced typeface, pale blue-white text with subtle dark shadow, cyan borders, pixelated/blocky shapes, and a palette of navy, cyan, pale cloud blue, yellow, and pink. Keep the HUD and touch controls layered above the canvas, with the D-pad bottom-left and PULSE bottom-right. Do not add additional enemies, weapons, levels, camera scrolling, or mechanics beyond this single-sector collection run.