Your idea. A playable browser game.

Create <GAME>.

Read and follow the aigamelabs-game-publishing skill. Use the authenticated AIGameLabs MCP server at https://aigamelabs.net/mcp for the real publishing workflow, not simulated tool results.

Implement a complete, playable WebGL/browser demo with clear controls, a core gameplay loop, and restart/win/lose states appropriate to the game. Choose a web-capable stack such as a web-native engine, Canvas/WebGL, or a supported Unity/Godot web export. Do not assume stock Unreal Engine 5 can export WebGL; it has no official HTML5/WebGL target. Use original or properly licensed game assets and bundle all runtime dependencies locally. Keep the build single-threaded, with no workers, service workers, or external runtime requests, and follow the skill's sandbox and size limits.

Run the actual production build in a browser, play through the core loop, inspect the console, and fix problems. Package the tested static output as the skill requires: a ZIP with index.html at its root and relative asset paths. Do not upload an untested build.

Use AIGameLabs MCP to create my private game draft, upload the finished build, upload cover artwork and actual gameplay screenshots, and fill in accurate metadata, controls, supported devices, and AI-use disclosures. Open and exercise the private preview returned by preview_build in the real player sandbox; fix issues before requesting review. Do not claim that an upload, preview, or review succeeded without observing its result.

Record the game's actual or estimated creation cost in USD only when the token, tool, and asset costs are known. Clearly distinguish an estimate from a measured total; leave the creation cost unspecified rather than inventing a number. This is the cost to create the game, not a price to play it.

Before asserting rightsAccepted: true, ask me to explicitly confirm that I own or have permission to distribute all code, game assets, artwork, music, and text, and that the AI-use disclosures are accurate. This prompt is not that rights confirmation.

I explicitly authorize autoPublish: true on create_release for the exact tested build and reviewed metadata/artwork, so that release may publish automatically only after moderator approval. After my rights confirmation, freeze that release and use submit_release to send it for human review. Do not bypass moderation or claim immediate public publication.

Give me the private preview link, an honest summary of what you tested, the draft/release status, and any remaining action I must take. If authentication, creator access, rights confirmation, quotas, or moderator feedback blocks a step, explain it and wait for the required action. Never ask me to paste OAuth tokens or account credentials into chat.