Skyline Skirmish

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 2D top-down arena shooter called “Skyline Skirmish,” implemented as a responsive HTML canvas game with no scrolling camera: the entire playfield fits the viewport and resizes with the browser. Use a dark navy background (#101936) overlaid with a subtle blue 40-pixel square grid. Place six static horizontal blue platforms/walls as rectangular obstacles: two near the upper left and upper right, two near the lower left and lower right, and two narrower platforms centered around the middle-upper and middle-lower areas. Walls have a darker blue body and a brighter blue highlight strip along their top edge. They block movement and bullets.

The player starts at the center of the arena as a cyan/sky-blue circular character about 18 pixels in radius. Give the player a small pale-cyan rectangular gun projecting from the circle in the direction they are aiming, plus a dark blue marking on the opposite side. Aim toward the mouse/pointer using the angle from the player to the pointer. Move with WASD or arrow keys, with collision against the screen edges and platforms. Holding Shift performs a brief high-speed dash (roughly 500 movement speed for about 0.65 seconds, with cyan particle effects); otherwise movement is about 190 speed. Include a simple particle burst effect for dashes and hits.

The goal is to survive and destroy continuously spawning hostile circular enemies. Enemies enter randomly from one of the four screen edges, are pink/red circles about 16 pixels in radius, and pursue the player while avoiding the platforms and screen boundaries. Each enemy has 2 hit points, a small dark health-bar background above it and a pink health bar that visibly decreases after hits. Enemies rotate toward the player and have a pale pink rectangular gun/extension pointing at the player, along with a dark red interior marking. They periodically fire orange-red bullets toward the player, and touching an enemy damages the player continuously. Enemy bullets also damage the player on collision.

The player fires small yellow bullets toward the current aim direction by holding the mouse button; pressing Enter can also fire. Fire at roughly 0.16-second intervals, consume one round per shot, and start with 12 ammo. When ammo reaches zero, refill it to 12 after about half a second. Player bullets travel quickly (about 560 speed), enemy bullets more slowly (about 260 speed), expire after a short lifetime, leave the screen, or hit a wall. Player bullets deal one damage to enemies; killing an enemy awards 100 score and creates a larger pink burst. Use small square particle fragments for impact and dash effects. The player begins with 100 HP. Enemy contact drains HP over time and an enemy bullet deals a fixed 8 HP hit; when HP reaches zero, stop gameplay and show a centered “YOU LOST” message with “Press R to restart” below it. Pressing R resets the player, score, HP, ammo, enemies, bullets, particles, and spawn timing.

Use a clean neon arcade visual style: flat geometric vector shapes, high contrast cyan player, hot pink enemies, yellow player projectiles, orange enemy projectiles, blue barriers, and a navy grid arena. Add light synthesized arcade beeps for firing, enemy firing, dash, kills, reset, and defeat where browser audio permits it.

Add a fixed HUD over the canvas: bold white “SCORE 0” at the upper-left, “HP 100” centered along the top, and “AMMO 12” at the upper-right, updating live with the game state. At the top center below the HUD, show a translucent rounded instruction pill reading “WASD / arrows to move · mouse to aim · click to fire.” On coarse-pointer/touch devices, show mobile controls: a translucent circular movement stick at bottom-left, a round red FIRE button at bottom-right, and a cyan DASH button just to its left. The mobile stick should map directional dragging to movement, FIRE should hold the firing state and aim generally in the player’s current facing direction, and DASH should trigger the same short boost. Keep the interface responsive, hide overflow, support safe-area insets, and preserve the minimalist full-screen presentation.