Claude Code for Google Genkit: Firebase AI Flows — Claude Skills 360 Blog
Blog / AI / Claude Code for Google Genkit: Firebase AI Flows
AI

Claude Code for Google Genkit: Firebase AI Flows

Published: July 2, 2027
Read time: 6 min read
By: Claude Skills 360

Google Genkit is a Firebase SDK for building AI applications — import { genkit } from "genkit" initializes the framework. const ai = genkit({ plugins: [googleAI({ apiKey })], model: gemini15Flash }) configures providers. ai.defineFlow("summarize", { inputSchema, outputSchema }, async (input) => { const { text } = await ai.generate({ prompt: input.text, config: { temperature: 0.3 } }); return { summary: text } }) defines a typed flow. ai.definePrompt("classify", { inputSchema }, "Classify: {{input}}") creates a reusable prompt. ai.defineTool("search", { description, inputSchema, outputSchema }, async ({ query }) => search(query)) adds function calling. ai.defineRetriever("docs", { retrieve: async (query) => await vectorSearch(query) }) adds RAG. const result = await runFlow(myFlow, input) executes a flow. streamFlow(myFlow, input) streams output. Genkit’s developer UI (genkit start) provides tracing and flow testing. Claude Code generates Genkit flows, RAG pipelines, tool-using agents, and typed AI functions.

CLAUDE.md for Genkit

## Genkit Stack
- Version: genkit >= 0.9, @genkit-ai/googleai >= 0.9
- Init: const ai = genkit({ plugins: [googleAI()], model: "googleai/gemini-1.5-flash" })
- Flow: const myFlow = ai.defineFlow({ name: "flowName", inputSchema: z.string(), outputSchema: z.string() }, async (input) => { const { text } = await ai.generate({ prompt: input }); return text })
- Run: await runFlow(myFlow, "input text")
- Stream: for await (const chunk of streamFlow(myFlow, input)) console.log(chunk)
- Prompt: const prompt = ai.definePrompt({ name: "name", input: { schema: z.object({...}) } }, "Template {{field}}")
- Tool: ai.defineTool({ name, description, inputSchema, outputSchema }, async (args) => result)

Genkit Configuration

// lib/genkit/index.ts — Genkit setup with Google AI plugin
import { genkit, z } from "genkit"
import { googleAI, gemini15Flash, gemini15Pro } from "@genkit-ai/googleai"

export const ai = genkit({
  plugins: [
    googleAI({
      apiKey: process.env.GOOGLE_AI_API_KEY,
    }),
  ],
  model: gemini15Flash,
  // Enable tracing in development
  enableTracingAndMetrics: process.env.NODE_ENV === "development",
})

export { gemini15Flash, gemini15Pro }
export { z }

AI Flows

// lib/genkit/flows.ts — type-safe AI flows with tools and RAG
import { runFlow, streamFlow } from "genkit"
import { ai, z, gemini15Flash, gemini15Pro } from "./index"

// ── Schema definitions ─────────────────────────────────────────────────────

const SummarizeInput = z.object({
  text: z.string().min(50).max(20000),
  length: z.enum(["short", "medium", "long"]).default("medium"),
  format: z.enum(["prose", "bullets"]).default("prose"),
})

const SummarizeOutput = z.object({
  summary: z.string(),
  keyPoints: z.array(z.string()),
  wordCount: z.number(),
})

const ClassifyInput = z.object({
  text: z.string().max(5000),
  categories: z.array(z.string()),
})

const ClassifyOutput = z.object({
  category: z.string(),
  confidence: z.number().min(0).max(1),
  reasoning: z.string(),
})

// ── Tools ──────────────────────────────────────────────────────────────────

const searchWebTool = ai.defineTool(
  {
    name: "searchWeb",
    description: "Search the web for current information about a topic",
    inputSchema: z.object({ query: z.string(), maxResults: z.number().default(5) }),
    outputSchema: z.object({
      results: z.array(z.object({ title: z.string(), snippet: z.string(), url: z.string() })),
    }),
  },
  async ({ query, maxResults }) => {
    // In production, call a real search API like Serper, Brave, or Tavily
    return {
      results: [
        { title: `Mock result for: ${query}`, snippet: "Search result content...", url: "https://example.com" },
      ].slice(0, maxResults),
    }
  },
)

const getCurrentDateTool = ai.defineTool(
  {
    name: "getCurrentDate",
    description: "Get the current date and time in UTC",
    inputSchema: z.object({}),
    outputSchema: z.object({ date: z.string(), timestamp: z.number() }),
  },
  async () => ({ date: new Date().toISOString(), timestamp: Date.now() }),
)

