mobile-automation-plugin

Automates the full mobile app release pipeline — version management, localized metadata, multi-device screenshot generation, i18n translations, and store submission for iOS and Android. Use when the user asks to "release my app", "bump the version", "generate store screenshots", "update metadata in all languages", "prepare a store submission", "sync translations", or "manage my app versions across platforms". Orchestrates sub-skills: managing-app-versions, generating-store-screenshots, managing-store-metadata, managing-app-localizations, submitting-app-release.

Manages the two-phase store screenshot pipeline: Phase 1 captures raw screenshots by automatically exploring the running iOS Simulator or Android Emulator — booting the device, launching the app, navigating every key screen, and capturing numbered PNGs; Phase 2 adds design layers (device frames, headlines, backgrounds) exclusively via ParthJadhav/app-store-screenshots (MIT). Outputs are grouped by locale/platform/device-size so folders can be downloaded and uploaded directly. Use when the user says "generate screenshots", "update store images", "take screenshots", "design marketing slides", or "screenshot pipeline".

Manages i18n translation files and store metadata localization across iOS, Android, and Google Play. Use when the user says "add a language", "fix missing translations", "translate strings", "audit i18n", "missing locale keys", or any task involving language support. Source of truth for translation keys is .msd/locales/{app-id}/en.json.

Validates iOS and Android app permissions — checks that all iOS NSUsageDescription strings are present and non-empty, detects dangerous or deprecated Android permissions, and cross-references declared permissions with actual API usage in the codebase. Use before every store submission to avoid rejection. Use /msd-permissions to run interactively.

Manages the registry of known apps in .msd/memory/apps.json. Use when initializing a new app, updating app state (first release complete, new locale added), discovering apps in a directory, or reading current app status. Always read the registry before any release operation to check if first-release setup is complete.

Manages semantic versioning for mobile apps across iOS and Android platforms. Use when the user says "bump version", "increment build number", "set version to", "release patch/minor/major", or "sync build numbers". Single source of truth is .msd/versions/{app-id}/version.json. Syncs to app.json (Expo), Info.plist (native iOS), and build.gradle (native Android).

Manages App Store Connect and Google Play Console metadata — names, subtitles, keywords, descriptions, and release notes — enforcing Apple and Google hard character limits. Use when the user says "update description", "change keywords", "edit metadata", "update release notes", or "validate store copy". Always run validate-metadata.js after any edit before uploading.

Optimizes App Store Optimization (ASO) strategy across all metadata fields for both Apple App Store and Google Play. Covers keyword research, competitor gap analysis, character-limit-aware copy, and screenshot caption alignment with Apple OCR indexing. Use when the user says "optimize keywords", "improve ASO", "keyword research", "improve ranking", or "write metadata". Use lenses/aso-optimizer.lens.md for AI-powered metadata generation per locale.

Optimizes Generative Engine Optimization (GEO) — making the app discoverable when users ask AI assistants (Claude, ChatGPT, Gemini, Perplexity) for app recommendations. Covers entity anchor sentences, JSON-LD schema markup, ProductHunt copy, press releases, and 30-day AI visibility action plans. Use when the user says "GEO optimization", "AI discoverability", "schema markup", "entity anchoring", or "ProductHunt launch". Use lenses/geo-optimizer.lens.md for AI-powered GEO content generation.

Enforces locale selection before any localisation, metadata, screenshot, or i18n task begins. Use when starting a new app, adding languages, preparing for store submission, or any time the locale set is unknown or unconfirmed. Presents both the Android BCP 47 locale list (locale_config.xml) and the Apple App Store storefront table (175 regions, default and additional languages) so the user can make an informed, explicit decision. Writes the confirmed locale set to .msd/config/{app-id}.config.json before any other skill runs.

Runs pre-flight validation gates and submits the app to App Store Connect and Google Play Console via EAS CLI. Use when the user says "release", "submit to store", "publish", "deploy app", or "submit for review". Always runs release-checklist.js first — never submits past a failing gate without explicit user confirmation.