mcpField
R
remix-submission-rules

remix-submission-rules

github.com/farworld-labsTesting & quality58 installs
Repository

About remix-submission-rules

A skill for agents building Remix games, documenting launch-readiness checks, metadata requirements, and REST workflow constraints. It also identifies endpoints for validating a version and checking aggregate readiness.

Key features

  1. 01Lists launch-readiness requirements
  2. 02Defines agent REST update constraints
  3. 03Explains metadata and asset handling
  4. 04Identifies validation and readiness endpoints

Use cases

  1. 01Check a game version for blockers
  2. 02Guide an agent updating existing version code
  3. 03Review overall readiness before submission

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/farworld-labs/remix-skills --skill remix-submission-rules

After installing, type/remix-submission-rulesin Claude Code to confirm it loaded.

Details

From the project README

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(...)

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).
  • Never update a live version.

Metadata requirements (current)

  • Name: set via existing game metadata APIs.
  • Category: add 1-3 categories via existing game metadata APIs.
  • Icon: upload in Remix Studio/app flow (no dedicated agent REST icon route yet).
  • Binary assets: upload in Remix Studio/app flow, then use GET /v1/games/{gameId}/assets to map hosted URLs into code.

Use GET /v1/games/{gameId}/versions/{versionId}/validate to confirm blockers. Use GET /v1/games/{gameId}/launch-readiness?versionId={versionId} when you want an aggregate readiness signal (valid + readyForSubmission).

Comments

Markdown supported