Menu
Guides the creation of a new game and is the high-level orchestrator skill that MUST be invoked first. Use when tasked with creating a new game.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Enforces data governance by verifying Knowledge Catalog Aspects before recommending BigQuery tables.
Ensures the game has a fun easter egg that turns the screen black and white, sepia or gameboy monotone colours. Use when creating or modifying a game.
Ensures platformer games have polished movement, responsive controls, and balanced jump mechanics. Use ONLY when the game type is "platformer".
Arcade game must have a retro asthetic. Use when creating or modifying a game to ensure that the game looks retro and maintains a consistent look and feel with all games.
Game will always use the same control scheme/buttons and mapping of the gamepad and keyboard. Use when creating or modifying a game.
Helps the user make or modify a game. Use when the user wants to create a new game or modify an existing one.
| name | creating-a-game |
| description | Guides the creation of a new game and is the high-level orchestrator skill that MUST be invoked first. Use when tasked with creating a new game. |
Follow these steps FIRST when creating a new game:
Setup Workspace:
Copy the contents of the game-template directory recursively to a subfolder in the workspace with the name of the game as a folder-friendly name (e.g., my-game).
Since node_modules are installed globally, you do not need to install dependencies.
Use the run_command tool to copy the template:
cp -r /workspace/game-template /workspace/<game-name>
Develop the Game: Attempt to make the game using this newly copied folder as the base. Start modifying the source files to fulfill the user's game request.
messaging-game-overensuring-arcade-visualshandling-user-inputimproving-game-qualityadding-easter-eggbuilding-platformer-gamesValidation Loop:
After every code edit you make, you MUST run the build command to ensure the game compiles successfully.
Use the run_command tool to run the build:
cd /workspace/<game-name> && npm run build
Do not proceed to the next step or notify the user until compilation succeeds. Fix any compilation errors you encounter.
Play Testing:
Once the user has made changes and wants to test them, execute the playing-the-game skill to start the server and launch the browser.