cmp-firebase-connectlisted

Add Firebase to a create-cmp app and wire it to its OWN real Firebase project. Use this when the user wants Firebase in their app, or asks "add firebase", "connect my app to firebase", "set up google-services.json", "wire firebase", "create a firebase project for this app", "replace the mock firebase config", "get a real GoogleService-Info.plist", "my app still has the REPLACE_ME firebase config". The stamp carries no Firebase: this runs `create-cmp add firebase` (the deterministic step that adds the GitLive SDK, the emulator wiring and a mock config that says it is one), then drives the Firebase CLI end-to-end — login, project create/reuse, Android app registration, the real google-services.json in place of the mock — 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 — add Firebase to a stamped CMP app and wire it to its own project Your job: take a CMP app `create-cmp` stamped — which carries **no Firebase** — add Firebase with `create-cmp add firebase`, 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. > **The code edits are a program's, not yours.** `create-cmp add firebase` adds the GitLive SDK, > the google-services plugin, the debug-build emulator redirect and the config file, and refuses > by name when the app's shape is one it does not recognise. Never hand-edit Gradle, the catalog or > the entry points to wire Firebase; if the step refuses, report its message to the user. > **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), Fi