Setup Accounts - NowStack Mobile

The whole point of this skill is API access, not hand-holding. For each service the goal is one thing: obtain a credential the CLI/API can use (a token, a deploy key, a service-account JSON, an ASC .p8), persist it in the correct place, and verify it works. From that moment on, every action on that service is automated through the credential — npx convex env set, vercel deploy, eas submit, asc ... — never by clicking in the web UI.

<core_principle> Minimize what the user does to the irreducible manual steps only — the things a provider physically forces a human to do:

• the initial browser signup (email + payment + accepting terms),
• 2FA / identity verification,
• downloading a one-time secret the provider only shows once (Apple .p8, Google service-account JSON),
• a permission grant that only exists in the web UI (e.g. inviting a service account in Play Console).

Everything else, the skill does itself via the acquired API access: creating tokens that CAN be created from the CLI, writing env vars, editing config, running deploys, validating. When you need the user, ask for exactly one thing, tell them the exact URL, and wait. Never say "go configure X somewhere" — either do it yourself with the credential, or ask for the single value and then write it. </core_principle>

node scripts/check-setup.mjs --accounts

Parse the service|status|hint lines: ready = API access already obtained, skip; todo = acquire it now; skip-ok = optional, offer to skip. Ask the user up front which surfaces they ship (iOS? Android? web? payments?) so whole branches can be skipped. Then work the accounts in the order below.

1. Apple Developer — first if shipping iOS; identity review can take 24–48h.
2. Google Play — second if shipping Android; identity review also takes days (the account may be "pending verification" — set up the API access now anyway so publishing is one command once approved).
3. Convex — required; the app won't run without it.
4. Expo / EAS — any mobile build.
5. Vercel — web app + admin.
6. Stripe — only if taking payments on web/Android (iOS uses Apple IAP).
7. Social sign-in (Google / Apple OAuth) — instant, do last; only for providers whose SiteConfig.features.enable<Provider>SignIn flag is on. Email-OTP needs none of this.

Per-account playbooks

Each playbook follows the same spine: acquire API access → store → verify → from now on, automated.

npm run check-setup

Summarize per service: API access obtained / skipped (and what skipping blocks), where each credential lives, and the recommended next command — usually /ns setup to turn the boilerplate into the real product.