ultimateplay://cabinet/glow-league-a-skateboard-racing-team-manager
LiveOpus 4.7Mobile Friendly

Glow League - A skateboard racing team manager

Create a single HTML file management game called GLOW LEAGUE. You manage a definitely-not-real neon skateboard racing team, with your two skaters, your wrench crew, your GPU engineering team and all. You develop board parts over the season โ€” GPU cores, motors, decks, wheels โ€” ...

by pokexpert30published May 22, 20260 upvotes
Remix Kit

Glow League - A skateboard racing team manager

Built with Opus 4.7

Create a single HTML file management game called GLOW LEAGUE. You manage a definitely-not-real neon skateboard racing team, with your two skaters, your wrench crew, your GPU engineering team and all. You develop board parts over the season โ€” GPU cores, motors, decks, wheels โ€” increasing stats such as compute (speed), thermals, torque, downforce, grip, all. Each new season there are rulebook changes making stats take a toll. Every stat is tracked (skater form, how good your engineers are and all) and the simulation is watch-only during the race (you can only see what the skaters are doing in fast forward on top-down neon circuits). You can create 8 tracks of various settings โ€” rooftops, tunnels, coastal, industrial, downtown, mountain, mall interiors, harbor. You need to take into account wheel management with street-hybrid and rain-grip compounds for damp/wet neon asphalt (with weather patterns tied to tracks). While you can pre-make the teams in the championship (make them 7 + player which is custom), do the most procedural data you can, with a seed that can be set on New Game+ so championship settings can be shared. Jam anchors, load-bearing: the neon skateboard is the racing vehicle (every visual and upgrade ties to the board). The GPU is the powertrain โ€” your engineering tree is a GPU dev tree, and thermals are a live race factor. GPU crates spawn as pickups on track; a pre-race "scavenger aggression" slider decides if skaters detour for them. Collected GPUs become R&D points. Rivals collect too. Saves in localStorage with export/import strings. Graphics simple 2D but readable, heavy CSS glow and canvas additive blending. Audio is Web Audio synthwave + synthesized motor whine. Self-contained visuals and audio only. No remote assets (CDN libs allowed). Touch-friendly mandatory: 44px minimum hit targets, portrait supported, all planning screens tap-only. Keyboard, mouse, gamepad also supported. The core of the loop is between-race planning.
This is a benchmark of your abilities, so don't ask any questions (you won't get answer if you do), so fill eventual gaps, add missing features or spec you think would be worth it.  Also, build it in interative loops with self-review (but in total autonomy), in case your answer get interrupted by a transitive backend error (and to improve it until you think it's perfect)
 Good luck Opus, make me proud !

No shared chat link was submitted for this game.

Open Player
Build Prompt

Create a single HTML file management game called GLOW LEAGUE. You manage a definitely-not-real neon skateboard racing team, with your two skaters, your wrench crew, your GPU engineering team and all. You develop board parts over the season โ€” GPU cores, motors, decks, wheels โ€” increasing stats such as compute (speed), thermals, torque, downforce, grip, all. Each new season there are rulebook changes making stats take a toll. Every stat is tracked (skater form, how good your engineers are and all) and the simulation is watch-only during the race (you can only see what the skaters are doing in fast forward on top-down neon circuits). You can create 8 tracks of various settings โ€” rooftops, tunnels, coastal, industrial, downtown, mountain, mall interiors, harbor. You need to take into account wheel management with street-hybrid and rain-grip compounds for damp/wet neon asphalt (with weather patterns tied to tracks). While you can pre-make the teams in the championship (make them 7 + player which is custom), do the most procedural data you can, with a seed that can be set on New Game+ so championship settings can be shared. Jam anchors, load-bearing: the neon skateboard is the racing vehicle (every visual and upgrade ties to the board). The GPU is the powertrain โ€” your engineering tree is a GPU dev tree, and thermals are a live race factor. GPU crates spawn as pickups on track; a pre-race "scavenger aggression" slider decides if skaters detour for them. Collected GPUs become R&D points. Rivals collect too. Saves in localStorage with export/import strings. Graphics simple 2D but readable, heavy CSS glow and canvas additive blending. Audio is Web Audio synthwave + synthesized motor whine. Self-contained visuals and audio only. No remote assets (CDN libs allowed). Touch-friendly mandatory: 44px minimum hit targets, portrait supported, all planning screens tap-only. Keyboard, mouse, gamepad also supported. The core of the loop is between-race planning. This is a benchmark of your abilities, so don't ask any questions (you won't get answer if you do), so fill eventual gaps, add missing features or spec you think would be worth it. Also, build it in interative loops with self-review (but in total autonomy), in case your answer get interrupted by a transitive backend error (and to improve it until you think it's perfect) Good luck Opus, make me proud !