// ── Flows ──────────────────────────────────────────────────────────────────

export const summarizeFlow = ai.defineFlow(
  {
    name: "summarize",
    inputSchema: SummarizeInput,
    outputSchema: SummarizeOutput,
  },
  async ({ text, length, format }) => {
    const wordTargets = { short: "50-80 words", medium: "100-150 words", long: "200-300 words" }

    const { output } = await ai.generate({
      model: gemini15Flash,
      prompt: [
        { text: `Summarize the following text in ${wordTargets[length]}.` },
        { text: `Format: ${format === "bullets" ? "Use bullet points for the summary." : "Write in flowing prose."}` },
        { text: `Also extract 3-5 key points as short phrases.\n\nText to summarize:\n${text}` },
      ],
      output: {
        schema: z.object({
          summary: z.string(),
          keyPoints: z.array(z.string()),
        }),
      },
      config: { temperature: 0.3 },
    })

    return {
      summary: output!.summary,
      keyPoints: output!.keyPoints,
      wordCount: output!.summary.split(/\s+/).length,
    }
  },
)

export const classifyFlow = ai.defineFlow(
  {
    name: "classify",
    inputSchema: ClassifyInput,
    outputSchema: ClassifyOutput,
  },
  async ({ text, categories }) => {
    const { output } = await ai.generate({
      model: gemini15Flash,
      prompt: `Classify the following text into one of these categories: ${categories.join(", ")}.
      
Text: "${text}"

Respond with JSON: { "category": "<chosen category>", "confidence": <0-1>, "reasoning": "<brief explanation>" }`,
      output: { schema: ClassifyOutput },
      config: { temperature: 0.1 },
    })
    return output!
  },
)

export const researchFlow = ai.defineFlow(
  {
    name: "research",
    inputSchema: z.object({ topic: z.string(), depth: z.enum(["brief", "detailed"]).default("brief") }),
    outputSchema: z.object({ report: z.string(), sources: z.array(z.string()) }),
  },
  async ({ topic, depth }) => {
    const response = await ai.generate({
      model: gemini15Pro,
      tools: [searchWebTool, getCurrentDateTool],
      prompt: `Research the following topic ${depth === "detailed" ? "in depth" : "briefly"}: ${topic}
      
Use the searchWeb tool to find current information and the getCurrentDate tool to note when this was researched.
Write a ${depth === "detailed" ? "comprehensive" : "concise"} report based on your findings.`,
      config: { temperature: 0.4 },
    })

    return {
      report: response.text,
      sources: ["Web search results (see tool calls)"],
    }
  },
)

// ── Re-exports for callers ─────────────────────────────────────────────────
export { runFlow, streamFlow }

Next.js Server Action Integration

// app/actions/ai.ts — Genkit flows as Next.js server actions
"use server"
import { runFlow, streamFlow } from "@/lib/genkit/flows"
import { summarizeFlow, classifyFlow, researchFlow } from "@/lib/genkit/flows"
import { z } from "zod"
import { createStreamableValue } from "ai/rsc"

export async function summarizeAction(text: string, options?: { length?: "short" | "medium" | "long" }) {
  const result = await runFlow(summarizeFlow, {
    text,
    length: options?.length ?? "medium",
    format: "prose",
  })
  return result
}

export async function classifyAction(text: string, categories: string[]) {
  return runFlow(classifyFlow, { text, categories })
}

export async function streamResearchAction(topic: string) {
  const stream = createStreamableValue("")

  ;(async () => {
    for await (const chunk of streamFlow(researchFlow, { topic, depth: "brief" })) {
      stream.update(chunk)
    }
    stream.done()
  })()

  return { output: stream.value }
}

For the Vercel AI SDK alternative when building primarily Next.js applications with streaming UI components, useChat/useCompletion hooks, and a simpler single-provider focus — Vercel AI SDK is tightly integrated with Next.js streaming while Genkit provides multi-step typed flows, built-in developer UI tracing, and Firebase/Google Cloud integration, see the Vercel AI SDK guide. For the LangChain.js alternative when a more comprehensive chain/agent/memory ecosystem with Python parity, a vast library of document loaders, and extensive third-party integrations are needed — LangChain.js has the broadest ecosystem while Genkit provides tighter TypeScript safety and better Firebase integration, see the LangChain guide. The Claude Skills 360 bundle includes Genkit skill sets covering typed flows, tools, RAG, and streaming. Start with the free tier to try Firebase AI generation.

Keep Reading

AI

Claude Code for email.contentmanager: Python Email Content Accessors

