---
description: Shipping a mobile game to Google Play or the App Store with storebound (listings, IAPs, screenshots, releases, review, compliance)
alwaysApply: false
---

<!-- generated by tools/gen-adapters.ts from docs/agents-core.md and skills/*/SKILL.md; do not edit -->

These rules apply to every AI tool that uses storebound (skills, MCP server or the CLI in a terminal).

1. **The owner decides public and irreversible steps.** Submitting for review, releasing a version, resuming or
   completing a rollout, canceling a submission, deleting products or listings, accepting agreements: 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.
2. **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.
3. **Read before you write.** `storebound check` (offline) and `storebound validate` (read-only, both stores) tell you
   what is missing and in which order to fix it.
4. **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.
5. **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".
6. **Pick builds by explicit number.** Use the build number / versionCode you just uploaded, never "the latest".
7. **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.
8. **No manipulative tactics** with reviewers, players or store policies: no fake reviews, no hidden features, no
   misleading screenshots, no keyword stuffing.

## Tools

- CLI: `storebound <command>` (`storebound help`); config `storebound.config.ts`, credentials in env or `.storebound/`.
- MCP: `storebound mcp` (stdio). Write tools default to `dry_run: true`; submit / release / cancel / delete 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 release
- `skills/app-icons/SKILL.md`: Generate every app icon a mobile game needs from one artwork
- `skills/appstore-first-release/SKILL.md`: Step-by-step first (and later) App Store release of a mobile game
- `skills/aso-basics/SKILL.md`: App store optimization basics for a mobile game's text
- `skills/export-compliance/SKILL.md`: Answer App Store export compliance (encryption) for a mobile game correctly
- `skills/play-first-release/SKILL.md`: Step-by-step first (and later) Google Play release of a mobile game
- `skills/portfolio-originality/SKILL.md`: Originality gate for studios that ship many similar mobile games
- `skills/privacy-manifest/SKILL.md`: Add and check Apple privacy manifests (PrivacyInfo.xcprivacy) for an iOS game
- `skills/privacy-policy/SKILL.md`: Write and host one studio-wide privacy policy page for all of a developer's mobile games
- `skills/release-management/SKILL.md`: Ship updates safely after the first release
- `skills/review-rejections/SKILL.md`: Triage and answer an App Store or Google Play rejection, policy warning or strike for a mobile game
- `skills/store-declarations/SKILL.md`: Answer the store compliance forms for a mobile game
- `skills/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 list
- `skills/store-preflight/SKILL.md`: Run and read the storebound readiness checks before submitting a mobile game
- `skills/store-screenshots/SKILL.md`: Produce store screenshots and the Play feature graphic for a mobile game in every required size and many languages
- `skills/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