Genkit

Use this skill when the main question is "should this Firebase AI feature be a direct client SDK integration or a reusable server-owned Genkit workflow?"

The job is not to dump a long Genkit tutorial, CLI catalog, or Firebase product tour. Frame the current packet, choose one ownership boundary and operating mode, then keep Firebase platform operations and broad framework comparisons routed to adjacent skills.

Read references/intake-packets-and-fallbacks.md before handling mixed or ambiguous requests. Read references/modes-and-routing.md before choosing a primary mode. Read references/deployment-and-runtime-boundaries.md when runtime choice is the real open question. Read references/evals-and-observability.md when the workflow already exists and confidence is the bottleneck.

When to use this skill

• A mobile or web app needs direct Firebase AI Logic client SDK integration, including model setup, structured output, streaming, App Check, or safe client/server boundaries
• A backend or full-stack feature needs a reusable Genkit flow instead of one-off provider calls scattered through route handlers
• The work needs typed contracts, tool calling, retrieval, prompt files, evaluation, tracing, or deployment under a server-owned boundary
• The request is explicitly about Firebase AI Logic, Genkit, or deciding between their client-owned and server-owned shapes
• An existing Firebase AI feature needs debugging, evaluation, observability, or launch-readiness review