CRT/storebound
1
0
Fork 0
Code Issues Pull requests Releases 1 Packages 1 Activity Actions
storebound/README.md
CRT 710c3a53d0 README, docs and site: one story (the whole job, no avoidable rejections, the desktop app, your AI, install) 
README is a short front page (about 120 lines) with one real visual per section; every former section moved
unchanged into docs/*.md with a docs/README.md index (journey, rejections, getting-started, commands, growth,
studios, store-art, listing-languages, api, skills, mcp, safety, faq, project). The site tells the same story on one
page: the teaser in the hero, real CLI output as text, the desktop app as a section with light/dark captures of eight
screens and the per-system downloads (desktop/latest.json); /desktop/ redirects to /#download. New capture tools:
tools/site-desktop-shots.ts (fixture-mode desktop frames) and tools/site-term-shots.ts (real CLI output as text and
WebP). tests/docs-links.test.ts checks README, docs and site links resolve.
2026-10-13 03:29:59 +08:00

7.9 KiB
Raw Blame History

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: Bun runtime dependencies: 0 Agent Skills: 25 MCP: 2026-07-28

Website: storebound.dev · Docs: docs/ · bunx 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; store keys stay in the system keychain.

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

Download for macOS, Windows and Linux: storebound.dev/#download, or storebound desktop --download (checks the signature, never installs). 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 Bun 1.1+ (and ffmpeg for icons, screenshots and video).

cd my-app
bun add -d storebound playwright
bunx storebound init                     # --profile app (default) | subscription-app | game
bunx storebound install --agent claude   # or codex, cursor, gemini, copilot, windsurf, opencode
bunx storebound check                    # offline: config, limits, Data safety, products, files

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. Desktop app: storebound.dev/#download.

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.