Owner-only steps in docs/agents-core.md now include Beta App Review, tester invitations, review replies, price changes and store experiments; personal data stays in .storebound/. README: live-game journey row, TestFlight and After launch command tables, four new skills, MCP 2026-07-28, unverified list. SECURITY: new endpoints.
5.3 KiB
5.3 KiB
storebound for GitHub Copilot
Mobile game store releases (Google Play, App Store). Skills live in skills/<name>/SKILL.md (Agent Skills format;
storebound install --agent copilot copies them to .github/skills/ of a game project).
These rules apply to every AI tool that uses storebound (skills, MCP server or the CLI in a terminal).
- The owner decides public and irreversible steps. Submitting for review (App Review or Beta App Review), releasing a version, resuming or completing a rollout, canceling a submission, deleting products or listings, accepting agreements, sending review replies, inviting or removing testers, changing prices, starting or stopping a store experiment: explain what will happen and let the owner do it (or run the command only after a clear yes in chat). storebound's MCP server does not offer these at all.
- Dry run first. Every write command has
--dry(MCP:dry_run, default true). Show the dry run, then run it for real only after the owner agrees. - Read before you write.
storebound check(offline) andstorebound validate(read-only, both stores) tell you what is missing and in which order to fix it. - Credentials only from the environment or
.storebound/in the project (gitignored). Never ask for keys, passwords or tokens in chat, never print them, never write them into the config, docs or commits. - Never answer a compliance question you cannot know. Export compliance, Data safety, App Privacy, age rating, target audience: ask the owner when the code does not prove the answer. A wrong "no" is worse than a slow "ask".
- Pick builds by explicit number. Use the build number / versionCode you just uploaded, never "the latest".
- Long uploads run in the background with a log (
storebound play images > .storebound/images.log 2>&1 &) and you report the progress lines, not guesses. - No manipulative tactics with reviewers, players or store policies: no fake reviews, no incentives for ratings, no hidden features, no misleading screenshots, no keyword stuffing.
- Personal data stays local. Tester lists, review reply drafts, health reports and analytics snapshots live in
.storebound/(gitignored). Never put tester emails, reviewer names or crash logs into issues, docs or commits, and never ask for tester emails in chat (storebound masks them in its output).
Tools
- CLI:
storebound <command>(storebound help); configstorebound.config.ts, credentials in env or.storebound/. - MCP:
storebound mcp(stdio). MCP 2026-07-28 + 2025-11-25. Write tools default todry_run: true; submit / release / cancel / delete / send are not exposed. - Readiness:
storebound check(offline),storebound validate(read-only, both stores).
Skills
| skill | for |
|---|---|
ads-levelplay-checks |
Diagnose and verify ad mediation (Unity LevelPlay / ironSource and its networks like Unity Ads, InMobi, Liftoff, AdMob) in a mobile game before and after store release |
app-icons |
Generate every app icon a mobile game needs from one artwork |
app-previews |
Make App Store app preview videos and a Google Play promo video for a mobile game from real gameplay |
appstore-first-release |
Step-by-step first (and later) App Store release of a mobile game |
aso-basics |
App store optimization basics for a mobile game's text |
export-compliance |
Answer App Store export compliance (encryption) for a mobile game correctly |
play-first-release |
Step-by-step first (and later) Google Play release of a mobile game |
portfolio-originality |
Originality gate for studios that ship many similar mobile games |
privacy-manifest |
Add and check Apple privacy manifests (PrivacyInfo.xcprivacy) for an iOS game |
privacy-policy |
Write and host one studio-wide privacy policy page for all of a developer's mobile games |
release-management |
Ship updates safely after the first release |
review-rejections |
Triage and answer an App Store or Google Play rejection, policy warning or strike for a mobile game |
review-replies |
Reply to App Store and Google Play reviews of a mobile game the safe way |
store-analytics |
Take store analytics snapshots for a mobile game (App Store impressions, product page views, downloads and conversion through the Analytics Reports API; Google Play store listing visitors, acquisitions and installs from the Play reports bucket) and compare them with listing, screenshot and experiment changes from git |
store-declarations |
Answer the store compliance forms for a mobile game |
store-health |
Watch a released mobile game's crash and ANR health on both stores |
store-iap-setup |
Create and price in-app purchases (consumables, non-consumables like "remove ads", coin/gem packs, starter packs) on Google Play and App Store Connect from one product list |
store-preflight |
Run and read the storebound readiness checks before submitting a mobile game |
store-screenshots |
Produce store screenshots and the Play feature graphic for a mobile game in every required size and many languages |
testflight |
Run TestFlight for a mobile game through the App Store Connect API |
whats-new |
Write player-facing release notes ("What's new") for a mobile game update from the git log since the last tag |