Game Studio
For browser multiplayer in OhMyGame, use the platform's Colyseus + WebSocket service and server-authoritative rules. Use multiplayer_setup when available for local validation and read its generated SDK guide; local tests need no cloud deployment. Missing service configuration or game rules requires an explicit setup error. Do not silently substitute PeerJS, WebRTC, or public signaling services. An explicitly requested alternative stack takes precedence; explain its separate deployment requirements.
Preserve the user's chosen engine, platform, and existing project conventions. For a new game with no chosen stack, select a suitable runtime from the intended experience, target devices, available tools, and delivery needs. General Game is an engine-independent workspace; it does not require Web output.
Match The Task
create: deliver a complete playable core loop with clear controls, progression, success or failure, restart, intentional art, and player feedback.
feature: identify existing state owners and integration points, implement the requested behavior, and check nearby regressions.
bugfix: establish evidence, identify the cause, make a focused fix, and replay the affected flow.
polish: connect art, audio, input, or performance work to a specific player-facing improvement.
refactor: improve boundaries while preserving observable gameplay.
Discussion, design-only, graybox, no-generation, and explicitly requested procedural art override the corresponding creation defaults. Applications, tools, and content requests use an appropriate workflow rather than the full game creation process. A focused change does not require a redesign or new art unrelated to that change.
Create A Game
- Read the workspace. When game design or asset planning needs a canvas, use
canvas_initialize if none exists, then follow its instructions. Establish the player fantasy, primary actions, core loop, controls, progression, success/failure/restart behavior, first playable scope, and visual direction. Record the design and an asset list with gameplay roles, specifications, sources, and runtime destinations in the canvas main design document. Build on an existing design when present.
- Establish a cohesive palette, typography, composition, and feedback language. Use key-screen mockups when substantial visual decisions need them. Save canvas generation nodes with dimensions, purposes, and shared references; generate through
generate_canvas_media and inspect the outputs. Mockups guide implementation and do not fulfill the production asset list.
- Reuse suitable assets and generate missing production art for the game's main subjects and themed UI. Keep sprite identity, frame sizes, anchors, and timing consistent; normalize 3D scale, axes, pivots, materials, and animation names for the chosen engine. Use code drawing for simple geometry, particles, and dynamic UI, or for explicitly requested procedural art. Prepare and import assets through the engine's real pipeline, then integrate them into the playable loop. Keep significant implementation decisions reflected in the design document.
- Exercise the primary actions, progression, failure/restart, and affected device sizes using available runtime tools. Compare actual gameplay screenshots with the visual direction. Check the asset list against real files and runtime usage; mockups, empty generation nodes, and unused files do not establish completion. Fix shortcomings and repeat the affected checks.
When a required generation tool is unavailable or fails, use a coherent substitute and disclose the remaining gap. Implementation convenience alone is not a reason to replace required production art with placeholders. Do not retry an unchanged failing generation indefinitely.
Specialist Work
- For engine choice, state ownership, input, saving, or performance boundaries, read Game Foundations.
- For playtest scope, runtime evidence, regression paths, or visual QA, read Game QA.
- Use relevant installed engine Skills or Connections when available. Follow the workspace's own authoring contract, including Playable Nodes rules for Interactive Story. These optional enhancements do not replace the engine-independent workflow.
For a single-domain request, use the relevant specialist directly. Keep one plan and one definition of done for mixed work. Verification must match available tools; never claim gameplay or visual checks that were not performed.
1---2name: game-studio3description: Create complete games across engines by coordinating design, visual direction, production assets, implementation, and playtesting; use for new games or changes spanning several game-production domains.4metadata:5 source: https://skillmd.com/skills/whitetowerai/game-studio6---78# Game Studio910For browser multiplayer in OhMyGame, use the platform's Colyseus + WebSocket service and server-authoritative rules. Use `multiplayer_setup` when available for local validation and read its generated SDK guide; local tests need no cloud deployment. Missing service configuration or game rules requires an explicit setup error. Do not silently substitute PeerJS, WebRTC, or public signaling services. An explicitly requested alternative stack takes precedence; explain its separate deployment requirements.1112Preserve the user's chosen engine, platform, and existing project conventions. For a new game with no chosen stack, select a suitable runtime from the intended experience, target devices, available tools, and delivery needs. General Game is an engine-independent workspace; it does not require Web output.1314## Match The Task1516- `create`: deliver a complete playable core loop with clear controls, progression, success or failure, restart, intentional art, and player feedback.17- `feature`: identify existing state owners and integration points, implement the requested behavior, and check nearby regressions.18- `bugfix`: establish evidence, identify the cause, make a focused fix, and replay the affected flow.19- `polish`: connect art, audio, input, or performance work to a specific player-facing improvement.20- `refactor`: improve boundaries while preserving observable gameplay.2122Discussion, design-only, graybox, no-generation, and explicitly requested procedural art override the corresponding creation defaults. Applications, tools, and content requests use an appropriate workflow rather than the full game creation process. A focused change does not require a redesign or new art unrelated to that change.2324## Create A Game25261. Read the workspace. When game design or asset planning needs a canvas, use `canvas_initialize` if none exists, then follow its instructions. Establish the player fantasy, primary actions, core loop, controls, progression, success/failure/restart behavior, first playable scope, and visual direction. Record the design and an asset list with gameplay roles, specifications, sources, and runtime destinations in the canvas main design document. Build on an existing design when present.272. Establish a cohesive palette, typography, composition, and feedback language. Use key-screen mockups when substantial visual decisions need them. Save canvas generation nodes with dimensions, purposes, and shared references; generate through `generate_canvas_media` and inspect the outputs. Mockups guide implementation and do not fulfill the production asset list.283. Reuse suitable assets and generate missing production art for the game's main subjects and themed UI. Keep sprite identity, frame sizes, anchors, and timing consistent; normalize 3D scale, axes, pivots, materials, and animation names for the chosen engine. Use code drawing for simple geometry, particles, and dynamic UI, or for explicitly requested procedural art. Prepare and import assets through the engine's real pipeline, then integrate them into the playable loop. Keep significant implementation decisions reflected in the design document.294. Exercise the primary actions, progression, failure/restart, and affected device sizes using available runtime tools. Compare actual gameplay screenshots with the visual direction. Check the asset list against real files and runtime usage; mockups, empty generation nodes, and unused files do not establish completion. Fix shortcomings and repeat the affected checks.3031When a required generation tool is unavailable or fails, use a coherent substitute and disclose the remaining gap. Implementation convenience alone is not a reason to replace required production art with placeholders. Do not retry an unchanged failing generation indefinitely.3233## Specialist Work3435- For engine choice, state ownership, input, saving, or performance boundaries, read [Game Foundations](../game-foundations/SKILL.md).36- For playtest scope, runtime evidence, regression paths, or visual QA, read [Game QA](../game-qa/SKILL.md).37- Use relevant installed engine Skills or Connections when available. Follow the workspace's own authoring contract, including Playable Nodes rules for Interactive Story. These optional enhancements do not replace the engine-independent workflow.3839For a single-domain request, use the relevant specialist directly. Keep one plan and one definition of done for mixed work. Verification must match available tools; never claim gameplay or visual checks that were not performed.