Read and write EmailMessage body content with Python's email.contentmanager module and Claude Code — email contentmanager ContentManager for the class that maps content types to get and set handler functions allowing EmailMessage to support get_content and set_content with type-specific behaviour, email contentmanager raw_data_manager for the ContentManager instance that handles raw bytes and str payloads without any conversion, email contentmanager content_manager for the standard ContentManager instance used by email.policy.default that intelligently handles text plain text html multipart and binary content types, email contentmanager get_content_text for the handler that returns the decoded text payload of a text-star message part as a str, email contentmanager get_content_binary for the handler that returns the raw decoded bytes payload of a non-text message part, email contentmanager get_data_manager for the get-handler lookup used by EmailMessage get_content to find the right reader function for the content type, email contentmanager set_content text for the handler that creates and sets a text part correctly choosing charset and transfer encoding, email contentmanager set_content bytes for the handler that creates and sets a binary part with base64 encoding and optional filename Content-Disposition, email contentmanager EmailMessage get_content for the method that reads the message body using the registered content manager handlers, email contentmanager EmailMessage set_content for the method that sets the message body and MIME headers in one call, email contentmanager EmailMessage make_alternative make_mixed make_related for the methods that convert a simple message into a multipart container, email contentmanager EmailMessage add_attachment for the method that attaches a file or bytes to a multipart message, and email contentmanager integration with email.message and email.policy and email.mime and io for building high-level email readers attachment extractors text body accessors HTML readers and policy-aware MIME construction pipelines.

5 min read Feb 12, 2029
AI

Claude Code for email.charset: Python Email Charset Encoding

Control header and body encoding for international email with Python's email.charset module and Claude Code — email charset Charset for the class that wraps a character set name with the encoding rules for header encoding and body encoding describing how to encode text for that charset in email messages, email charset Charset header_encoding for the attribute specifying whether headers using this charset should use QP quoted-printable encoding BASE64 encoding or no encoding, email charset Charset body_encoding for the attribute specifying the Content-Transfer-Encoding to use for message bodies in this charset such as QP or BASE64, email charset Charset output_codec for the attribute giving the Python codec name used to encode the string to bytes for the wire format, email charset Charset input_codec for the attribute giving the Python codec name used to decode incoming bytes to str, email charset Charset get_output_charset for returning the output charset name, email charset Charset header_encode for encoding a header string using the charset's header_encoding method, email charset Charset body_encode for encoding body content using the charset's body_encoding, email charset Charset convert for converting a string from the input_codec to the output_codec, email charset add_charset for registering a new charset with custom encoding rules in the global charset registry, email charset add_alias for adding an alias name that maps to an existing registered charset, email charset add_codec for registering a codec name mapping for use by the charset machinery, and email charset integration with email.message and email.mime and email.policy and email.encoders for building international email senders non-ASCII header encoders Content-Transfer-Encoding selectors charset-aware message constructors and MIME encoding pipelines.

5 min read Feb 11, 2029
AI

Claude Code for email.utils: Python Email Address and Header Utilities

Parse and format RFC 2822 email addresses and dates with Python's email.utils module and Claude Code — email utils parseaddr for splitting a display-name plus angle-bracket address string into a realname and email address tuple, email utils formataddr for combining a realname and address string into a properly quoted RFC 2822 address with angle brackets, email utils getaddresses for parsing a list of raw address header strings each potentially containing multiple comma-separated addresses into a list of realname address tuples, email utils parsedate for parsing an RFC 2822 date string into a nine-tuple compatible with time.mktime, email utils parsedate_tz for parsing an RFC 2822 date string into a ten-tuple that includes the UTC offset timezone in seconds, email utils parsedate_to_datetime for parsing an RFC 2822 date string into an aware datetime object with timezone, email utils formatdate for formatting a POSIX timestamp or the current time as an RFC 2822 date string with optional usegmt and localtime flags, email utils format_datetime for formatting a datetime object as an RFC 2822 date string, email utils make_msgid for generating a globally unique Message-ID string with optional idstring and domain components, email utils decode_rfc2231 for decoding an RFC 2231 encoded parameter value into a tuple of charset language and value, email utils encode_rfc2231 for encoding a string as an RFC 2231 encoded parameter value, email utils collapse_rfc2231_value for collapsing a decoded RFC 2231 tuple to a Unicode string, and email utils integration with email.message and email.headerregistry and datetime and time for building address parsers date formatters message-id generators header extractors and RFC-compliant email construction utilities.

5 min read Feb 10, 2029

Put these ideas into practice

Claude Skills 360 gives you production-ready skills for everything in this article — and 2,350+ more. Start free or go all-in.

Back to Blog

Get 360 skills free