SKILL=~/.claude/skills/store-art-studio
mkdir -p store/tools
cp $SKILL/templates/android/storeart.config.json store/
cp -R $SKILL/templates/android/page store/page
cp -R $SKILL/templates/android/storeart storeart
cp $SKILL/scripts/* store/tools/

Then add include(":storeart") to your settings and merge storeart/libs.versions.snippet.toml into your catalog, or let the agent do it once it has read your versions. store/storeart.config.json is the only list of markets, and its surfaces says what your app has: screens always, widgets, a live notification, Wear OS or a tablet layout only if you ship them. You own it.

It checks AGP, Kotlin, the Compose BOM, the JDK and any screenshot library you use, then tells you its choice and the dependency changes before editing any Gradle file. If you have Paparazzi or Roborazzi it uses that. It will not add two.

The template is a dedicated test-only module, storeart/, that depends on the modules holding your composables; nothing depends on it. The agent proposes where it goes, you answer. Shipping app code only gains small seams (plain state in, a clock parameter).

Screens are rendered from sample data. If a screen needs a ViewModel, the agent gives it a fake and tells you. No network, no account, no signed-in emulator.

From your Android project's root, with the skill installed:

Use the store-art-studio skill for Google Play, following docs/android-end-to-end.md and
templates/android/START-HERE.md in the skill folder.

1. Discover: read this project (modules, navigation and screens, view models, the manifest,
   widgets, notifications, Wear OS, string files per locale, brand, any fastlane metadata) and
   summarise what you found. Do not build or run anything.
2. Ask me only what the project cannot answer, in batches with your recommended option first:
   features and their order, surfaces to show, design direction, first market, my copy rules,
   the art budget and kind, who uploads.
3. Write docs/screenshots/brief.md and store/storeart.config.json (my first market only,
   "upload": false, "surfaces" as I chose), then stop for my approval.

Before you edit any Gradle file in Gate 0, tell me what this project uses (AGP, Kotlin, compileSdk,
Compose BOM, Glance, Coil, JDK, any screenshot library) and the exact changes, and wait. Never run
my real app, an emulator signed in to a real account, or anything that syncs.

The agent must stop and show you all five. Do not approve without them:

• The sample slot, 1080 x 1920, opaque, which it opened and looked at.
• One of your real screens rendered from sample data, offline.
• The same slot in two locales with different strings and number formats.
• verify-export.sh passing on the output.
• A list of what broke, also written into references/android-compose.md.

plugins { id("app.cash.paparazzi") version "<latest compatible>" }

class StoreArtTest {
  @get:Rule val paparazzi = Paparazzi(deviceConfig = /* 1080 x 1920 px, density 3.0 */)
  @Test fun sample() { paparazzi.snapshot { SampleSlot() } }
}

python3 storeart/scripts/fetch_logos.py
./gradlew :storeart:testDebugUnitTest --tests '*WorldsTest'
storeart/scripts/export.sh
store/page/tools/render-all.sh
store/page/tools/widthtest.sh && store/page/tools/widthtest.sh --negative

Surfaces land in storeart/build/storeart/<code>/, slots in store/page/out/<locale>/: 1080 x 1920 slots and a 1024 x 500 feature graphic. Only the config's default market renders unless you ask for more.

store/tools/verify-export.sh store/page/out 1080x1920 1024x500

Google Play wants each side between 320 and 3840 px, the long side at most twice the short one, JPEG or 24-bit PNG, no alpha, 8 MB at most, 2 to 8 screenshots. A 20:9 screen is not a valid shot as is, which is why slots are 9:16. Check the current Play Console help page before you upload.

One of your own composables, from sample data, with no network. Render it at a realistic phone size (about 412 x 915 dp) and scale it into the slot. If your app has a Wear OS app or tile and the config lists "wear", WearSurfacesTest also writes square, opaque wear_01_tile and wear_02_list for the Wear OS listing.

A finished run on a real app, Standings for Android: real Compose screens, Glance widgets, the live notification and the Wear OS tile, rendered with Paparazzi in 11 languages. The template's sample is plain on purpose; your screens, design and markets replace it.