firebase-vertex-ai
Execute firebase platform expert with Vertex AI Gemini integration for Authentication, Firestore, Storage, Functions, Hosting, and AI-powered features. Use when asked to "setup firebase", "deploy to firebase", or "integrate vertex ai with firebase". Trigger with relevant phrases based on skill purpose.
What this skill does
# Firebase Vertex AI
Operate Firebase projects end-to-end (Auth, Firestore, Functions, Hosting) and integrate Gemini/Vertex AI safely for AI-powered features.
## Overview
Use this skill to design, implement, and deploy Firebase applications that call Vertex AI/Gemini from Cloud Functions (or other GCP services) with secure secrets handling, least-privilege IAM, and production-ready observability.
## Prerequisites
- Node.js runtime and Firebase CLI access for the target project
- A Firebase project (billing enabled for Functions/Vertex AI as needed)
- Vertex AI API enabled and permissions to call Gemini/Vertex AI from your backend
- Secrets managed via env vars or Secret Manager (never in client code)
## Instructions
1. Initialize Firebase (or validate an existing repo): Hosting/Functions/Firestore as required.
2. Implement backend integration:
- add a Cloud Function/HTTP endpoint that calls Gemini/Vertex AI
- validate inputs and return structured responses
3. Configure data and security:
- Firestore rules + indexes
- Storage rules (if applicable)
- Auth providers and authorization checks
4. Deploy and verify:
- deploy Functions/Hosting
- run smoke tests against deployed endpoints
5. Add ops guardrails:
- logging/metrics
- alerting for error spikes
- basic cost controls (budgets/quotas) where appropriate
## Output
- A deployable Firebase project structure (configs + Functions/Hosting as needed)
- Secure backend code that calls Gemini/Vertex AI (with secrets handled correctly)
- Firestore/Storage rules and index guidance
- A verification checklist (local + deployed) and CI-ready commands
## Error Handling
- Auth failures: identify the principal and missing permission/role; fix with least privilege.
- Billing/API issues: detect which API or quota is blocking and provide remediation steps.
- Firestore rule/index problems: provide minimal repro queries and rule fixes.
- Vertex AI call failures: surface model/region mismatches and add retries/backoff for transient errors.
## Examples
**Example: Gemini-backed chat API on Firebase**
- Request: “Deploy Hosting + a Function that powers a Gemini chat endpoint.”
- Result: `/api/chat` function, Secret Manager wiring, and smoke tests.
**Example: Firestore-powered RAG**
- Request: “Build a RAG flow that embeds docs and answers with citations.”
- Result: ingestion plan, embedding + index strategy, and evaluation prompts.
## Resources
- Full detailed guide (kept for reference): `${CLAUDE_SKILL_DIR}/references/SKILL.full.md`
- Firebase docs: https://firebase.google.com/docs
- Cloud Functions for Firebase: https://firebase.google.com/docs/functions
- Vertex AI docs: https://cloud.google.com/vertex-ai/docs
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.