---
name: mobile-store-asset-production
description: "Produce App Store and Google Play screenshot sets, listing metadata, and localized assets from real mobile runtime captures. Use for truthful store storyboards, capture manifests, asset QA, and export handoffs."
---

# Mobile Store Asset Production

Work as the agency's listing and asset-production desk. Make the current app understandable through real product evidence and concise, platform-appropriate copy.

1. Establish app/build, iOS/Android/device support, target markets/locales, approved value proposition, and output folder. Record every proposed claim against a working feature or verified evidence.
2. Read [capture and export workflow](references/capture-workflow.md) and verify current official store requirements linked there. Resolve required device classes before preparing artwork. Historical skills contain tactics, not authoritative dimensions, indexing claims, or conversion guarantees.
3. Draft [storyboard and metadata](templates/storyboard-metadata.md). Route copy ideas to `design-screenshots` / `design-screenshots-play` and keyword work to `aso-keywords` / `aso-keywords-play`, then validate those suggestions against current platform policy and the app's actual behavior.
4. Capture the installed current app at reproducible routes with permissioned test fixtures. Keep originals and fill [capture manifest](templates/capture-manifest.json). A simulator capture proves the visible simulator state; it does not prove a physical-device flow, purchase, backend, or release.
5. Compose captions, licensed backgrounds, framing, and localized layout around the originals. Decorative generated artwork must remain a separate labeled asset. Do not generate, draw, or alter fake controls/data to imply a feature works. A design prototype or web recreation is not a runtime capture.
6. Review exports for real functionality, privacy, typography, clipping, locale accuracy, dimensions, alpha/format, platform consistency, and current store policy. Deliver originals, compositions, manifest, copy, and outstanding gaps.

## Tool routing

Use available device/simulator screenshot tools. If no capture tool or runtime exists, create the storyboard and capture checklist and report captures pending. For supplied Figma compositions, use `figma-to-rn` / `figma-to-rn-android` only when implementation is actually requested. A Figma frame never substitutes for captured working UI. No paid screenshot tool, Figma subscription, or new account is mandatory.

## Completion and external actions

A complete local asset pack links each exported screenshot to an original current runtime capture, versioned app/build, locale/device, and an evidence-backed caption. Keep approved exports separate from drafts and unavailable-feature placeholders. Upload, submission, store experiments, publication, and paid ad launch require the user's applicable external-action authorization; local production does not imply those actions.