← MWM AICONTENT HISTORY
WHAT CHANGED
Update to MWM AI
Snapshot Nov 16, 2026 · 18:15 UTC · version 0.32.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save MWM AI and check future changes in Following.
Up to 3 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Store visuals for the App Store and Google Play: screenshots and their headlines, app icons, the iOS 27 App Store header and search visual, Google Play graphics, and their localization. Use when the person says things like \"make my screenshots\", \"my icon looks dated\", \"redo the screenshots for iPad\", \"design my App Store header\" or \"translate my screenshots into Spanish\". Not for listing text (store-copy), pages per audience (acquisition-pages) or matching the app's look (brand-visuals).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 380
}
],
"name": "store-visuals",
"skill_md_contents": "---\nname: store-visuals\ndescription: \"Store visuals for the App Store and Google Play: screenshots and their headlines, app icons, the iOS 27 App Store header and search visual, Google Play graphics, and their localization. Use when the person says things like \\\"make my screenshots\\\", \\\"my icon looks dated\\\", \\\"redo the screenshots for iPad\\\", \\\"design my App Store header\\\" or \\\"translate my screenshots into Spanish\\\". Not for listing text (store-copy), pages per audience (acquisition-pages) or matching the app's look (brand-visuals).\"\n---\n\n# Store visuals\n\n## When this applies\n\nMaking, judging, adjusting or localizing a listing's images: screenshots per device, the icon, the iOS 27 App Store header and search visual, Google Play's graphics. Pages per audience belong to acquisition-pages, the words to store-copy, the app's look to brand-visuals.\n\n## The job and what good looks like\n\nThe person ends with visuals a stranger understands at a glance in search results. Screenshots build on the app's real screens, one idea and one short headline each, the promise on the first ones people see. A series reads as one family, with the same background, accent, type and character, yet never repeats one composition: each screenshot gets its own staging (device angle or no hand, framing, supporting element) fitted to its position's job. An icon is one clear symbol that still reads at the smallest size. A header carries one idea for a first-time visitor, on brand with the screenshots.\n\n## How a pro decides\n\n- **Real screens or a scenario.** The app's screens come from its listing, or from the project or the person's files before launch. A written scenario only illustrates: use it when no screens exist, and say so.\n- **Adjust or regenerate.** A headline, a colour or one screen is an adjustment; regenerate only when the direction is wrong.\n- **Source language or every locale.** Iterate the source language until the person is happy, and localize from that series.\n- **Text on the header or not.** By default none; a few words in the page's language only when the person wants them.\n- **Separate screens or a panorama.** A panorama is one continuous image cut across a few consecutive slots so the seams match, for a series telling one story. Each of the first screenshots must still read alone: search shows only the first few, as many as the knowledge base says.\n- **Inspired or copied.** A competitor's style may guide a series; their images, layouts and words stay theirs.\n\n## Do\n\n- Make every image look like the app, from its brand guide and references as brand-visuals describes.\n- Keep what the person brought, screenshots, icon or video, as given unless they ask for a restyle.\n- Restaging a screen keeps its real interface, brand type and layout; headlines go in the caption.\n- Offer a new style direction, more icons, a video or other devices only when asked.\n- Say which older series stays live on a device you did not redo, so the listing does not mix two looks.\n- Show what replaces what before anything reaches a store.\n\n## Don't\n\n- Don't generate from a scenario when screens exist, nor ask for screens in the chat when the listing or project holds them.\n- Don't crop or stretch an image to fit a slot: make it at the size the store asks for.\n- Don't regenerate after a studio reported its result; read it.\n\n## Pitfalls\n\n- A device the generators skip is still in the listing; empty or stale, it shows.\n- An icon with fine detail or words turns into noise at small size.\n- A header with claims (prices, rankings, awards, other platforms) fails App Review.\n- Losing the person's screens between design and apply: reuse the design's.\n\n## Store facts\n\nTool results carry the store rules and limits they depend on, each with its source and the date it was checked. `get_publishing_knowledge` answers questions on this skill's topics the same way (topics: `app-store/screenshots`, `app-store/product-page-header`, `app-store/app-icon`, `google-play/graphics-and-screenshots`, `aso/screenshot-practice`, `aso/icon-practice`, `mwm/studios-and-assets`). When you use one of these facts, give its source and date.\n"
}SHA-256 of public snapshot: 432b8b924e59430b2c5e64eca0d55442c89bbc013ff7e9d8c6b8a5ea0421a6d5