> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/for-users/prompt-writing-guide/gemini-models-prompt-guide.md).

# Gemini Models Prompt Guide

Gemini responds best when your prompts are clear, structured, and grounded. A simple formula makes it easy: P–T–C–F → Persona, Task, Context, Format.

**Table of Contents**

1. [Start with a Persona](#id-1.-start-with-a-persona)
2. [Define the Task Clearly](#id-2.-define-the-task-clearly)
3. [Add Context](#id-3.-add-context)
4. [Specify the Format](#id-4.-specify-the-format)
5. [Keep it Natural and Concise](#id-5.-keep-it-natural-and-concise)
6. [Iterate and Refine](#id-6.-iterate-and-refine)
7. [Ground in your Files](#id-7.-ground-in-your-files)
8. [Use Power Prompts](#id-8.-use-power-prompts)
9. [Always Review the Output](#id-9.-always-review-the-output)
10. [Practical Prompt Templates by Use Cases](#id-10.-practical-prompt-templates-by-use-case)

***

### 1. Start with a Persona

Tell Gemini *who it should be*. Giving it a role makes answers more realistic and tailored.

**Less effective:**

```
Summarize this report
```

**More effective:**

```
You are a program manager in the healthcare industry. Summarize this report for executives.
```

***

### 2. Define the Task Clearly

Use a **verb**: summarize, draft, compare, rewrite, create. Clear actions = clear results.

**Example:**

```
Draft an executive summary email for the attached report
```

***

### 3. Add Context

Explain **why** you need the output and **where it will be used**. This avoids generic results.

**Example:**

```
This summary will be used in an upcoming board presentation based on @[Project Roadmap Doc].
```

*Tip: When providing large amounts of context, such as documents or data, provide the context before the instructions*

***

### 4. Specify the Format

Say exactly how you want the answer delivered: bullets, table, JSON, slides, short paragraph. Be precise and structured

**Example:**

```
Limit to 5 bullet points under 20 words each
```

***

### 5. Keep it Natural and Concise

Write prompts like you’re talking to a colleague. Avoid over-engineering.

*Tip: The sweet spot is \~20 words. Enough detail to be clear, but not so much that it’s cluttered.*

***

### 6. Provide Examples

The fastest way to get exactly what you require is to provide Gemini with examples. If you need specific tones or layouts show the model what “right” looks like

***

### 7. Iterate and Refine

Don’t stop at the first draft. If Gemini misses the mark, add more detail and try again.

**Prompt idea:**

```
Good, now expand the summary into 3 sections: background, decisions, and next steps
```

***

### 8. Ground in your Files

Reference files directly to keep Gemini anchored. Provide strict rules to prevent the model from creating information

**Example:**

```
Summarize @[Customer Feedback Q3] into 5 themes for the leadership team
```

***

### 9. Use Power Prompts

In Gemini Advanced, you can ask it to rewrite your prompt for clarity.

**Example:**

```
Make this a power prompt: Turn my notes into a client-ready proposal
```

***

### 10. Break Down Complex Tasks

If you have massive tasks, break it down. Have the model accomplish the task per step to avoid overload with a single prompt

**Example:**

```
Step 1: Extract all the pain points from these call transcripts.
(Once generated) 
Step 2: Now, group those pain points into 3 themes.
```

***

### 9. Always Review the Output

Gemini can make mistakes. Check for **clarity, accuracy, and tone** before sharing.

***

### 10. Prompt Templates by Use Case

**General Task Prompt**

```
Persona: [Who Gemini should act as].
Task: [Action verb + goal].
Context: [Why this matters, who it’s for].
Format: [How the output should look – list, table, paragraph, etc.].
Tone: [Optional - professional, friendly, concise, etc.].
```

**Analyze a Dataset**

```
Persona: You are a business analyst preparing insights for an executive dashboard.
Task: Analyze the provided dataset and summarize key performance trends.
Context: This will be used in a leadership meeting to guide Q3 strategy. Keep it simple and visually clear.
Format:
1. 1 short paragraph summary
2. 3 bullet-point insights
3. 1 recommendation section (2 sentences max)
Tone: Professional, factual, and concise. Avoid jargon or statistical notation.
Note: Keep the analysis conversational and grounded. Imagine explaining it aloud to an exec in under a minute.
```

**Summarize Emails and Next Steps**

<pre><code>Persona: You are an operations coordinator summarizing a long internal email thread.
Task: Write a brief summary and list next steps with owners.
Context: The summary will be shared with management to confirm alignment on tasks.
Format:
<strong>1. Summary: 3–4 lines capturing discussion points
</strong>2. Decisions: Bulleted list
3. Next Steps: Tasks with names and deadlines
4. Tone: Clear, neutral, and professional.
</code></pre>

**Generate Marketing Content**

```
Persona: You are a marketing copywriter at an AI company.
Task: Write a LinkedIn post promoting a new AI product feature.
Context: The target audience is business leaders who want practical benefits, not technical details.
Format:
1. Headline: 1 line under 12 words
2. Body: 3 short sentences (what, why it matters, call to action)

Tone: Engaging, confident, and human. Avoid over-engineering or buzzwords.
```

**Act as a Sales Assistant**

```
Persona: You are a sales assistant following up after a client demo.
Task: Draft a short and warm follow-up email that reinforces value and suggests next steps.
Context: The goal is to reconnect without sounding pushy.
Format:
1. Greeting
2. 1-sentence recap of demo
3. 2 bullet points of value or benefits
4. Clear call to action (e.g., “Let’s schedule a 15-minute call next week.”)
Tone: Friendly, respectful, and action-oriented.
```

***

### Gemini 3 Tips

1. **Tell the model how much you want it to talk.** Gemini 3 is designed to provide concise and straight-to-the-point answers.
   1. Say: “Write a long, highly detailed explanation”
   2. Don’t just say: “Explain this…”
2. **Turn on “Deep Thinking”:** Gemini 3 has a built-in thinking engine. You no longer need to write out its step-by-step logic or request to show its work.
3. **Prioritize critical instructions:** Place essential constraints, roles, and format requirements at the beginning of the user prompt.
4. **Current day accuracy:** Add clauses or knowledge cutoffs to the instructions to aid the model to pay attention to current day
   1. Say: “Remember it is 2026 this year”
   2. Say: “Your knowledge cutoff date is August 30, 2026
5. **Ground rules for Big Tasks.** For the model to accomplish, multi-step jobs like heavy research or data organization, state when it is allowed to guess and when it needs to stop.
   1. Do Say: "Rely only on the facts in the text I provided. If the answer isn't in the text, say 'I don't know.'”
   2. Do Say: "If a detail is missing, stop and ask me for clarification. Do not make assumptions or guess.”

***

#### Final Tip

Think P–T–C–F every time. If Gemini knows *who it is, what to do, why it matters, and how to format*, you’ll get sharper results every time.

{% hint style="info" %}
*Learn more about Gemini Prompt Engineering in Google’s* [*Prompting Guide 101*](https://services.google.com/fh/files/misc/gemini-for-google-workspace-prompting-guide-101.pdf)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.blockbrain.ai/for-users/prompt-writing-guide/gemini-models-prompt-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.