Three guides, in the order you will need them. Written by people who ship browser games and have made every mistake described in them at least twice.
A working process, not a prompt list: scoping something you can finish, picking a stack, the prompting patterns that hold up on game code, and the debugging loop that gets you to playable.
You can read code but have never shipped a game.
Read the guideWhere to host it, what a custom domain actually costs you, how embedding works, why mobile input will eat a day, and the load-time budget that decides whether anyone plays it.
The game works on your machine. Now it needs a URL.
Read the guideThe tactical version: choosing a day, writing a tagline that earns a click, screenshots that convert, what to do in the first hour, and the mistakes that quietly cost you the front page.
It is hosted, it works, and nobody has played it.
Read the guideEvery tool credited by a published game, with live counts.