About remix-glossary
A glossary of terms used in Remix's game-version and launch-readiness APIs. It defines API keys, version states, validation results, launch readiness, and thread context for readers working with these endpoints.
Key features
- 01API-key definition
- 02Draft and live version states
- 03Validation and blocker terms
- 04Launch-readiness payload definition
- 05Version thread context
Use cases
- 01Interpret Remix API documentation
- 02Understand game-version validation results
- 03Review launch-readiness status fields
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ farworld-labs/ remix-skills --skill remix-glossaryAfter installing, type/remix-glossaryin Claude Code to confirm it loaded.
Details
From the project READMEGlossary
| Term | Definition |
|---|---|
| API Key | User-generated key from https://remix.gg/api-keys used for bearer auth (Authorization: Bearer <api_key>). |
| Draft | Editable game version state used by the agent REST flow. |
| Validation | Readiness checks for metadata + SDK hooks. |
| Blocker | Machine-readable issue returned from GET /v1/games/{gameId}/versions/{versionId}/validate. |
| Launch Readiness | Aggregate readiness payload from GET /v1/games/{gameId}/launch-readiness, including status, valid, and readyForSubmission. |
| Thread Context | Version thread payload from GET /v1/games/{gameId}/versions/{versionId}/thread with threadId and resolved HTML. |
| Status | Version state from status endpoint: draft, blocked, review, approved, or live. |
| Live Version | The currently launched version; cannot be modified by agent REST code updates. |
Comments
Markdown supported