Quick Game

Organization

PlayableIntelligence

quick-game

Rapidly scaffold and implement a playable game — no assets, design, audio, deploy, or monetize. Get something on screen fast. Use when the user says "quick game", "fast prototype", "just get something playable", or wants a game without the full pipeline. For the complete one-shot pipeline (deploy + monetize), use /viral-game instead. For a milestone-driven project, use /make-game. Do NOT use for production games.

Overview

Publisher	PlayableIntelligence
Repository	`game-creator`
Skill name	`quick-game`
Stars	331
Forks	41
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by PlayableIntelligence on GitHub. Read the source before you install it.

Installation

Install the Quick Game AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/PlayableIntelligence/game-creator.git /tmp/game-creator
mkdir -p .claude/skills
cp -r /tmp/game-creator/skills/quick-game .claude/skills/quick-game

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Quick Game in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Quick Game on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Quick Game is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Performance Notes

Take your time to do this thoroughly
Quality is more important than speed
Do not skip validation steps

Quick Game (Fast Prototype)

Build a playable game prototype as fast as possible. This is /viral-game without the polish — just scaffold + implement the core loop. Get something on screen, then incrementally add layers with /add-assets, /design-game, /add-audio, /game-deploy, and /monetize-game.

What you'll get:

A scaffolded game project with clean architecture
Core gameplay — input, movement, scoring, fail condition, restart
A running dev server you can play immediately

What you skip (run these later if you want):

/add-assets — pixel art sprites (2D) or 3D models
/design-game — visual polish, particles, transitions
/add-audio — music and sound effects
/record-promo — promo video capture
/game-deploy — deploy to here.now
/monetize-game — Play.fun integration

Instructions

Step 0: Parse arguments

Parse $ARGUMENTS to determine the game concept:

Direct specification: [2d|3d] [game-name]

Engine: 2d (Phaser) or 3d (Three.js). If not specified, default to 2d.
Name: kebab-case. If not specified, ask the user.

Tweet URL: If arguments contain a tweet URL (x.com/*/status/*, twitter.com/*/status/*, fxtwitter.com/*/status/*):

Fetch the tweet using the fetch-tweet skill
Default to 2D
Creatively abstract a game concept from the tweet
Generate a kebab-case name
Tell the user what you'll build

Meshy API Key (3D only): If 3D, check for MESHY_API_KEY. If missing, ask the user (link to https://app.meshy.ai). Store for model generation.

Step 1: Scaffold + Implement

Infrastructure (main thread):

Locate the template directory — check ~/.claude/plugins/cache/local-plugins/game-creator/*/templates/ or templates/ relative to this plugin
Target directory: If inside the game-creator repo, create in examples/<game-name>/. Otherwise, create in ./<game-name>/.
Copy the template:
- 2D: templates/phaser-2d/ → target
- 3D: templates/threejs-3d/ → target
Update package.json name and index.html title
Run npm install
Start the dev server (npm run dev) in the background. Check port availability first — if 3000 is taken, try 3001, 3002, etc.

Game implementation (subagent via Task):

Launch a Task subagent with:

You are building a quick game prototype. Speed is the priority — get a playable core loop working.

Project path: <project-dir> Engine: <2d|3d> Game concept: <description> Skill to load: phaser (2D) or threejs-game (3D)

Implement in this order:

Input (touch + keyboard from the start)

Player movement / core mechanic

Fail condition (death, collision, timer)

Scoring

Restart flow (GameState.reset() → clean slate)

Scope: 1 scene, 1 mechanic, 1 fail condition. Keep it tight.

Rules:

All cross-module communication via EventBus

All magic numbers in Constants.js

No title screen — boot directly into gameplay

No in-game score HUD — Play.fun widget handles score display

Mobile-first input: touch + keyboard, use unified InputSystem pattern

Import SAFE_ZONE from Constants.js — keep UI below SAFE_ZONE.TOP

Minimum 7-8% canvas width for collectibles/hazards

Character sizing: GAME.WIDTH * 0.12 to GAME.WIDTH * 0.15 for character-driven games

Preserve the template's createButton() helper in GameOverScene — do NOT rewrite it

Wire spectacle events: SPECTACLE_ENTRANCE, SPECTACLE_ACTION, SPECTACLE_HIT, SPECTACLE_COMBO, SPECTACLE_STREAK, SPECTACLE_NEAR_MISS

Add isMuted to GameState for future audio support

Ensure restart is clean — 3 restarts in a row should work identically

Step 2: Verify

After the subagent returns:

Run npm run build in the project directory to confirm no errors
If the build fails, fix the issues (up to 2 retries)
If Playwright MCP is available, navigate to the dev server, take a screenshot, and do a quick visual check

Example Usage

2D game


/quick-game 2d asteroid-dodge

Result: Copies Phaser template → implements player ship, asteroid spawning, collision death, score counter, restart flow → dev server running at localhost:3000 in ~2 minutes. Shapes only, no polish.

From tweet


/quick-game https://x.com/user/status/123456

Result: Fetches tweet → abstracts game concept → scaffolds and implements a playable prototype inspired by the tweet content.

Troubleshooting

Game scaffolds but won't start

Cause: Vite config or import paths incorrect. Fix: Verify vite.config.js has correct root. Check that main.js is referenced in index.html.

Missing core files

Cause: Scaffold skipped EventBus/GameState/Constants. Fix: Every game needs core/EventBus.js, core/GameState.js, core/Constants.js. Re-run scaffold or create manually.

Done

Tell the user:

Your game is running at http://localhost:<port>. Open it in a browser to play!

To keep building, run these commands:

/add-assets — replace shapes with pixel art sprites

/design-game — add visual polish (particles, gradients, juice)

/add-audio — add music and sound effects

/game-deploy — deploy to the web

/monetize-game — add Play.fun integration

Or run /viral-game next time for the full one-shot pipeline (assets, polish, deploy, monetize all in one go).

Frequently asked questions

What does the Quick Game AI skill do?

Why use Quick Game on TypingMind?

Because you install it once and use it with any model. Quick Game is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Quick Game in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/PlayableIntelligence/game-creator/tree/main/skills/quick-game. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Quick Game?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Quick Game?

As many as you like. As long as a model supports skills, you can use Quick Game with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Quick Game AI skill free?

Yes. It is published on GitHub by PlayableIntelligence under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Discover

JuliusBrussee

CommunityPopular

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

Caveman Manage

Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.

Caveman Setup

Wire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.

Eng Runbook

An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Performance Notes

Quick Game (Fast Prototype)

Instructions

Step 0: Parse arguments

Step 1: Scaffold + Implement

Step 2: Verify

Example Usage

2D game

From tweet

Troubleshooting

Game scaffolds but won't start

Missing core files

Done

Frequently asked questions

Related AI Skills

Set up your own AI workspace now