How do I install the Techtide GCP Firebase Developer skill?

Run npx skillmds@latest add techtideohio/techtide-gcp-firebase-developer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Techtide GCP Firebase Developer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Techtide GCP Firebase Developer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Techtide GCP Firebase Developer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Techtide GCP Firebase Developer?

TechTideOhio (@techtideohio) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Techtide GCP Firebase Developer by techtideohio

Name: Techtide GCP Firebase Developer
Author: TechTideOhio

Techtide GCP Firebase Developer

Build, configure, and operate Firebase-powered web and mobile applications - covering Firestore, Firebase Auth, Firebase Hosting, Cloud Functions for Firebase, Firebase Storage, App Check, Firebase Remote Config, and Firebase Analytics. Use when building mobile/web apps with Firebase, setting up authentication flows, designing Firestore data models, deploying Firebase Hosting, or configuring Firebase security rules.

TechTideOhio 349d88a 2 files · 4.9 KB Updated Sep 17, 2026

File contents

GCP Firebase Developer

Overview

Firebase is Google's app development platform for web and mobile. It provides a unified suite of backend services, SDKs, and tooling. Key products: Firestore (NoSQL real-time database), Firebase Auth (identity), Hosting (global CDN), Cloud Functions for Firebase (server logic), Firebase Storage (file storage), App Check (abuse prevention), Remote Config, Analytics.

Quick Start

# Install Firebase CLI
npm install -g firebase-tools

# Login
firebase login

# Initialize project
firebase init

# Deploy
firebase deploy

Reference Directory

Load only when needed:

Scenario	Trigger Keywords	Reference
Firestore data modeling	collection, document, subcollection, NoSQL schema, query design	references/firestore.md
Authentication	auth, sign-in, OAuth, email, phone, anonymous, custom claims	references/auth.md
Security Rules	rules, allow, deny, Firestore rules, Storage rules	references/security-rules.md
Cloud Functions	functions, trigger, callable, HTTP, Pub/Sub, Firestore trigger	references/functions.md
Hosting	deploy, hosting, CDN, SPA, redirect, custom domain	references/hosting.md
App Check	abuse, attestation, reCAPTCHA, DeviceCheck, Play Integrity	references/app-check.md
Emulator Suite	local testing, emulator, integration test	references/emulators.md
Firebase Extensions	extension, marketplace, prebuilt	references/extensions.md

Core Operating Rules

Firebase SDKs come in Web (v9 modular), React Native, Flutter, iOS (Swift), and Android (Kotlin/Java) variants. Always confirm the platform before providing SDK code.
Firestore security rules are the primary access control layer for client-side apps - never assume the app logic is sufficient authorization.
Use Firebase Emulator Suite for local development and integration testing before deploying to production.
App Check is mandatory for production apps to prevent unauthorized API access and quota abuse.
Cloud Functions for Firebase run on Cloud Run (gen2) by default in new projects - prefer gen2 for better performance, concurrency, and VPC connectivity.
Firebase Auth supports custom claims for role-based access - use claims, not Firestore documents, as the authority for authorization decisions.
Never expose service account keys or private Firebase config in client-side code. The Firebase client SDK config (apiKey, projectId) is not a secret - it is safe to embed in client bundles.
Use Firebase Hosting rewrites to serve SPAs and proxy Cloud Functions securely.

Response Shape

Platform/SDK confirmation, Firestore data model, security rules, auth flow, functions, hosting config, App Check setup, test plan with emulators.

Official Docs

Security Notes

Read-only skill. Do not deploy to production, modify Firestore security rules, or change Firebase project settings without explicit approval. Client config (apiKey, projectId) is public - service account keys are private and must never be embedded in client code.

---name: techtide-gcp-firebase-developerdescription: Build, configure, and operate Firebase-powered web and mobile applications - covering Firestore, Firebase Auth, Firebase Hosting, Cloud Functions for Firebase, Firebase Storage, App Check, Firebase Remote Config, and Firebase Analytics. Use when building mobile/web apps with Firebase, setting up authentication flows, designing Firestore data models, deploying Firebase Hosting, or configuring Firebase security rules.---# GCP Firebase Developer## OverviewFirebase is Google's app development platform for web and mobile. It provides a unified suite of backend services, SDKs, and tooling. Key products: Firestore (NoSQL real-time database), Firebase Auth (identity), Hosting (global CDN), Cloud Functions for Firebase (server logic), Firebase Storage (file storage), App Check (abuse prevention), Remote Config, Analytics.## Quick Start```bash# Install Firebase CLInpm install -g firebase-tools# Loginfirebase login# Initialize projectfirebase init# Deployfirebase deploy```## Reference DirectoryLoad only when needed:| Scenario | Trigger Keywords | Reference ||---|---|---|| Firestore data modeling | collection, document, subcollection, NoSQL schema, query design | references/firestore.md || Authentication | auth, sign-in, OAuth, email, phone, anonymous, custom claims | references/auth.md || Security Rules | rules, allow, deny, Firestore rules, Storage rules | references/security-rules.md || Cloud Functions | functions, trigger, callable, HTTP, Pub/Sub, Firestore trigger | references/functions.md || Hosting | deploy, hosting, CDN, SPA, redirect, custom domain | references/hosting.md || App Check | abuse, attestation, reCAPTCHA, DeviceCheck, Play Integrity | references/app-check.md || Emulator Suite | local testing, emulator, integration test | references/emulators.md || Firebase Extensions | extension, marketplace, prebuilt | references/extensions.md |## Core Operating Rules- Firebase SDKs come in Web (v9 modular), React Native, Flutter, iOS (Swift), and Android (Kotlin/Java) variants. Always confirm the platform before providing SDK code.- Firestore security rules are the primary access control layer for client-side apps - never assume the app logic is sufficient authorization.- Use Firebase Emulator Suite for local development and integration testing before deploying to production.- App Check is mandatory for production apps to prevent unauthorized API access and quota abuse.- Cloud Functions for Firebase run on Cloud Run (gen2) by default in new projects - prefer gen2 for better performance, concurrency, and VPC connectivity.- Firebase Auth supports custom claims for role-based access - use claims, not Firestore documents, as the authority for authorization decisions.- Never expose service account keys or private Firebase config in client-side code. The Firebase client SDK config (apiKey, projectId) is not a secret - it is safe to embed in client bundles.- Use Firebase Hosting rewrites to serve SPAs and proxy Cloud Functions securely.## Response ShapePlatform/SDK confirmation, Firestore data model, security rules, auth flow, functions, hosting config, App Check setup, test plan with emulators.## Official Docs- https://firebase.google.com/docs- https://firebase.google.com/docs/firestore- https://firebase.google.com/docs/auth- https://firebase.google.com/docs/hosting- https://firebase.google.com/docs/functions- https://firebase.google.com/docs/app-check## Security NotesRead-only skill. Do not deploy to production, modify Firestore security rules, or change Firebase project settings without explicit approval. Client config (apiKey, projectId) is public - service account keys are private and must never be embedded in client code.

Frequently asked questions