extension-to-functions-codebase

Habilidade para converter uma extensão do Firebase instalada (ou código-fonte da extensão) em um codebase independente do Cloud Functions for Firebase ou em um pacote npm publicável,…

npx skills add https://github.com/firebase/agent-skills --skill extension-to-functions-codebase

Extension to Functions Codebase & npm Package Migration

Overview

Migrates a Firebase Extension into either:

  1. A local Cloud Functions codebase (functions/src/ for app integration).
  2. A publishable npm package (reusable open-source package exporting V2 functions).

Leverages native Cloud Functions features (declarative IAM, Parameterized Config, SDK Lifecycle Hooks) and modernizes 1st Gen triggers to 2nd Gen using the Destructuring Compatibility Shim.


Target Migration Workflows

  • Target A: Local Functions Codebase (End-User App Integration)

    • Output: Code under functions/src/. Config in .env.
    • Deployment: firebase deploy --only functions.
  • Target B: Publishable npm Package / Shareable Package

    • Output: Reusable npm package exporting V2 functions.
    • Configuration: package.json specifying exports map, engines: { "node": ">=22" }, and peerDependencies: { "firebase-functions": ">=6.0.0" }.
    • Usage: Consumers install package and re-export functions in index.ts (export * from "<package-name>").

Core Rules & Constraints

1. Declarative IAM & APIs (Zero-Local-Overhead)

Use native SDK declarations instead of manual gcloud scripts or console instructions:

  • Use requiresRole("roles/...") for required GCP IAM permissions.
  • Use requiresAPI("service.googleapis.com", "Description") for Google APIs.

2. Global Parameter Access Restriction

  • Never call .value() at top-level module load scope.
  • Initialize global SDK instances inside onInit() or lazy getters:
    import { defineString } from "firebase-functions/params";
    import { onInit } from "firebase-functions/v2";
    
    const dataset = defineString("DATASET_ID");
    let client: BigQuery;
    
    onInit(() => {
      client = new BigQuery({ datasetId: dataset.value() });
    });
    

3. V2 Concurrency & Cost Parity

V2 enables concurrency (up to 80 requests). To preserve V1 single-concurrency pricing, set cpu: "gcf_gen1".


Step-by-Step Migration Execution

Step 1: Inventory Extension Resources

  1. extension.yaml:
    • params → defineString, defineInt, defineBoolean, defineSecret.
    • apis → requiresAPI(...).
    • roles → requiresRole(...).
    • lifecycleEvents → afterFirstDeploy & afterRedeploy.
    • resources → Upgrade 1st Gen triggers to 2nd Gen (onDocumentWritten, onTaskDispatched, onRequest).
  2. Files & Scripts: Preserve devDependencies, test framework (jest), and test scripts.

Step 2: Configure package.json

  • Set name: "<package-name>", engines: { "node": ">=22" }.
  • Set peerDependencies:
    "peerDependencies": {
      "firebase-admin": "^11.0.0 || ^12.0.0",
      "firebase-functions": ">=6.0.0"
    }
    
  • Configure exports map targeting ESM/CommonJS and TypeScript declarations (lib/index.js, lib/index.d.ts).

Step 3: Upgrade Triggers from V1 to V2

  • Firestore: Use onDocumentWritten from firebase-functions/v2/firestore.
  • Tasks: Use onTaskDispatched from firebase-functions/v2/tasks. Remove EXT_INSTANCE_ID when enqueueing tasks.
  • HTTP: Use onRequest from firebase-functions/v2/https.
  • Apply Destructuring Compatibility Shim ({ change, context }, { snapshot, context }) where legacy 1st Gen handlers expect (change, context).

Step 4: Convert Lifecycle Events

Map extension lifecycle events to SDK lifecycle hooks in src/index.ts:

  • onInstall → afterFirstDeploy({ task: { function: "initTask" } })
  • onUpdate / onConfigure → afterRedeploy({ task: { function: "setupTask" } })

Step 5: Package README & Export Instructions

Generate README.md containing:

  1. Installation instructions (npm install).
  2. Re-export snippet (export * from "<package-name>").
  3. Parameterized Configuration .env reference table.
  4. What Changed (Extension vs Package) comparison table.

Reminder: NEVER execute npm publish.

Mais skills de firebase

developing-genkit-dart
firebase
SDK de IA unificado para Dart que permite geração de código, saídas estruturadas, ferramentas, fluxos e agentes. Fornece APIs principais para geração, definição de ferramentas, orquestração de fluxos, embeddings e streaming com uma única interface. Inclui mais de 8 plugins para provedores de LLM (Google Gemini, Anthropic Claude, OpenAI GPT), Firebase AI, Model Context Protocol, integração com navegador Chrome e hospedagem de servidor HTTP via Shelf. CLI integrado com interface de desenvolvimento local para execução de fluxos, rastreamento, experimentação de modelos e...
developing-genkit-go
firebase
Desenvolva aplicações com tecnologia de IA usando Genkit em Go. Use quando o usuário pedir para construir funcionalidades de IA, agentes, fluxos ou ferramentas em Go usando Genkit, ou ao trabalhar…
developing-genkit-js
firebase
Crie aplicativos Node.js/TypeScript com tecnologia de IA usando flows, ferramentas e suporte a múltiplos modelos do Genkit. O Genkit é independente de provedor; suporta Google AI, OpenAI, Anthropic, Ollama e outros provedores de LLM por meio de plugins. Defina flows com esquemas type-safe usando Zod, execute solicitações de geração e componha workflows de IA de várias etapas em TypeScript. Requer Genkit CLI v1.29.0+; mudanças recentes na API significam que você deve consultar genkit docs:read e common-errors.md para padrões atuais, e não conhecimento prévio...
developing-genkit-python
firebase
Desenvolva aplicações com tecnologia de IA usando Genkit em Python. Use quando o usuário perguntar sobre Genkit, agentes de IA, fluxos ou ferramentas em Python, ou ao encontrar Genkit…
developing-genkit-tooling
firebase
Melhores práticas para criar ferramentas Genkit, incluindo comandos CLI e ferramentas de servidor MCP. Aborda convenções de nomenclatura, padrões arquiteturais e consistência…
firebase-ai-logic
firebase
We need to translate the given text from English to Brazilian Portuguese. The text describes a client-side Gemini integration for web apps. We must preserve the name "firebase-ai-logic" but it's not in the text, so we ignore. We must not add any labels or extra commentary. Just translate the text. The text: "Client-side Gemini integration for web apps with multimodal inference, streaming, and on-device hybrid execution. Supports text-only and multimodal inputs (images, audio, video, PDFs); files over 20 MB route through Cloud Storage Includes chat sessions with automatic history, streaming responses for real-time display, and structured JSON output enforcement Offers hybrid on-device inference via Gemini Nano in Chrome, with automatic fallback to cloud execution Requires App Check for production..." We need to translate accurately, preserving technical terms like "Gemini", "Cloud Storage", "Gemini Nano", "Chrome", "App Check", "JSON", "MB". Also "multimodal inference", "streaming", "on-device hybrid execution", etc. Let's translate:
firebase-ai-logic
firebase
Integre o Firebase AI Logic (Gemini no Firebase) para funcionalidades inteligentes no aplicativo. Use ao adicionar capacidades de IA a aplicativos Firebase, implementando IA generativa…
firebase-ai-logic-basics
firebase
Habilidade oficial para integrar o Firebase AI Logic (API Gemini) em aplicações web. Aborda configuração, inferência multimodal, saída estruturada e segurança.