How to use these prompts
Use these prompts one step at a time. Start with the setup prompt, then come back for SDK integration, export packaging, media preparation, CLI upload, or ongoing game management.
Each prompt assumes the agent is working in your game repo, not the Buncha Games platform repo. The agent should never print secrets, bypass Buncha Games APIs, or use direct Cloudflare, R2, Supabase, or admin shortcuts.
Getting Started with Buncha Games
You are helping me understand and prepare this browser game for Buncha Games.
Start here:
- Full docs archive: https://bunchagames.com/developers/docs/all
- Quickstart: https://bunchagames.com/developers/docs/quickstart
- SDK docs: https://bunchagames.com/developers/docs/sdk
- CLI docs: https://bunchagames.com/developers/docs/cli
Tasks:
- Read the docs above.
- Inspect this repo enough to identify the engine, build/export path, package manager, and likely Buncha Games readiness.
- Make the Buncha Games CLI available for later use with: npm exec --yes --package @bunchagames/cli -- buncha-games --help
- Install or download the relevant Buncha Games SDK path if appropriate: @bunchagames/sdk for web projects, Unity UPM tarball for Unity WebGL, or Godot addon ZIP for Godot Web.
- Do not export, package, upload, or modify gameplay in this pass.
Rules:
- Work only in this game repo unless I explicitly say otherwise.
- Do not edit the Buncha Games platform repo.
- Never print, echo, log, commit, or ask me to paste BUNCHA_GAMES_API_TOKEN.
- Do not add direct ads, direct payments, crypto, provider SDKs, or production monetization assumptions.
Return:
- your understanding of Buncha Games,
- the game engine/build system you found,
- whether the CLI and SDK path are available,
- likely next steps for me to choose from,
- any blockers or questions for me.Integrating the Buncha Games SDK
You are integrating the Buncha Games SDK into this browser game.
Read first:
- SDK docs: https://bunchagames.com/developers/docs/sdk
- Analytics docs: https://bunchagames.com/developers/docs/analytics
- Monetization docs: https://bunchagames.com/developers/docs/monetization
Tasks:
- Confirm the SDK package/download is already available, or install/download it using the documented path.
- Wire the SDK into the project with the smallest safe setup for this engine.
- Keep SDK calls fail-soft outside Buncha Games.
- Do not add gameplay hooks until you report the available SDK calls and I choose where they belong.
- Summarize available calls for player identity/display name, lifecycle, analytics events, Buncha Credits display, wallet/IAP, entitlement validation, ads, and sandbox testing.
Rules:
- Work only in this game repo unless I explicitly say otherwise.
- Do not edit the Buncha Games platform repo.
- Do not add direct ads, direct payments, crypto, provider SDKs, payout logic, or production monetization assumptions.
Return:
- files changed,
- how SDK availability is checked,
- available SDK calls and short examples,
- recommended places where I might add hooks,
- any manual follow-up required.Exporting and Packaging Your Game
You are preparing the browser export package for this game for Buncha Games.
Read first:
- Uploading games: https://bunchagames.com/developers/docs/uploading-games
- Optimizing for Web: https://bunchagames.com/developers/docs/optimizing-for-web
- Quickstart: https://bunchagames.com/developers/docs/quickstart
Tasks:
- Identify the engine/export format.
- If this is Unity or Godot and no web export exists, ask me to create the engine's WebGL/Web export.
- If this is a native web project, run the normal production web build command.
- Run a quick optimization audit on the export: final size, largest files, oversized image/audio assets, source/editor files, first-load asset pressure, hidden-tab behavior, mobile claims, and Buncha Games ZIP readiness.
- Test the exported build from a local static server.
- Create a ZIP from the export contents so index.html is at the ZIP root.
- Exclude source folders, node_modules, .env files, secrets, server files, editor/project folders, caches, and unrelated files.
- Do not upload yet.
Return:
- commands run,
- export folder,
- ZIP path,
- top-level ZIP tree,
- local smoke-test result,
- optimization checks performed and safe improvements still recommended,
- external domains or connected services observed,
- anything that must be fixed before upload.Prepping Screenshots, Videos, and Metadata
You are preparing Buncha Games listing media and metadata for this game.
Read first:
- Uploading games: https://bunchagames.com/developers/docs/uploading-games
- CLI docs: https://bunchagames.com/developers/docs/cli
- Review process: https://bunchagames.com/developers/docs/review-process
Tasks:
- Inspect the repo for title, slug, description, controls, categories, player count, platforms, screenshots, thumbnails, hero art, trailers, and gameplay captures.
- If you have enough information, propose a listing packet.
- If information is missing, ask me for the missing items instead of inventing them.
- Prepare media files where possible: thumbnail, hero image, up to five carousel media assets, and optional trailer link/file.
- Draft concise alt text for each media asset.
- Do not upload yet unless I explicitly ask.
Return:
- suggested title/slug/short description/long description,
- controls, categories, platforms, modes, and player count,
- media file paths and alt text,
- trailer/YouTube info if present,
- missing items I need to provide.Uploading Your Game via CLI
You are uploading this game to Buncha Games using the Buncha Games CLI.
Read first:
- CLI docs: https://bunchagames.com/developers/docs/cli
- Review process: https://bunchagames.com/developers/docs/review-process
Prerequisites:
- I have already approved the export ZIP and media/metadata packet.
- BUNCHA_GAMES_API_TOKEN may be available locally. Never print it.
Tasks:
- Run CLI help/status safely.
- If a Buncha Games game record already exists, update it. If not, create a draft from a manifest.
- Upload the approved ZIP.
- Upload or manage thumbnail, hero, screenshots, and other approved media.
- Request connected-service/domain review only when the build requires it.
- Do not submit for final review unless I explicitly confirm the required attestations.
Return:
- commands run,
- game slug and game id if available,
- build upload result,
- media upload/manage result,
- CLI status JSON summary,
- Developer Dashboard links I should check,
- whether review submission is ready or blocked.Managing Your Game via CLI
You are helping me manage an existing Buncha Games listing using the Buncha Games CLI.
Read first:
- CLI docs: https://bunchagames.com/developers/docs/cli
- Full docs archive: https://bunchagames.com/developers/docs/all
Tasks:
- Explain what the Buncha Games CLI can do for this game: status, create/update listing metadata, upload builds, upload/move/reorder/remove media, request connected-service/domain review, and submit review after human approval.
- Inspect current local repo state and identify which CLI task is appropriate now.
- Run only the CLI commands needed for the task I approve.
- Do not submit review or make irreversible changes unless I explicitly approve that exact action.
Return:
- current Buncha Games status if available,
- recommended CLI action,
- exact command plan before mutating commands,
- results after approved commands,
- dashboard checks I should do manually.