remix-game-creation
Create a new game draft via the Remix API
Best use case
remix-game-creation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a new game draft via the Remix API
Teams using remix-game-creation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/remix-game-creation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How remix-game-creation Compares
| Feature / Agent | remix-game-creation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a new game draft via the Remix API
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Game Creation Workflow
## Overview
This skill guides you through creating a new HTML game on the Remix platform.
## Prerequisites
- The `REMIX_API_KEY` environment variable must be set.
## Constraints
- The game must target a **2:3 aspect ratio** (e.g. 720x1080).
- It must fill the entire viewport at that ratio -- use `width: 100vw; height: 100vh`
on the game container. No scrollbars, no overflow.
- The game **must support touch controls** as the primary input method (the Remix
platform is primarily mobile/touch-based). Keyboard and mouse controls are
welcome but optional.
## Steps
### 1. Plan the Game
Decide on the game concept, mechanics, and visual style. Keep scope small --
a single-file HTML game should be playable in under 30 seconds.
### 2. Write the HTML
Create a single HTML file with inline `<style>` and `<script>` tags. Structure:
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Game Title</title>
<script src="https://cdn.jsdelivr.net/npm/@remix-gg/sdk@latest/dist/index.min.js"></script>
<style>
/* Game styles can go here */
</style>
</head>
<body>
<!-- Game markup can go here -->
<script>
// Game logic here
</script>
</body>
</html>
```
### Required RemixSDK Functions
1. **`window.RemixSDK.singlePlayer.actions.gameOver({ score })`** -- Call when the game
ends, passing the player's final score as `{ score: number }`. This reports
the score to the platform.
2. **`window.RemixSDK.onPlayAgain(callback)`** -- Register a callback (no arguments)
that fires when the player requests to play again. The callback should reset
game state and restart the game.
3. **`window.RemixSDK.onToggleMute(callback)`** -- Register a callback that receives
`{ isMuted: boolean }`. The game must mute or unmute all audio based on the
`isMuted` value.
### 3. Validate
Before uploading, read the HTML file and verify:
1. Has `<!DOCTYPE html>` declaration
2. Has `<meta name="viewport" ...>` tag
3. Has RemixSDK script tag: `<script src="https://cdn.jsdelivr.net/npm/@remix-gg/sdk@latest/dist/index.min.js"></script>`
4. No legacy `@farcade/game-sdk` script tag
5. Calls `singlePlayer.actions.gameOver(` OR `multiplayer.actions.gameOver(` (not both)
6. Registers `.onPlayAgain(` callback
7. Registers `.onToggleMute(` callback
8. No `localStorage` or `sessionStorage` usage
9. No inline event handlers (`onclick=`, `onload=`, etc.)
Fix any issues before proceeding.
### 4. Upload the Game
Follow the **upload-game** workflow to create the game on the Remix platform and
deploy your HTML code.
## Tips
- Use `requestAnimationFrame` for game loops, not `setInterval`.
- Touch controls are required (primary input); keyboard/mouse are optional extras.
- Keep the total HTML under 100KB for fast loading.Related Skills
remix-upload-game
Upload and validate HTML game code for Remix. Use when creating or updating a draft version through the CLI, MCP tools, or direct REST calls.
remix-upload-asset
Upload images, audio, or 3D models as hosted game assets
remix-submission-rules
Validation and publish constraints for Remix game submissions
remix-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.
remix-save-game
Add save and load game state functionality via RemixSDK
remix-rest-snippets
REST client snippets for Remix agent publishing
remix-open-game
Open a game in the Remix Studio browser for preview and editing
remix-multiplayer
Enable multiplayer support for a Remix game
remix-game-sdk
Reference for the current @remix-gg/sdk runtime. Use when generating or repairing Remix game code, shop item integrations, save-state flows, multiplayer hooks, or host-safe mobile UI behavior.
remix-game-best-practices
Mobile-first game creation best practices for Remix
remix-cli
Use the official Remix CLI for authentication, config inspection, game creation, uploads, and analytics. Trigger this skill when a task involves `remix login`, `remix whoami`, `.remix-cli.json`, `REMIX_API_KEY`, or terminal-based game management on Remix.
remix-api-reference
OpenAPI-first endpoint reference for Remix game publishing REST routes