# Skill: Assemble the complete store asset kit before submitting an app for publication

> Lets an AI coding/design agent produce or audit every non-code asset the App Store and Google Play require before a submission can go through — applies any time a developer is preparing a first release or a major update.

Source: sodigi·learn — publish/chto-nuzhno-dlya-publikacii · https://sodigi.io/learn/publish/chto-nuzhno-dlya-publikacii

## When to use
- The developer is approaching their first submission and asks what is needed beyond the code.
- A store listing is incomplete and the "Submit" button is greyed out.
- The developer needs to prepare assets for both App Store and Google Play in one pass.
- A previous submission was rejected for a missing icon, wrong screenshot size, broken privacy link, or no age rating.

## Core rules
- Publishing requires a storefront, not just a binary. No assets = no submission, regardless of code quality.
- Prepare assets DURING development, not the day before launch.
- The base kit is shared between stores: icon, screenshots, name, short description, full description, category, age rating, privacy policy link.
- Screenshots must match the actual build — they are the primary conversion driver and the primary deception check.
- Provide separate screenshot sets for every screen size you support (phone minimum; tablet if supported).
- Age rating is CALCULATED by the store from a questionnaire — never set manually; answer honestly.
- Privacy policy must be a live, public URL that opens without a login. A broken or empty link is a top rejection cause.
- Google Play additionally requires a wide feature graphic (horizontal banner). Apple accepts an optional short preview video.
- Character limits for name and description differ between stores — the same text will likely need trimming for one of them.

## Procedure
1. Create the app icon as a 1024x1024 px square with no text, no transparent edges, and no manually rounded corners — the stores apply their own corner radius.
2. Take screenshots from the real, current build (not designer mockups). Annotate the first two screenshots with a one-line benefit caption.
3. Produce a phone screenshot set. If the app supports tablets, produce a separate tablet set. Check each store's current size requirements right before submission.
4. Write the short name (brand only, fits the narrow field without truncation).
5. Write the short description/subtitle: one hook phrase — what the app is and why it matters.
6. Write the full description: features and benefits for humans, no keyword stuffing.
7. Select the primary category (and optional secondary) where users will actually look for the app.
8. Fill out the age rating questionnaire honestly in each store console; the stores calculate the final rating.
9. Publish a privacy policy page at a stable public URL; confirm it opens in an incognito window with no login. Paste the URL into both store consoles.
10. For Google Play: prepare the wide feature graphic (horizontal promotional image).
11. Run the pre-submission checklist: every field filled, every link live, every screenshot from the current build.

## Ready-to-use prompt
```
Help me assemble the complete asset kit for publishing my app to the App Store and Google Play.

For each asset below, tell me the current required sizes/limits (check the official App Store Connect and Play Console help — do not use cached numbers) and flag anything I am missing:

1. App icon: 1024x1024, no text, no transparency, no manual corner rounding.
2. Phone screenshots (at least 2, up to the store maximum): taken from the current build, first two showing the main benefit.
3. Tablet screenshots (if the app supports tablets): separate set.
4. Short name: brand only, fits the character limit.
5. Short description / subtitle: one hook phrase.
6. Full description: benefits-first, no keyword spam.
7. Category: where users will search for this app.
8. Age rating questionnaire: completed honestly; do not set a rating manually.
9. Privacy policy URL: public, no login, stable host.
10. Google Play feature graphic (if targeting Android).

For each item, confirm whether I have it ready or tell me exactly what to produce.
```

## Pitfalls
- One screenshot set for all screen sizes — phones and tablets require separate sets; using one for both causes a mangled listing or rejection.
- Bare screenshots with no caption — they undersell the app; the first two screenshots are the main conversion moment.
- Manually rounding the icon corners — the system adds rounding; doing it yourself produces a double-rounded or misaligned icon.
- Broken or empty privacy policy URL — one of the most common single rejection causes; verify the link opens in incognito before submitting.
- Setting the age rating to the lowest value for reach — lying on the questionnaire leads to rejection or removal; the store calculates the rating from answers.
- Preparing assets on launch day — wrong sizes and missing pages cause multi-day delays; start during development.
- Assuming the same text fits both stores — character limits differ; always check both before copy-pasting.