Context before question
For long inputs, supply the corpus first and end with a focused question tied back to that corpus.
Gemini 3 works best with direct instructions, coherent multimodal context, and the question placed after large source material.
The mental model
“Structure the evidence first, put the actual task last, and use tools for facts or calculation.”
Three levels
Do not add production scaffolding before you can describe and measure a good single-task result.
Avoid making a reasoning model untangle decorative or contradictory instructions.
Keep the question anchored to the evidence across large inputs.
Use the model’s context window without treating it as a current database or calculator.
Starter template
Replace the bracketed text, run it on a real task, and add guidance only when you can name the failure it fixes.
# Context
[Documents, code, images, audio, or video]
# Task
Based on the context above, [specific request].
# Constraints
- Use Google Search grounding for time-sensitive claims.
- Use code execution for arithmetic or counting.
- Mark anything the supplied evidence does not support.
# Output
[Exact format and desired level of detail]For long inputs, supply the corpus first and end with a focused question tied back to that corpus.
Search handles current facts; code execution handles arithmetic and inspection; structured output controls the final shape.
Google recommends keeping Gemini 3 temperature at its default and using thinking level plus prompt instructions for control.
The response summarizes a long document but misses the actual request.
Fix: Put the task after the context and explicitly anchor it to the preceding material.
Low temperature causes degraded or looping behavior on complex Gemini 3 tasks.
Fix: Keep the documented default and control behavior through thinking level, constraints, and output format.
The answer sounds current but relies on training knowledge.
Fix: Turn on Search grounding and require sources for time-sensitive claims.
Current as of July 26, 2026
Google’s current Gemini 3 guidance explicitly favors concise instructions, consistent structure, context-first ordering for long inputs, default temperature, and tools for freshness and computation.
Evidence ledger
Official provider documentation takes priority. Maintainer field notes are useful evidence, but they are labeled separately.
Thinking levels, temperature, thought signatures, long context, migration, and model-specific prompting.
Direct instructions, long-context ordering, multimodal inputs, grounding, code execution, and structured prompts.
Current model naming, stable versus preview aliases, and production versioning guidance.
This guide is reviewed at least every 30 days. Automated checks flag unavailable sources and overdue reviews; substantive advice changes require human verification.