A practical guide to writing Gemini prompts for research, writing, planning, coding, visual work, and everyday tasks with clear goals and useful context.
A strong Gemini prompt explains the task, context, inputs, constraints, and desired output. When reference material is provided, say exactly what should be extracted, transformed, or compared.
- Task and objective
- Context and audience
- Inputs or reference material
- Constraints
- Output format
- Success criteria
Define the research question and the level of depth you need. If the result will support an important decision, request clear separation between established information, assumptions, and items that need verification.
- Exact research question
- Scope and timeframe when relevant
- Comparison criteria
- Source material
- Uncertainty or gaps
- Verification of important claims
Give Gemini the audience, purpose, tone, and structure. If you already have source copy, state what may be changed and what must remain accurate.
- Audience
- Content goal
- Tone and voice
- Source material
- Required sections
- Length or platform constraints
Technical prompts should describe the environment and existing behavior before the requested change. Include the exact error and relevant code instead of describing the problem only in general terms.
- Language and framework
- Version and environment
- Expected behavior
- Actual behavior and error
- Relevant code
- Testing requirements
Visual prompts should identify the subject, action, environment, composition, lighting, mood, and style. Put the most important visual requirements where they are easy to understand.
- Subject and action
- Setting and background
- Composition and viewpoint
- Lighting and mood
- Visual style
- Important exclusions
If you give Gemini an article, notes, image, document, or other source, explain how the material should influence the answer. This reduces the chance of a generic response.
- State what the reference contains
- Say what to extract or transform
- Specify what not to infer
- Define the final output
- Ask for missing information
If a result is close but not correct, identify the exact mismatch and refine that instruction. Keeping successful requirements makes iteration more predictable.
- Identify the failed part
- Keep successful instructions
- Change one major variable
- Test again
- Save the version that works
Avoid broad requests with no audience, goal, or output structure. More adjectives or more words do not automatically create a better result.
- No clear outcome
- Missing context
- Conflicting instructions
- No output structure
- Overly broad request
- Unverified factual claims
Start with the result you need, add only context that changes the answer, and make important constraints explicit. Test the prompt with a real example before treating it as a finished template.