Each kit includes TypeScript source, a small playable scene, local development tools, and a production build. Not sure where to start? Choose Phaser for a simple 2D game. You can edit every part of the game.
Download the ZIP from a kit page and extract it into a new folder. Open the extracted project folder containing package.json in your editor. Use the kit builder if you want to choose your own combination of tools.
Open a terminal in the project folder, then install its dependencies and start the development server.
Open the local address printed in the terminal. In the starter scene, use the arrow keys to move and collect gold. Leave the terminal running while you edit; stop the server with Ctrl+C.
Start with one visible change: update the heading in index.html, save it, and check the browser. Then open src/main.ts to change the scene, artwork, or game behavior.
| File or folder | What it controls |
|---|
src/main.ts | The entry point for your chosen rendering engine. |
|---|
src/ | Game logic and any selected simulation modules. |
|---|
public/ | Static artwork, audio, and other game assets. |
|---|
spawnkit.config.ts | The title, description, and media for your game listing. |
|---|
package.json | Installed dependencies and available commands. |
|---|
AGENTS.md | Project instructions for your coding agent. |
|---|
Working with an agent? Open the project in your agent and have it read AGENTS.md before editing. For the reusable create, extend, and publish workflow, see Agent resources.
Run these checks before sharing a build. Curated kits include browser-based Vitest tests; Chromium only needs to be installed once on each machine.
pnpm lint
pnpm test
pnpm build
A successful build creates dist/, the files your players will load. Keep the pnpm-lock.yaml created during installation so future installs use the same resolved dependencies.
- Play through the starter scene and check movement and scoring.
- Resize the browser and check that the game stays usable.
- Check the browser console for errors.
- If you chose a custom kit, run only the test scripts included in its
package.json.
Ready to share? Follow Publish your game to upload your browser build.
| What you see | What to try |
|---|
pnpm or node is not recognized | Install the required tool, reopen your terminal, and check its version. |
|---|
| The local address does not open | Keep the development terminal running. Run pnpm exec dev-domains doctor, or use pnpm exec vite for a plain local server. |
|---|
| Tests cannot find a browser | Run pnpm test:setup, then retry pnpm test. |
|---|
| The page is blank | Check the terminal and browser console. Confirm you opened the development URL, rather than opening index.html directly. |
|---|