cmp-firebase-connectlisted

Wire a freshly scaffolded CMP/KMP app to its OWN real Firebase project — the #1 post-scaffold manual step. Use this when the user wants to connect their app to Firebase, or asks "connect my app to firebase", "set up google-services.json", "wire firebase", "create a firebase project for this app", "replace the placeholder firebase config", "get a real GoogleService-Info.plist", "my app still has the REPLACE_ME firebase config", or right after cmp-new as post-scaffold onboarding. Drives the Firebase CLI end-to-end — login, project create/reuse, Android app registration, real google-services.json in place of the placeholder — every cloud-mutating command consent-gated, then proves it with a green assembleDebug. Android-first; iOS branch optional/deferred.
kvdm-co-pilot/create-cmp · ★ 0 · API & Backend · score 72

Install: claude install-skill kvdm-co-pilot/create-cmp

# cmp-firebase-connect — wire a stamped CMP app to its own Firebase project Your job: take a CMP app that `create-cmp` stamped with a **placeholder** `google-services.json` (`REPLACE_ME_PROJECT_ID`, zeroed app id) and connect it to a **real Firebase project on the user's account**, using the Firebase CLI — no console clicking for anything the CLI can do. You finish by proving the wiring with a green build. > **Consent rule.** Every command that creates or mutates a cloud resource on the user's Google > account (`projects:create`, `apps:create`, `firestore:databases:create`, `apps:android:sha:create`) > is shown to the user **verbatim first** and run only after an explicit yes. Read-only commands > (`--version`, `login:list`, `projects:list`, `apps:list`, `apps:sdkconfig`, `firestore:locations`, > `--help`) need no gate. Never batch a mutation behind a read. > **Cost honesty.** A fresh Firebase project starts on the **Spark (free)** plan. Nothing in this > flow enables billing, attaches a card, or upgrades to Blaze — and the CLI *cannot* silently do so. > Auth (email/phone within free quota), Firestore, and the free-tier services all work on Spark. > Say this to the user up front so "create a cloud project" doesn't read as "spend money". ## 1. Preflight Run these checks before touching anything; fix in order. 1. **CLI present** — `firebase --version`. If missing, offer (consent-gated — it's a global install on their machine): `npm i -g firebase-tools`, then re-check.