A field guide · v1.0

How to talk
to Gemini.

A working manual for prompting Google's models — built on the idea that directness, well-placed structure, and grounded inputs are what turn a vague request into a useful answer. Use the interactive flow below to assemble a prompt for your exact situation.

01 / Interactive flow

Find your prompt shape.

Pick the kind of work you're doing. The flow narrows toward a tailored template, a checklist of what to include, and the pitfalls most people hit.

02 / Principles

Six things that always help.

Independent of the task. Gemini specifically rewards direct phrasing, question-last ordering, and grounding in real inputs over generic instructions.

01

Be direct, skip the persuasion

Gemini 3 favors directness over verbosity. "Summarize this in 100 words" beats "I'd really appreciate it if you could maybe help me by summarizing this." No hype, no flattery — those phrases actively hurt newer models.

good"Summarize the attached doc in 5 bullets. Each bullet ≤15 words. Focus on decisions."
02

Put the question last

Google's own prompting whitepaper recommends placing your specific question AFTER the data and context, not before. Gemini's attention is best at the end of the prompt — that's where it commits to action.

good[role] → [context] → [data block] → [the actual question]\n\nNot: [question] → [a bunch of context after]
03

Always include examples

Google explicitly recommends few-shot over zero-shot. One example calibrates format; 2–3 nail it. This is more emphasized for Gemini than for other models — don't skip it.

goodInput: "ship it" → {"tone":"casual"}\nInput: "Please advise." → {"tone":"formal"}\nNow classify: "asap pls"
04

Frame everything positively

"Only use the data in <context>" outperforms "don't make things up" — every time. The Pink Elephant Problem: negative instructions force the model to think about the forbidden thing first.

good"Use everyday vocabulary and short sentences" beats "don't use jargon, don't be verbose."
05

Use Gemini's native superpowers

Live Google Search grounding, 1M+ token context, native multimodal (images, video, audio, code), Workspace integration. If your task involves any of these, lean on them — don't paste paragraphs of stale info Gemini could just fetch.

good"Using Google Search, find 3 recent (2025–2026) studies on X. Then write a brief from them."
06

Ask explicitly for verbosity

Gemini 3 defaults to short, efficient answers. If you want long, detailed, or step-by-step output, you have to ask. The reverse of older models where you were trying to get them to shut up.

good"Provide a detailed analysis with section headings, examples, and reasoning shown — at least 800 words."
03 / Anatomy

A prompt, dissected.

Click any segment to see what role it plays. Gemini accepts either XML tags OR markdown headings — pick one and stay consistent within a single prompt.

ROLE<role> You are a senior backend engineer reviewing a pull request for a payment-processing service. You are precise, analytical, and care about idempotency. </role> CTX<context> Codebase is Python 3.11, FastAPI + SQLAlchemy. The team values explicit code over clever abstractions. Deployed to Google Cloud Run. </context> EX<example> Good review feedback: "Line 14: db.query().get() is deprecated in SQLAlchemy 2.x. Use session.get(Order, order_id) instead. Risk: silent deprecation warnings in logs." </example> DATA<diff> + def process_refund(order_id): + order = db.query(Order).get(order_id) + stripe.Refund.create(charge=order.charge_id) </diff> TASK<task> Identify the three most important issues in the diff. For each: explain the risk in one sentence, propose a concrete code change. Output as Markdown with H3 per issue. </task> GUARD<constraints> Focus only on correctness issues. Mark uncertain behaviors as [UNCERTAIN] rather than guessing. </constraints>
04 / Pattern library

Specialized moves.

Techniques worth knowing by name. Reach for these when the default prompt isn't getting you there.

Grd

Search grounding

Gemini's killer feature: instruct it to use Google Search for current data, then write from real sources. Cite specific statistics from 2025–2026, not stale training data.

"Using Google Search, find 3+ recent statistics on [topic] from 2025–2026. Then write [deliverable]."
Few

Few-shot examples

Google's whitepaper explicitly prefers few-shot over zero-shot for Gemini. Show 2–5 input/output pairs before the real input — especially powerful for classification, extraction, and style-matching.

<example> Input: ... Output: ... </example>\n<example> Input: ... Output: ... </example>
Mod

Multimodal grounding

Upload images, PDFs, video, or audio directly. Reference them by content in your prompt: "In the screenshot, the error appears at the top right." Native multimodal is Gemini's strength.

"[image attached] Identify all UI bugs visible. For each, name the affected element and the issue."
Long

Long-context hygiene

Gemini's 1M token window is real, but reasoning still degrades past ~3000 tokens. Place questions AFTER documents. Wrap each input in tags. Don't dump 50 files — curate.

<doc id="1">...</doc> <doc id="2">...</doc>\n\nQuestion (cite sources): ...
Plan

Plan → Execute → Validate

Gemini 3 responds well to explicit workflow structure: 1) Plan with sub-tasks. 2) Execute and track progress. 3) Validate output against the original task. 4) Format the answer.

"1. Plan steps. 2. Execute with [x]/[ ] tracking. 3. Validate. 4. Output final result only."
DR

Deep Research mode

For multi-source research, use Gemini's Deep Research feature instead of a regular prompt. It plans, searches, browses dozens of sources, and produces a structured report.

Switch to Deep Research → "Comprehensive market analysis of X. Cover: size, competitors, trends, gaps."