remix-submission-rules
Submission Requirements
A version should be considered launch-ready only when all are true:
- Game code exists
- Game has name, icon, and >=1 category
- SDK hooks exist in code:
- HTML
<head>includes:<script src="https://cdn.jsdelivr.net/npm/@remix-gg/sdk@latest/dist/index.min.js"></script>
window.RemixSDK.singlePlayer.actions.gameOver(...)window.RemixSDK.onPlayAgain(...)window.RemixSDK.onToggleMute(...)
- HTML
Agent REST flow constraints
- Create a game draft via
POST /v1/games. - Update current version via
POST /v1/games/{gameId}/versions/{versionId}/code. - Do not create extra versions from agent REST (no create-version route).
- Do not submit from agent REST (no submit route).
More from farworld-labs/remix-skills
phaser-2d-arcade
Build mobile-first 2D browser games with Phaser 3 Arcade Physics
41remix-agent-publish
Build and publish Remix games with the current Remix toolchain. Use when work touches the official Remix CLI, MCP server, REST publishing APIs, or the @remix-gg/sdk game runtime.
39threejs-lite
Build lightweight mobile-friendly 3D browser games with Three.js
36remix-api-auth
Configure and verify authentication for Remix REST, CLI, and MCP workflows. Use when a task needs `REMIX_API_KEY`, `remix login`, stored Remix credentials, or auth troubleshooting.
34remix-shop-items
Create, update, delete, and integrate Remix shop items. Use when a game needs Bits items, consumables, one-time unlocks, tier unlocks, store icons, or purchase handling in @remix-gg/sdk code.
34remix-add-sprite
Generate and add sprites to a Remix game
33