Use this when
This is the canonical Buncha Games page to give to Codex, Claude, Gemini, Cursor, or another local coding agent.
Use /developers/docs/agent-upload as supporting detail when the agent needs more upload background.
The agent should work in the game repo and use the Buncha Games CLI when a developer API token is available.
Copy-paste prompt
You are preparing my browser game for Buncha Games.
Work only in this game repo unless I explicitly say otherwise. Do not edit the Buncha Games platform repo. Do not use direct Cloudflare, R2, Supabase, database, or admin shortcuts.
Goal:
1. Build/export the browser-playable production web version.
2. Package only the exported web build contents into a ZIP with index.html at the ZIP root.
3. Verify the build from a local static server when the engine uses WASM, loaders, or relative assets.
4. Use the Buncha Games Developer CLI for listing status, listing create/update, build upload, media upload/management, external-domain requests, and review submission when BUNCHA_GAMES_API_TOKEN is available.
Rules:
- Never print, echo, log, commit, or ask me to paste BUNCHA_GAMES_API_TOKEN.
- Upload the exported browser build only, not the source project.
- Do not include .env files, hidden files, node_modules, source project folders, server files, private keys, access tokens, or unrelated files.
- Bundle engine/library scripts locally. Do not depend on remote script tags from CDNs.
- Do not add external ads, payments, crypto, NFTs, phishing, malware, obfuscated payloads, or provider checkout scripts.
- Disclose required external domains through the CLI domain request command before review.
- Submit for review only after I explicitly confirm the required rights, content, external-services, and terms attestations.
Recommended CLI commands:
- npm exec --yes --package @bunchagames/cli -- buncha-games games status --site https://bunchagames.com --game-slug <slug> --json
- npm exec --yes --package @bunchagames/cli -- buncha-games games create --site https://bunchagames.com --manifest ./buncha-game-manifest.json --json
- npm exec --yes --package @bunchagames/cli -- buncha-games games update --site https://bunchagames.com --game-slug <slug> --manifest ./buncha-game-manifest.json --json
- npm exec --yes --package @bunchagames/cli -- buncha-games upload --site https://bunchagames.com --game-slug <slug> --file ./dist/game.zip --json
- npm exec --yes --package @bunchagames/cli -- buncha-games media upload --site https://bunchagames.com --game-slug <slug> --type screenshot|thumbnail|hero --file <path> --alt "<clear alt text>" --json
- npm exec --yes --package @bunchagames/cli -- buncha-games media reorder --site https://bunchagames.com --game-slug <slug> --media-ids <id-1>,<id-2>,<id-3> --json
- npm exec --yes --package @bunchagames/cli -- buncha-games domains request --site https://bunchagames.com --game-slug <slug> --domain <host> --service-type <type> --service-name "<name>" --purpose "<purpose>" --json
- npm exec --yes --package @bunchagames/cli -- buncha-games review submit --site https://bunchagames.com --game-slug <slug> --content-disclosure "<summary>" --rights-confirmed --content-policy-confirmed --external-services-confirmed --terms-accepted --json
Optional SDK:
- Web/Phaser/Three/Vite: npm install @bunchagames/sdk.
- Unity WebGL: use the Buncha Games Unity UPM tarball linked from /developers/docs/sdk.
- Godot Web: use the Buncha Games Godot addon ZIP linked from /developers/docs/sdk.
- SDK calls must fail soft outside Buncha Games. Do not add real payments, real ads, payout logic, or production monetization assumptions.
Return:
1. commands run,
2. build/export folder,
3. ZIP path, ZIP tree, and inspection result,
4. local smoke-test result,
5. CLI JSON summaries or concise parsed status results,
6. any external domains that need approval,
7. whether review submission is ready or blocked.Stack variants
- Manual web upload: build/export the game, inspect the ZIP, then use the Developer Dashboard file picker.
- CLI-assisted web upload: use the Buncha Games CLI for status, listing metadata, build upload, media, domains, and review submission.
- Unity WebGL: export WebGL from Unity, ZIP the export folder contents, and use the Unity UPM tarball only if adding optional SDK calls.
- Godot Web: export the web build, ZIP the HTML5 output contents, and use the Godot addon ZIP only if adding optional SDK calls.
- All stacks: keep SDK and CLI usage optional unless the human explicitly asks for those integrations.
Human checklist before running the prompt
- Confirm the game repo is the active working folder.
- Create a Buncha Games developer API token only if a CLI path is needed.
- Put the token in the local environment as BUNCHA_GAMES_API_TOKEN without committing it.
- Prepare listing copy and media files if you want the agent to create or update a listing.
- Review any external-domain requests before asking for review submission.
Where agents should look next
- CLI commands: /developers/docs/cli
- Manual upload path: /developers/docs/upload-without-cli
- Build packaging: /developers/docs/uploading-games
- Engine exports: /developers/docs/engine-export-notes
- SDK install paths: /developers/docs/sdk
- Agent-readable context: /developers/docs/agent-context.md
- Plain agent index: /developers/docs/llms.txt