mobile-app
Installation
SKILL.md
Mobile app: build, check, ship
You are the orchestrator. You do not replace the bundled skills: at each stage, load the skill named here and follow it. Skill names below are folder names in this pack. If the pack was installed as a Claude Code plugin, the same skills appear with the mobile-app-skill: prefix (for example mobile-app-skill:asc-release-flow).
The path is always the same: intake -> pick the stack -> build -> store setup -> check -> ship -> watch review. Do not skip the check stage.
Rules that apply at every stage
- Say the limits before starting, once. Read references/limits.md and tell the user the ones that apply to them. The short version:
- Apple Developer Program costs $99 a year. Google Play Console costs $25 once.
- An iOS binary needs a Mac with Xcode, or a cloud build (EAS, paid plan limits apply).
- New personal Google Play accounts must run a closed test with 12 testers for 14 days before production.
- With
gplay, the app's initial setup and first upload are manual steps in Play Console. - No tool, including this one, can guarantee approval. Apple and Google decide.
- Never promise approval, a review time, or a rejection-free submission. Report the furthest state you verified and nothing past it.
- Dry-run before you mutate. Every store-changing command gets its
--dry-runfirst. Ask the user before adding--confirm, before any production release, and before cancelling a submission. - Do not invent commands.
ascandgplaychange often. Before running a command you have not seen in a bundled skill, loadasc-cli-usageorgplay-cli-usageand checkasc <command> --help,asc search "<intent>", orgplay <command> --help. - Secrets stay out of the repo. API keys (
AuthKey_*.p8), service-account JSON and keystores are never committed, printed or pasted into chat.