CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions
Take mobile apps and games from zero to Submit for review on Google Play and the App Store. Bun CLI, MCP server, Agent Skills. npm: storebound · MIT https://storebound.dev
338 commits 28 branches 80 tags 76 MiB
Find a file
CRT c3b1e8c370 release candidates: every push to main runs the full CI, the acceptance matrix and the Linux / Windows installer builds in parallel (ci.yml) and records the green result per commit as the draft rc-<sha> (green.json last); a version-only bump commit (proven file by file with the version writers) reuses its parent's CI and matrix and rebuilds only the installers; a v* tag only promotes the candidate (release.yml), fails fast on a red or missing commit; acceptance runs carry a CLI key; tools/release.ts does the whole release on the Mac (bump, CHANGELOG cut, fast gate, push, tag, Mac build + notarize in parallel with Forgejo, cached macOS acceptance, add, verify, publish with one upload of the Mac files, /Applications update, npm commands) and --rehearsal; DMG notarization runs while the app and updater bundle are checked; rehearsal channel on the VDS; docs
2026-10-15 00:42:50 +08:00
.claude-plugin storebound 0.8.4: version in package.json and every copy, CHANGELOG 0.8.4 section 2026-10-14 23:40:40 +08:00
.codex-plugin storebound 0.8.4: version in package.json and every copy, CHANGELOG 0.8.4 section 2026-10-14 23:40:40 +08:00
.cursor/rules CLI runs on Node 20+: npx storebound (bunx keeps working) 2026-10-13 04:03:28 +08:00
.forgejo release candidates: every push to main runs the full CI, the acceptance matrix and the Linux / Windows installer builds in parallel (ci.yml) and records the green result per commit as the draft rc-<sha> (green.json last); a version-only bump commit (proven file by file with the version writers) reuses its parent's CI and matrix and rebuilds only the installers; a v* tag only promotes the candidate (release.yml), fails fast on a red or missing commit; acceptance runs carry a CLI key; tools/release.ts does the whole release on the Mac (bump, CHANGELOG cut, fast gate, push, tag, Mac build + notarize in parallel with Forgejo, cached macOS acceptance, add, verify, publish with one upload of the Mac files, /Applications update, npm commands) and --rehearsal; DMG notarization runs while the app and updater bundle are checked; rehearsal channel on the VDS; docs 2026-10-15 00:42:50 +08:00
.github CLI runs on Node 20+: npx storebound (bunx keeps working) 2026-10-13 04:03:28 +08:00
apps/desktop storebound 0.8.4: version in package.json and every copy, CHANGELOG 0.8.4 section 2026-10-14 23:40:40 +08:00
bin CLI runs on Node 20+: npx storebound (bunx keeps working) 2026-10-13 04:03:28 +08:00
brand New logo from one master: brand/, tools/brand-assets.py makes every app icon, favicon, header mark and og image; no hand-written SVG left 2026-10-11 10:13:13 +08:00
cli console Chrome never outlives its run: exit kills it, SIGINT / SIGTERM / SIGHUP close it gracefully, a detached watchdog ends it when the parent dies (SIGKILL included; a reused pid is never killed); every start ends headless orphans on storebound profiles and names orphaned windows; headless runs on macOS prefer Chromium / Chrome for Testing over Google Chrome.app (an orphan kept the owner's Chrome from opening from the Dock); console fill closes the window on errors; pitfall 68; tests 2026-10-15 00:28:32 +08:00
docs release candidates: every push to main runs the full CI, the acceptance matrix and the Linux / Windows installer builds in parallel (ci.yml) and records the green result per commit as the draft rc-<sha> (green.json last); a version-only bump commit (proven file by file with the version writers) reuses its parent's CI and matrix and rebuilds only the installers; a v* tag only promotes the candidate (release.yml), fails fast on a red or missing commit; acceptance runs carry a CLI key; tools/release.ts does the whole release on the Mac (bump, CHANGELOG cut, fast gate, push, tag, Mac build + notarize in parallel with Forgejo, cached macOS acceptance, add, verify, publish with one upload of the Mac files, /Applications update, npm commands) and --rehearsal; DMG notarization runs while the app and updater bundle are checked; rehearsal channel on the VDS; docs 2026-10-15 00:42:50 +08:00
examples template compliance answers never reach a store: init writes unanswered (dataSafety, appPrivacy, reviewNotes, ageRating, accounts, reviewAccess), older configs are recognised by the template values; check / validate / scan block, play data-safety (also --dry), console plan / fill, apple review-details and appinfo refuse. onboard --declarations replaces them on a live app: name and copyright from the stores (a copyright with a private term is left out), the rows the code proves (scan proposal, sign-up methods from auth code and login SDKs), the rest as one owner question list. play data-safety --dry prints the answers that change (old -> new, account and deletion first) against the last uploaded CSV; pitfall 60; tests 2026-10-14 11:36:30 +08:00
media/teaser --json prints only JSON on stdout (withJsonOutput around every command: logs, tables and prompts to stderr; printJson everywhere; test runs every --json command against the fake stores and parses stdout); prices ppp compares like with like: par = the store's own US-equivalent price (Play convertRegionPrices, Apple equalizations; offline base x fx x (1 + VAT) rounded up) scaled by the PPP price level; defaults only lower, only price levels <= 0.5, World Bank high-income at par, CN at par on Apple and skipped on Play, never above par (--only-decreases, --max-ratio, --min-ratio, --max-level, --include-high-income; --floor / --ceiling kept), top-10 revenue market drops > 20 % warned (sales reports, else a static list), unchanged regions out of the sheet; price changes of existing products only with --allow-price-changes, TTY or not (a terminal yes covered them), then their own question listing each old -> new, held section in dry runs (play products, prices import, play / apple subscriptions); pitfalls 61-63; tests 2026-10-14 17:36:00 +08:00
site site: first-party, cookieless visit stats (self-hosted Umami at storebound.dev/s/, Do Not Track respected) with events for copy buttons, desktop downloads per OS, the teaser (play, 50 %, complete) and outbound docs / git / npm links; a privacy note in the footer; docs/site-analytics.md and tools/vds/ configs to rebuild the server side; scrub allows a page's public stats website id 2026-10-14 11:11:24 +08:00
skills console Chrome never outlives its run: exit kills it, SIGINT / SIGTERM / SIGHUP close it gracefully, a detached watchdog ends it when the parent dies (SIGKILL included; a reused pid is never killed); every start ends headless orphans on storebound profiles and names orphaned windows; headless runs on macOS prefer Chromium / Chrome for Testing over Google Chrome.app (an orphan kept the owner's Chrome from opening from the Dock); console fill closes the window on errors; pitfall 68; tests 2026-10-15 00:28:32 +08:00
specs storebound api: every App Store Connect and Google Play operation 2026-10-11 23:37:09 +08:00
templates template compliance answers never reach a store: init writes unanswered (dataSafety, appPrivacy, reviewNotes, ageRating, accounts, reviewAccess), older configs are recognised by the template values; check / validate / scan block, play data-safety (also --dry), console plan / fill, apple review-details and appinfo refuse. onboard --declarations replaces them on a live app: name and copyright from the stores (a copyright with a private term is left out), the rows the code proves (scan proposal, sign-up methods from auth code and login SDKs), the rest as one owner question list. play data-safety --dry prints the answers that change (old -> new, account and deletion first) against the last uploaded CSV; pitfall 60; tests 2026-10-14 11:36:30 +08:00
tests release candidates: every push to main runs the full CI, the acceptance matrix and the Linux / Windows installer builds in parallel (ci.yml) and records the green result per commit as the draft rc-<sha> (green.json last); a version-only bump commit (proven file by file with the version writers) reuses its parent's CI and matrix and rebuilds only the installers; a v* tag only promotes the candidate (release.yml), fails fast on a red or missing commit; acceptance runs carry a CLI key; tools/release.ts does the whole release on the Mac (bump, CHANGELOG cut, fast gate, push, tag, Mac build + notarize in parallel with Forgejo, cached macOS acceptance, add, verify, publish with one upload of the Mac files, /Applications update, npm commands) and --rehearsal; DMG notarization runs while the app and updater bundle are checked; rehearsal channel on the VDS; docs 2026-10-15 00:42:50 +08:00
tools release candidates: every push to main runs the full CI, the acceptance matrix and the Linux / Windows installer builds in parallel (ci.yml) and records the green result per commit as the draft rc-<sha> (green.json last); a version-only bump commit (proven file by file with the version writers) reuses its parent's CI and matrix and rebuilds only the installers; a v* tag only promotes the candidate (release.yml), fails fast on a red or missing commit; acceptance runs carry a CLI key; tools/release.ts does the whole release on the Mac (bump, CHANGELOG cut, fast gate, push, tag, Mac build + notarize in parallel with Forgejo, cached macOS acceptance, add, verify, publish with one upload of the Mac files, /Applications update, npm commands) and --rehearsal; DMG notarization runs while the app and updater bundle are checked; rehearsal channel on the VDS; docs 2026-10-15 00:42:50 +08:00
.gitignore CLI runs on Node 20+: npx storebound (bunx keeps working) 2026-10-13 04:03:28 +08:00
.mcp.json Adapters for every AI tool from one source, tests and CI 2026-10-10 21:03:10 +08:00
AGENTS.md CLI runs on Node 20+: npx storebound (bunx keeps working) 2026-10-13 04:03:28 +08:00
bunfig.toml idempotency: WIP 2026-10-12 04:00:58 +08:00
CHANGELOG.md release candidates: every push to main runs the full CI, the acceptance matrix and the Linux / Windows installer builds in parallel (ci.yml) and records the green result per commit as the draft rc-<sha> (green.json last); a version-only bump commit (proven file by file with the version writers) reuses its parent's CI and matrix and rebuilds only the installers; a v* tag only promotes the candidate (release.yml), fails fast on a red or missing commit; acceptance runs carry a CLI key; tools/release.ts does the whole release on the Mac (bump, CHANGELOG cut, fast gate, push, tag, Mac build + notarize in parallel with Forgejo, cached macOS acceptance, add, verify, publish with one upload of the Mac files, /Applications update, npm commands) and --rehearsal; DMG notarization runs while the app and updater bundle are checked; rehearsal channel on the VDS; docs 2026-10-15 00:42:50 +08:00
CONTRIBUTING.md One product per machine: the CLI and the desktop app share one version, the store accounts and the app folder list 2026-10-13 06:17:37 +08:00
gemini-extension.json storebound 0.8.4: version in package.json and every copy, CHANGELOG 0.8.4 section 2026-10-14 23:40:40 +08:00
GEMINI.md CLI runs on Node 20+: npx storebound (bunx keeps working) 2026-10-13 04:03:28 +08:00
LICENSE crt-ship 0.1.0: CLI, Claude Code skills and templates for shipping mobile games to Google Play and the App Store 2026-10-10 20:29:20 +08:00
package.json storebound 0.8.4: version in package.json and every copy, CHANGELOG 0.8.4 section 2026-10-14 23:40:40 +08:00
README.md One product per machine: the CLI and the desktop app share one version, the store accounts and the app folder list 2026-10-13 06:17:37 +08:00
SECURITY.md 0.4.0: changelog, version, README (journey, commands, skills, MCP, safety, FAQ, roadmap), agent rules, adapters 2026-10-10 23:30:48 +08:00
tsconfig.json storebound scan: offline rejection-risk scan of the project itself 2026-10-11 23:20:55 +08:00

README.md

storebound logo

storebound

From an empty folder to "Submit for review" on Google Play and the App Store.

Your AI agent does all of it with storebound: builds, uploads, store text, screenshots in every language and size, in-app products and prices, the compliance forms, even the consoles that have no API. You only press Submit.

npm license: MIT version 0.6.0 runtime: Node 20+ or Bun 1.1+ runtime dependencies: 0 Agent Skills: 25 MCP: 2026-07-28

Website: storebound.dev · Docs: docs/ · npx storebound init

The storebound teaser: from an empty folder to Submit for review in under a minute (opens the video on storebound.dev)

Watch the teaser on storebound.dev: the demo game from an empty folder to both stores, then the desktop app.

Your agent does the whole job

Do it, don't ask. You ask once ("get my app ready for both stores"); your agent and storebound do the work: the app records, builds and uploads, listings in every language, screenshots and previews in every store size, icons, in-app products and subscriptions priced in 175 countries, Data safety, App Privacy, age rating and every other form, and the console pages that have no API (the agent drives them from a console plan). Each step is planned first:

storebound release plan 1.0.0: every step left on both stores for a brand-new app, in fix order, with the owner's next step named

You press only the final public or irreversible buttons (Submit for review, releasing, App Privacy Publish, legal agreements) and answer, once and in one batch, the facts no file can prove. The full rules: AGENTS.md; the whole journey step by step: docs/journey.md.

You won't get rejected for the avoidable things

storebound scan reads your project (Xcode and Gradle files, manifests, lockfiles, SDKs, your listings) and the store state, and names every App Review or Play policy problem it can prove before the stores do: the guideline, the evidence as file:line, and the fix.

storebound scan on a sign-in app: blockers for Guideline 2.1(a) (no demo account) and 5.1.1(v) (no account deletion), each with its evidence and fix

Every rule, what it proves and what only a reviewer can see: docs/rejections.md.

The desktop app: every app, both stores, one window

Every app and game you ship on Google Play and the App Store side by side: releases, charts, catalog and prices, crash health, reviews, TestFlight and the rejection checks. Send for review from there too: a dry run first, then a confirm, then your click. Same storebound underneath, same version number as the CLI, and the same store accounts and app folders as your terminal (~/.storebound).

storebound desktop, Releases › Send for review: the dry run of the submission with the build picked by number and the confirm step

More screens: portfolio, growth charts, prices, checks, TestFlight, console plan

Portfolio: every app of every studio with its state on both stores Growth: store analytics chart with the day under the pointer Prices: products by key territory, both stores' prices per country, gaps marked Checks: rejection risks with evidence and the fix TestFlight: groups, testers and builds Console plan: the steps, answer sheet and never-press list for a console form without an API

npx storebound desktop installs it for you (macOS, Windows, Linux; signature checked, no admin rights) and opens it on the current app folder. Manual downloads: storebound.dev/#download. Internals: docs/desktop.md.

Works with your AI, safe by design

Skills, an MCP server and the CLI for Claude Code, Codex, Cursor, Gemini CLI, Copilot, Windsurf, OpenCode or anything that reads AGENTS.md. Every write shows a dry run first; submit, release and delete are not MCP tools; keys stay in env vars or the gitignored .storebound/.

storebound play products --dry: two in-app products planned with regional prices in 174 Google Play regions, nothing written

Per-tool setup: docs/getting-started.md · MCP tools: docs/mcp.md · Safety model: docs/safety.md.

Install and start

You need Node 20+ or Bun 1.1+ (and ffmpeg for icons, screenshots and video).

cd my-app
npx storebound init                     # storebound.config.ts + .storebound/ in this project (--profile app | subscription-app | game)
npx storebound desktop                  # installs the desktop app once (asks first) and opens it on this folder

One product, installed once per machine: the CLI (npx / bunx) and the desktop app have the same version, the same store accounts (~/.storebound/credentials, npx storebound accounts) and the same list of app folders. Each project has its storebound.config.ts and a gitignored .storebound/ (upload keystore, review contact). Then npx storebound install --agent claude (or codex, cursor, gemini, copilot, windsurf, opencode) and npx storebound check. Every npx storebound ... works as bunx storebound ... too.

Then ask your agent: "take my app to Google Play and the App Store". Claude Code plugin, credentials, coming from fastlane: docs/getting-started.md.

What it covers

Store screenshots of the demo game, rendered by storebound in every size and language:

Store screenshots rendered by storebound: four scenes in English plus the hero scene in Turkish, Japanese and Arabic

Contributing and license

Issues and pull requests are welcome; see CONTRIBUTING.md (bun run ci must be green). MIT, see LICENSE. Copyright (c) 2026 CRTkafa. Not affiliated with Google or Apple.