Loading...
Loading...
Found 92 Skills
Mobile game development principles. Touch input, battery, performance, app stores.
Guide for migrating an existing web app, PWA, or SPA into a store-ready Capacitor iOS and Android app. Use this skill when users want to wrap or convert a web app into a mobile app, avoid thin WebView app store rejection, add native-feeling UX, handle permissions, offline behavior, account deletion, billing, testing, and Capgo live updates.
Guidance for using the App Store Connect CLI in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
Expert blueprint for mobile platforms (Android/iOS) covering touch controls, virtual joysticks, responsive UI, safe areas (notches), battery optimization, and app store guidelines. Use when targeting mobile releases or implementing touch input. Keywords mobile, Android, iOS, touch, InputEventScreenTouch, virtual joystick, safe area, battery, app store, orientation.
Metadata and localization sync (including Fastlane format) for Google Play Store listings. Use when updating app descriptions, screenshots, or managing multi-locale metadata.
Develop React Native, Flutter, or native mobile apps with modern architecture patterns. Masters cross-platform development, native integrations, offline sync, and app store optimization. Use PROACTIVELY for mobile features, cross-platform code, or app optimization.
Legal document generation and compliance guidance for indie Apple developers. Covers privacy policies, terms of service, EULAs, GDPR/CCPA/DPDP compliance, and Apple App Store legal requirements. Use when user needs legal documents or compliance guidance.
Initialise a project's App Store Connect context using the `asc init` command. Use this skill when: (1) Saving app context to a project directory: "asc init", "pin my app ID", "set up project context" (2) Auto-detecting the app from an Xcode project: user says "run asc init in my project folder" (3) Searching by app name: "asc init --name 'My App'" (4) Explaining what .asc/project.json is used for (5) Reading saved project context to avoid running asc apps list every session
Manage Game Center features using the `asc` CLI tool. Use this skill when: (1) Getting Game Center detail for an app: "asc game-center detail get --app-id ID" (2) Listing achievements: "asc game-center achievements list --detail-id ID" (3) Creating achievements: "asc game-center achievements create --detail-id ID --reference-name NAME --vendor-identifier ID --points N" (4) Deleting achievements: "asc game-center achievements delete --achievement-id ID" (5) Listing leaderboards: "asc game-center leaderboards list --detail-id ID" (6) Creating leaderboards: "asc game-center leaderboards create --detail-id ID --reference-name NAME --vendor-identifier ID --score-sort-type ASC|DESC --submission-type BEST_SCORE|MOST_RECENT_SCORE" (7) Deleting leaderboards: "asc game-center leaderboards delete --leaderboard-id ID" Trigger phrases: "game center", "achievements", "leaderboards", "arcade enabled", "score sort", "best score", "most recent score"
When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.
When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.
When the user wants to design or optimize the funnel that takes web visitors into installing and onboarding the app — including smart app banners, web-to-app deep links, deferred deep links, web onboarding (Stripe-paid web flow before app install), QR codes, "open in app" CTAs, and the trade-off between paying on web vs in-app. Use when the user mentions "web to app", "smart app banner", "Stripe before app", "web paywall before install", "Branch web SDK", "web funnel for app", "AppsFlyer OneLink web", "Universal Links", "App Links", "QR code to app", "open in app", "deferred deep link from web", or "should I sell on web first then push to app". For pure in-app onboarding, see onboarding-optimization. For deep link infra, see attribution-setup.