← 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": "App Store and Google Play listing text and ASO wording: app name, subtitle, keyword field, promotional text, descriptions, What's New and Play release notes, and their localization. Use when the person says things like \"rewrite my subtitle\", \"what keywords should I put\", \"my app isn't found in search\", \"translate my listing into German\", \"is my description good?\" or \"write the release notes\". Not for researching competitors or a market (market-research) or for images (store-visuals).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 356
}
],
"name": "store-copy",
"skill_md_contents": "---\nname: store-copy\ndescription: \"App Store and Google Play listing text and ASO wording: app name, subtitle, keyword field, promotional text, descriptions, What's New and Play release notes, and their localization. Use when the person says things like \\\"rewrite my subtitle\\\", \\\"what keywords should I put\\\", \\\"my app isn't found in search\\\", \\\"translate my listing into German\\\", \\\"is my description good?\\\" or \\\"write the release notes\\\". Not for researching competitors or a market (market-research) or for images (store-visuals).\"\n---\n\n# Store copy\n\n## When this applies\n\nWriting, judging or localizing the words of a store listing, on either store, for an app that is live or not published yet. Researching competitors and markets belongs to market-research; screenshots and icons to store-visuals.\n\n## The job and what good looks like\n\nThe person ends with copy for each store and language they asked about that a stranger in that country finds by typing what they type, and understands from the first words. The promise comes first. The fields search reads spend every character on distinct terms people search for; the selling text speaks to someone already on the page. Every proposal rests on evidence the person can check: competitors' listings, keyword demand and difficulty.\n\n## How a pro decides\n\n- **Search or persuasion.** The stores read different fields for search. Place each term where search reads it, and let the description persuade.\n- **Brand or job in the name.** A known brand keeps its name; an unknown one spends it on what the app does.\n- **Localize or translate.** Each locale gets the words its users type, which may share nothing with the source. A translation that overflows is rewritten to fit, never cut.\n- **Variants or one answer.** Offer variants only on short fields where wording changes the outcome; each names its angle and its evidence in one sentence. One long description, not variants.\n- **Which findings to act on.** Fix what a store enforces or documents. Fix MWM's own pipeline rules while saying the store would accept the text. Mention practitioner habits only when asked. A clean check means no rule fired, not that App Review agrees.\n\n## Do\n\n- Use the person's own wording as given, untranslated unless they ask; when it breaks a store rule, write it and say what it costs.\n- Write each store's fields for that store; never carry a value from one store's field to the other's.\n- For an open goal on Google Play, include release notes in the first draft for the languages in scope.\n- Take a new country's keywords from that country's searches.\n- For an app not on a store yet, read its texts in the project: fastlane metadata, Info.plist, strings.xml.\n- For an open goal, default to the app's stores, its primary language and that language's country, and say so; ask only for the positioning, once, when nothing gives it.\n\n## Don't\n\n- Don't propose another app's or company's name in visible fields.\n- Don't derive URLs or the copyright line from the app name, or copy them to other languages unasked.\n- Don't truncate to fit.\n- Don't estimate keyword demand or rank when there is no data: say it is unknown.\n- Don't say a listing was saved or sent without a result that says so.\n\n## Pitfalls\n\n- A keyword-field word that search already reads elsewhere wastes room; the knowledge base says which words count as already present.\n- \"Where the app is found\" is not \"where it is sold\".\n- Some fields change only with a new version; promising a same-day edit that needs one disappoints.\n- Locale codes differ between the two stores.\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/text-fields`, `app-store/keywords`, `app-store/versions-and-mutability`, `app-store/localizations`, `app-store/links-and-legal-fields`, `google-play/listing-text`, `cross-store/store-differences`, `cross-store/localization`). When you use one of these facts, give its source and date.\n"
}SHA-256 of public snapshot: 9459c27979390def75799b7046c9d9e251fe9054b6827078f9bd286498e2614e