Your First Game
From nothing to a published Post in about ten minutes: one opinionated path, with a deep-dive link at every step.
How this guide works
One starter, one build loop, one validation pass, one upload. Every step links to the article that covers it in depth. Two things this page never does:
- Restate the platform rules: every constraint lives in Platform Requirements; when a step says "validate", that page is the checklist.
- Require a terminal: you can download a starter as a ZIP and work with it in an AI tool without using the command line.
New to the platform entirely? Read the Creator Guide first.
Step 1: Pick a starter (~1 minute)
Pick exactly one:
Option A: a starter template. Project structure and SDK wiring already correct; your AI tool (or you) only fills in the game:
- minit-template-vanilla: plain Canvas/DOM
- minit-template-pixi: PixiJS
- minit-template-phaser: Phaser
- minit-template-three: Three.js
Clone one with git, or use GitHub's Code → Download ZIP button and unpack (no terminal needed). Unsure which? See the template notes in Build with AI Tools.
Option B: the Minit MCP scaffold. With the Minit MCP server connected, ask your AI tool to scaffold a project (minit_scaffold_project). Same kind of starter, generated in your workspace.
Step 2: Describe and build the game (~5 minutes)
Tell your AI tool what to build in one thorough prompt: mechanic, win/loss condition, difficulty curve, visual style. Don't write it from scratch. Paste the universal prompt from Build with AI Tools and fill in your game concept.
- Using any AI tool (Claude Code, Codex/ChatGPT, Cursor, Lovable, Gemini, …)? Build with AI Tools is tool-agnostic and includes the per-tool gotchas.
Iterate in the same conversation with specific, measurable feedback: "make the touch targets twice as large" beats "make it better".
Step 3: Validate (~2 minutes)
- Minit MCP connected: ask your assistant to fetch the live rules (
minit_get_requirements), run the validator (minit_validate_build), and fix what it reports. Setup: Minit MCP Server. - No MCP? Walk the Platform Requirements checklist yourself; the manual sweep is in Build with AI Tools.
Either way, play the game on a real phone before shipping. See Testing Your Game on Device.
Step 4: Zip, upload, publish (~2 minutes)
Zip it. Zip the contents of your build folder, not the folder itself: index.html must sit at the root of the Zip, and every script it references must be in the Zip as built output (the one exception is an MRAID playable's mraid.js reference — see Platform Requirements). The console validates each upload against Platform Requirements and names anything that trips a rule; fix and re-upload. Building a single self-contained .html file with no external script or asset references? Upload it directly — Studio zips it for you client-side.
Upload it. Click + Create (top right) → Upload game and follow the 3-step wizard: Upload build → Game details → Post. A meta.json at the Zip's root pre-fills your title and scoring (see Config Values).
Publish it. The wizard's last step is the post: Post now, Keep it private (draft), or Schedule for later (up to 4 weeks out).
What next
- Sharpen your post: Writing & formatting your Game description.
- Let your assistant upload and schedule next time: Minit MCP Server.
- Go deeper on the SDK: start at Install.