Firebase and Azure Skill Families
Firebase and Azure are large product families: start with the ecosystem page, then route to the specific skill that owns the product, safety check, and verification path. Source: User request, 2026-06-27; Firebase Ecosystem; Azure Ecosystem
When To Use This
Use this page when a task touches Firebase or Azure but the product boundary is not yet clear. It prevents generic cloud/backend advice from flattening Auth, Firestore, App Hosting, Entra, App Insights, Foundry, Kusto, storage, and deployment into one blob. Source: Skill Resolver, 2026-06-27
Decision Matrix
| Need | Route | Verification |
|---|---|---|
| Firebase general setup | Firebase Skills | Project/emulator proof |
| Firestore/rules | Firebase Skills and Firebase Skills | Allowed/denied tests |
| Azure account preflight | Azure Skills | az account show |
| Azure deploy/resource work | Azure Skills / Azure Skills | What-if/readback |
| Microsoft AI/Foundry | Azure Skills and Azure AI skills | Service-specific result |
Core Model
Firebase is app-backend product routing. Azure is cloud-platform product routing. Both require project/account confirmation before mutation and product-specific verification after mutation. Source: Firebase Ecosystem; Azure Ecosystem
Tool And Skill Routing
Use Firebase Ecosystem and Azure Ecosystem for ecosystem selection. Then load the specific skill: Firebase Auth, Firestore, Hosting, Data Connect, Crashlytics, Remote Config, or Azure prepare, lookup, deploy, diagnostics, cost, storage, AKS, Entra, App Insights, AI Gateway, Kusto, RBAC, and Foundry. Source: Skill Resolver, 2026-06-27
Failure Modes
- Deploying to the wrong Firebase project or Azure subscription.
- Treating identity, authorization, and hosting as one concern.
- Skipping rules tests, what-if, preview, or readback.
- Promoting one skill page as the whole ecosystem.
Evidence And Timeline
Proof should include Firebase project ID or Azure tenant/subscription/resource group, the product-specific command or skill used, and readback/test evidence. Source: Firebase Ecosystem; Azure Ecosystem
Concept Position
| Field | Value |
|---|---|
| Concept family | Capability, tool, and skill routing |
| Concept owned | Firebase and Azure are large product families: start with the ecosystem page, then route to the specific skill that owns the product, safet... |
| Category map | Concept System Map |
Timeline
- 2026-07-01 | Concepts category refresh added this page to the Capability, tool, and skill routing family, linked it to Concept System Map, and kept it standalone because it owns this reusable mental model: Firebase and Azure are large product families: start with the ecosystem page, then route to the specific skill that owns the product, safet... Source: User request, 2026-07-01
- 2026-06-27 | Canonical cluster page created to unify Firebase and Azure skill-family routing after the ecosystem coverage rollout. Source: User request, 2026-06-27