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.9 KiB
5.9 KiB
storebound
Toolchain for shipping mobile games to Google Play and the App Store. Before a store task, open the matching skill file below and follow it step by step.
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
skills/ads-levelplay-checks/SKILL.md: 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 releaseskills/app-icons/SKILL.md: Generate every app icon a mobile game needs from one artworkskills/app-previews/SKILL.md: Make App Store app preview videos and a Google Play promo video for a mobile game from real gameplayskills/appstore-first-release/SKILL.md: Step-by-step first (and later) App Store release of a mobile gameskills/aso-basics/SKILL.md: App store optimization basics for a mobile game's textskills/export-compliance/SKILL.md: Answer App Store export compliance (encryption) for a mobile game correctlyskills/play-first-release/SKILL.md: Step-by-step first (and later) Google Play release of a mobile gameskills/portfolio-originality/SKILL.md: Originality gate for studios that ship many similar mobile gamesskills/privacy-manifest/SKILL.md: Add and check Apple privacy manifests (PrivacyInfo.xcprivacy) for an iOS gameskills/privacy-policy/SKILL.md: Write and host one studio-wide privacy policy page for all of a developer's mobile gamesskills/release-management/SKILL.md: Ship updates safely after the first releaseskills/review-rejections/SKILL.md: Triage and answer an App Store or Google Play rejection, policy warning or strike for a mobile gameskills/review-replies/SKILL.md: Reply to App Store and Google Play reviews of a mobile game the safe wayskills/store-analytics/SKILL.md: 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 gitskills/store-declarations/SKILL.md: Answer the store compliance forms for a mobile gameskills/store-health/SKILL.md: Watch a released mobile game's crash and ANR health on both storesskills/store-iap-setup/SKILL.md: 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 listskills/store-preflight/SKILL.md: Run and read the storebound readiness checks before submitting a mobile gameskills/store-screenshots/SKILL.md: Produce store screenshots and the Play feature graphic for a mobile game in every required size and many languagesskills/testflight/SKILL.md: Run TestFlight for a mobile game through the App Store Connect APIskills/whats-new/SKILL.md: Write player-facing release notes ("What's new") for a mobile game update from the git log since the last tag
Working on storebound itself
- Bun + TypeScript strict, zero runtime dependencies.
bun run cimust pass (adapters fresh, tests, typecheck, scrub). - Skills are the single source: edit
skills/*/SKILL.mdordocs/agents-core.md, thenbun tools/gen-adapters.ts. - Never commit credentials, account / team / issuer / key / app ids or personal data; placeholders use example.com.