cmp-firebase-connect

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 is a program in the stamped app; this skill does not restate it. create-cmp add firebase (§1 step 4) ships qa/hooks/firebase-consent.mjs and registers it in the app's .claude/settings.json as a PreToolUse hook: when a command would run projects:create, apps:create, firestore:databases:create or apps:android:sha:create, Claude Code asks the user first, naming the mutation. The hook asks and never allows. Run the add step before any cloud command, so the hook is there when one runs.

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.
2. Logged in — firebase login:list. If it reports no accounts, run firebase login. Tell the user first: this opens an interactive browser OAuth flow they must complete themselves; you cannot do it for them. On a headless/remote box use firebase login --no-localhost. Do not proceed until login:list shows an account.
3. Read the app's identity from the stamped project (never ask the user to retype what the repo already knows):
   • Android applicationId — from composeApp/build.gradle.kts (the applicationId = "..." line inside android { defaultConfig { … } }).
   • iOS bundle id — from iosApp/project.yml (PRODUCT_BUNDLE_IDENTIFIER / bundleIdPrefix). iOS is optional and currently deferred product-wide — do the Android wiring first and only take the iOS branch (§5) if the user explicitly wants it now.
4. Add Firebase, if the app has none yet — read create-cmp.json's firebase record.
   • Absent: run the add step. It edits only this repo's files, writes nothing until its whole plan is made, and changes nothing on a second run — tell the user what it does, then: