Firebase Ecosystem

Firebase is the Google-backed app backend route when tasks involve Auth, Firestore, Hosting, App Hosting, Data Connect, AI Logic, Crashlytics, Remote Config, or security rules. Source: Ecosystem Capability Coverage, 2026-06-27; Skill Resolver, 2026-06-27

When To Use This

Use Firebase when the app is already on Firebase or the task names one of its products. Use Supabase when the desired backend center is Postgres/RLS. Use Google Workspace pages only for user productivity APIs, not app backend state. Source: Skill Resolver, 2026-06-27

Decision Matrix

Core Model

Firebase is a product family. Auth, Firestore, Hosting, Data Connect, Crashlytics, Remote Config, and AI Logic have different ownership and verification paths. Route to the specific skill after the general Firebase check. Source: Skill Resolver, 2026-06-27

Routing Summary

Preferred order: Firebase MCP for project reads, Firebase Skills first, then product-specific Firebase skills, then firebase CLI for emulators, deploys, auth, and project config. Source: Skill Resolver, 2026-06-27; config/capability-harvest-seeds.json

Failure Modes

• Treating Firestore rules as optional.
• Deploying without confirming project alias.
• Mixing Firebase app backend work with Google Workspace user-data APIs.
• Skipping emulator/rules tests.

Verification Path

Run firebase projects:list, emulator tests, rules tests, or deploy preview/status depending on the work. Always name the Firebase project/environment in the proof. Source: config/capability-harvest-seeds.json; Skill Resolver, 2026-06-27

---

Timeline

• 2026-06-27 | Canonical ecosystem page created to unify Firebase product skills, CLI routing, pack placement, and security-rule verification. Source: User request, 2026-06-27; Ecosystem Capability Coverage