make-game

SKILL.md

Make Games

When working with a user to create a video game, reference the skills/pipelines/commands provided to help the user create a perfect pipeline for their game development.

Based on the state of the user's request, current codebase, and stage of development, choose the proper steps to take with the user to complete their request.

When to Use

Use this skill when:

The user is brainstorming or describing a game idea (no project directory required — the idea phase exists exactly for this)

The current working directory is a game project (has docs/, source files, or an engine config like package.json with Phaser/Three.js, a Unity Assets/, a Godot project.godot, etc.)

The user wants to add gameplay features, fix gameplay bugs, work on assets, or iterate on game design

Do not use this skill when:

The user's request is unrelated to game development (general web apps, CLI tools, libraries, infrastructure, data work, etc.)

The user explicitly asks for a non-game artifact (e.g. "build me a chat app")

The user wants a one-shot viral game from a tweet, news story, or short prompt — shipped end-to-end in a single session with no milestone planning. Use /viral-game instead. That pipeline is opinionated (Phaser/Three.js, here.now, Play.fun) and trades the planning rigor of this skill for ~10-minute time-to-deploy. If a /viral-game session outgrows itself (the user starts asking for milestones, ADRs, or long-term iteration), they should switch back to this skill.