← AppLaunchFlowCONTENT HISTORY
WHAT CHANGED
Update to AppLaunchFlow
Snapshot Oct 28, 2026 · 12:30 UTC · version 1.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save AppLaunchFlow and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Draft, edit and localize AppLaunchFlow App Store and Google Play listing text while preserving existing languages, claims and store character limits.",
"included_files": [
{
"relative_path": "references/tool-catalog.md",
"size_in_bytes": 8156
}
],
"name": "applaunchflow-store-copy",
"skill_md_contents": "---\nname: applaunchflow-store-copy\ndescription: Draft, edit and localize AppLaunchFlow App Store and Google Play listing text while preserving existing languages, claims and store character limits.\n---\n\nCheck that the workflow's named tools are exposed by this host. If one is absent, use the matching AppLaunchFlow editor link and explain the specific step that needs the dashboard; don't claim the step completed.\n\n# Preserve product truth and scope\n\nResolve the project and linked store app with `get_project`. Separate the user's goal: listing copy, keyword discovery/rank monitoring, or publishing to a store. The audited MCP edits listing data and tracking; store publishing happens in the dashboard.\n\nFor existing copy, `get_store_listing` gives the saved source and languages. `update_store_listing` applies requested fields while preserving other languages and AI insights. `generate_store_listing` creates AI copy; use it for a requested draft rather than replacing copy for a small correction. Explicit replacement can retire a variant. `translate_store_listing` creates/refreshes localized copy; inspect existing languages before overwriting edited translations.\n\nKeep app capabilities and claims grounded in user/project input. Respect the tool's store-specific bounds: app name 30 characters, iOS subtitle 30 versus Play short description 80, iOS promotional text 170, descriptions 4000, iOS keyword field 100; release-note limits depend on store. A locale-specific correction should change that locale only.\n\nFor keyword research or monitoring, use the separate [keyword tracking skill](../applaunchflow-keywords/SKILL.md). Do not confuse changing the stored iOS keywords text field with adding tracked search terms.\n\nSee [the store-copy tool catalog](references/tool-catalog.md) for fields and language inputs. Preview exact proposed copy and character counts when a limit is close. Say that copy was saved in AppLaunchFlow, not published to a store.\n"
}SHA-256 of public snapshot: db2daa045beacc59b3c4a0d757ff2954e172e31a9aa8f86071d216ce4df6980b