How to prompt Gemini 3 Flash

Gemini 3 Flash follows the same ordering as Gemini 3 Pro (context, task, output, constraints last), but it needs shorter, denser blocks. Flash is built for low latency. Long background essays and padded briefs degrade it, and a word limit placed at the top of the prompt is the constraint it most often drops.

The prompt structure

Use short labeled blocks rather than XML:

Context:
- Sprint 14 ended Friday.
- Shipped: CSV export, SSO login.
- Slipped: audit log (blocked on legal review).

Task:
Write the sprint update for the #product channel.

Output:
Bullets under "Shipped", "Slipped", "Next".

Constraints:
- Maximum 6 bullets.
- Only items listed above.
- No preamble.

For quick tasks, a one-line task with an optional one-line persona is enough. Add Output and Constraints as the job gets more specific, and always keep Constraints last.

Density beats detail

• Prefer bullets over paragraphs in Context.
• Cut decorative background that doesn’t change the answer.
• Keep any persona to one line. A paragraph of backstory takes attention away from the task.
• Don’t add “show your reasoning” sections unless you actually want the reasoning in the output.

A short prompt gets you speed more reliably than asking the model to “be fast”.

Put constraints in one place, at the end

Moving a word cap or formatting rule to the top is the most common Flash failure. Collect every limit into the final block. Don’t scatter the same constraint through Task, Output and Constraints, because duplicates make Flash more likely to drop one of them.

Positive grounding

As with Pro, avoid a blanket “do not infer”. Tell Flash to calculate only from the figures provided and to mark missing numbers as [TBD]. Instead of “don’t make up links”, say “if no source is given, leave the link out”.

If you’re asking for live or current information Flash may not have, tell it to say when it can’t verify something and to answer from what it does know.

Name the output shape

• Tables: name the columns.
• Email: name Subject and Body.
• Code: name the language and whether you want a full file or a diff.
• Language: say which. If you write in another language and don’t specify, Flash may answer in English.

Why Flash prompts go wrong

• Pro-length briefs with nested explanations.
• Constraints placed first, so they get dropped.
• Blanket negatives that stop it deducing anything.
• Several tasks in one prompt without labels.