store-pack
Build a Google Play and App Store submission pack for an app (icons, framed screenshots in the exact store sizes, feature graphic, listing text with character limits, console form answers, blocker analysis) into a store/ folder in the project. Use when asked to make an app "Play Store / App Store ready" or to prepare store assets, listings or console form answers.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/nowfalsalahudeen--store-pack)HTML
<a href="/listings/nowfalsalahudeen--store-pack"><img src="/api/listings/nowfalsalahudeen--store-pack/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
The skill is a folder. Put it where your agent loads skills.
**Claude Code**
git clone https://github.com/nowfalsalahudeen/store-pack ~/.claude/skills/store-pack
(for one project only, clone into `<project>/.claude/skills/store-pack`).
**Other agents:** copy `SKILL.md`, `scripts/`, `templates/` and `docs/` into the folder your agent reads skills from.
**Requirements:** Python 3, the Flutter SDK (the composer is a Flutter test, so no Flutter app is needed), and macOS for the image checks and icon resizing (`sips`). The first run does `flutter pub get` inside `scripts/compose`.
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
SKILL.md · Manifest · 51 lines
- ---
- name: store-pack
- description: Build a Google Play and App Store submission pack for an app (icons, framed screenshots in the exact store sizes, feature graphic, listing text with character limits, console form answers, blocker analysis) into a store/ folder in the project. Use when asked to make an app "Play Store / App Store ready" or to prepare store assets, listings or console form answers.
- ---
- # store-pack
- Produces `store/` in the project root: icons, framed screenshots, a feature graphic, listing text, console form answers and a README of blockers. Never submit, commit or deploy; leave that to the user.
- Requirements: Python 3, the Flutter SDK (the image composer is a Flutter test, no app needed), and macOS (`sips` for image checks and icon sizes). Raw screenshots come from the app itself.
- ## Workflow
- 1. **Inspect the app for facts** (never invent): package/bundle ID, version, permissions (AndroidManifest, Info.plist), SDKs in pubspec, Cargo.toml or package.json (ads, analytics, crash reporting, billing, sign-in), how accounts and payments work, privacy-policy and support URLs, signing config, device families. Read the project's own contributor docs for its rules.
- 2. **Raw screenshots.** Capture from the real app with realistic *invented* data. Never use production data or a production account.
- - Flutter: a widget-test harness with real fonts (`debugDisableShadows = false`, or shadows render as hard outlines); phone 440x956 at 3x = 1320x2868.
- - Web, desktop or hybrid apps: run the app's own server on a scratch database, seed it through the API, and drive it with a browser automation tool. Use a separate browser context with `deviceScaleFactor` 3 (phone, viewport 440x956) or 2 (tablet, 1032x1376), and hide scrollbars with `*::-webkit-scrollbar{display:none!important}*{scrollbar-width:none!important}` before each shot.
- - Kill only the process listening on your own scratch port (`lsof -ti tcp:PORT -sTCP:LISTEN`), never by name.
- - Check each shot by eye. Drop screens that are broken at that width and tell the user.
- 3. **`store/app.json`** (see `docs/config-reference.md`), then run `python3 scripts/make_pack.py store/app.json`. It frames screens on a brand gradient with a caption, builds a feature graphic and icons, and runs `scripts/check_pack.py`.
- - Icon: usually only art with baked-in rounded corners or text exists; the `icon` job crops the mark onto a flat full-bleed background. Tell the user a vector or clean 1024 px source is still needed.
- 4. **Listing text:** `store/listings.json`, then `python3 scripts/write_listings.py store/listings.json` (fastlane layout, limits enforced). Describe only what the build really does and what the platform build includes.
- 5. **Docs:** `store/README.md` (blockers table first), `google-play/console-forms.md`, `app-store/connect-forms.md`.
- ## Store specs (confirm in the consoles; Apple's page may not load)
- - Play: icon 512 px (<= 1 MB); feature graphic 1024x500, no alpha; 2-8 phone shots, each side 320-3840 px and long side <= 2x short side (use 1080x1920); optional 7"/10" tablet shots (1200x1920, 1600x2560); title 30, short 80, full 4000.
- - App Store: iPhone 6.9" 1320x2868 (required), 6.5" 1284x2778; iPad 13" 2064x2752 if iPad is supported; up to 10 each; **no alpha**; icon 1024 px, no alpha; name 30, subtitle 30, promo 170, keywords 100.
- - Both reject screenshots with an alpha channel; the composer writes RGB PNG.
- ## Blockers to look for in every app (learned)
- - **Payments:** selling digital unlocks or licences through a web payment provider inside the app breaks Play Billing / Apple IAP rules. For iOS ship without purchase UI, or add StoreKit. No prices or buy links in mobile builds.
- - **Account deletion:** any app that creates accounts needs an in-app delete path and (Play) a public web URL describing it.
- - **Sign in with Apple:** required wherever Google or other third-party sign-in is offered on iOS.
- - **Test ad IDs** left in a release; missing real IDs.
- - **Play App Signing:** add Play's app-signing SHA-1 to Google OAuth Android clients, or sign-in fails on Play installs.
- - **Restricted or declared permissions:** `REQUEST_IGNORE_BATTERY_OPTIMIZATIONS`, foreground-service types (need a declaration and a video), location (even with `maxSdkVersion`), Bluetooth `neverForLocation`.
- - **Reviewer access:** apps that need a server or licence need a demo server, PIN and steps (Play App access, Apple guideline 2.1).
- - **Privacy policy URL** must exist; contact address and phone for trader status (EU/UK).
- - **Release signing** configured; version bump; AAB for Play; Apple team and bundle ID; `ITSAppUsesNonExemptEncryption`; privacy manifest.
- - **New personal Play accounts:** a 12-tester, 14-day closed test is required before production.
- - **Data safety:** "processed ephemerally" only for data used in memory and never stored (for example a photo sent to an AI service); email or IDs kept on a server are not ephemeral. Advertising ID: answer "No" only if no ad or conversion SDK is present and the advertising-ID permission is removed.
- - **Target audience** 18+ unless the app is truly for children.
- - **A minimum-size shrinker (R8) can fail on optional libraries:** if a release build fails with "Missing classes", add `-dontwarn` rules for the named packages.
- ## Files
- - `scripts/make_pack.py` runs everything; `scripts/compose/` is the Flutter composer (`STORE_JOBS=jobs.json flutter test`); `scripts/build_icons.py`; `scripts/check_pack.py`; `scripts/write_listings.py`.
- - `templates/app.example.json`, `templates/listings.example.json` - configs to copy. `examples/` - a complete worked example with a fictional app and its output.
- - `docs/` - getting started, config reference, how it works.
README.md · README · 94 lines
- # store-pack
- **A Claude skill that gets an app Play Store and App Store ready: icons, framed screenshots in the exact store sizes, a feature graphic, listing text with the limits enforced, and a checklist of the blockers that get apps rejected.**
- Ask an agent to "make my app Play Store ready" and it produces a `store/` folder you can upload from:
- ```
- store/
- google-play/metadata/android/<locale>/ title, short and full description, release notes, images/
- app-store/metadata/en-US/ name, subtitle, promo text, keywords, description, URLs
- app-store/screenshots/en-US/ iPhone 6.9", 6.5" and iPad 13" sets
- README.md the blockers table, first
- ```
- <p align="center">
- <img src="examples/store/google-play/metadata/android/en-US/images/phoneScreenshots/1_dashboard.png" width="30%" alt="Framed Play Store screenshot example">
- <img src="examples/store/google-play/metadata/android/en-US/images/phoneScreenshots/2_dashboard.png" width="30%" alt="Second framed screenshot example">
- </p>
- <p align="center"><sub>Made by <code>scripts/make_pack.py</code> from one raw screenshot and a JSON file. The app is fictional.</sub></p>
- ## What it does
- - **Frames your screenshots** on a brand gradient with a caption, at the exact sizes both stores require (RGB PNG with no alpha, which both stores reject otherwise).
- - **Builds the feature graphic and icons** from your art, including every iOS icon size.
- - **Writes listing text** in the fastlane layout and refuses anything over a store's character limit.
- - **Checks every image** against the published rules (size, count, alpha, file size).
- - **Lists blockers** that cause rejections: account deletion, Sign in with Apple, test ad IDs, payments outside store billing, permissions that need a declaration, reviewer access, the 12-tester rule for new Play accounts, data-safety traps and more.
- - **Never submits, commits or deploys.** You do that.
- ## Install
- The skill is a folder. Put it where your agent loads skills.
- **Claude Code**
- ```bash
- git clone https://github.com/nowfalsalahudeen/store-pack ~/.claude/skills/store-pack
- ```
- (for one project only, clone into `<project>/.claude/skills/store-pack`).
- **Other agents:** copy `SKILL.md`, `scripts/`, `templates/` and `docs/` into the folder your agent reads skills from.
- **Requirements:** Python 3, the Flutter SDK (the composer is a Flutter test, so no Flutter app is needed), and macOS for the image checks and icon resizing (`sips`). The first run does `flutter pub get` inside `scripts/compose`.
- ## Use
- Ask in plain words:
- > "Make my app Play Store ready. Here are the screenshots."
- > "Write the Play and App Store listings for my app and check the limits."
- > "What would get this app rejected?"
- The agent reads your app for the facts (package id, permissions, SDKs, how accounts and payments work), then runs the steps below. Full tutorial: [docs/getting-started.md](docs/getting-started.md).
- ### Run it yourself
- ```bash
- cp -R examples/store my-app-store && cd my-app-store # start from the working example
- python3 ../scripts/make_pack.py app.json # screenshots, icons, feature graphic, then checks
- python3 ../scripts/write_listings.py listings.json # listing text with limits enforced
- python3 ../scripts/check_pack.py app.json # re-run the checks any time
- ```
- Every option is in [docs/config-reference.md](docs/config-reference.md).
- ## What is in the box
- ```
- SKILL.md workflow, store specs, blockers checklist (entry point)
- scripts/
- make_pack.py runs the whole pack from app.json
- compose/ the Flutter image composer (framed screenshots, feature graphic, icon)
- build_icons.py every icon size the stores need
- check_pack.py validates images against the store rules
- write_listings.py listing text files, limits enforced
- templates/ app.example.json, listings.example.json
- examples/store/ a complete worked example (fictional app) and its output
- docs/ getting started, config reference, how it works
- ```
- ## Honesty
- Store specifications change. The skill points to the consoles as the source of truth and says so; confirm sizes and limits there before submitting.
- ## Author
- Built by **Nowfal** from real store submissions. Portfolio: [nowfal.in](https://nowfal.in).
- ## Licence
- MIT. See [LICENSE](LICENSE).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.