Gemini Guide

Look up Gemini API documentation and SDK patterns when building with Google Gemini. This skill brings Gemini docs TO Claude — it does not call Gemini.

Documentation Sources

Check in this priority order:

Lookup Workflow

When the user asks about a Gemini topic:

1. Check corrections first: Read references/deprecated-patterns.md — know what NOT to suggest before writing any code
2. Fetch latest SDK patterns: Get the GitHub codegen_instructions.md for always-current patterns
3. Map the query to a topic: Read references/topic-index.md — if local docs exist at ~/Documents/google-gemini-context/, read the matching file; otherwise use WebFetch on https://ai.google.dev/gemini-api/docs/{topic}.md.txt
4. Synthesise: Combine the documentation into a clear answer with working code examples. Always use the CORRECT patterns from step 1.

Quick Corrections

These are the most common mistakes. Apply these even without reading the full references:

Correct Initialisation (JS)

import { GoogleGenAI } from "@google/genai";
const ai = new GoogleGenAI({});  // auto-reads GEMINI_API_KEY env var
const response = await ai.models.generateContent({
  model: "gemini-2.5-flash",
  contents: "Your prompt"
});

Correct Initialisation (Python)

from google import genai
client = genai.Client()  # auto-reads GEMINI_API_KEY env var
response = client.models.generate_content(
    model="gemini-2.5-flash",
    contents="Your prompt"
)

Local Docs (Optional)

If you have a local cache at ~/Documents/google-gemini-context/, it contains:

If not available, fall back to WebFetch on Google AI docs (append .md.txt for markdown format).

Current Models

For full model details, check ~/Documents/google-gemini-context/MODELS.md (if available) or https://ai.google.dev/gemini-api/docs/models.

Maintenance

When information seems wrong or outdated:

1. Check the GitHub codegen_instructions.md (always current)
2. Verify model IDs against https://ai.google.dev/gemini-api/docs/models
3. Flag stale docs to the user

Reference Files