# Gemini Models Prompt Guide

**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].
```

***

### 4. Specify the Format

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

**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. 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
```

***

### 7. Ground in your Files

Reference files directly to keep Gemini anchored.

**Example:**

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

***

### 8. 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
```

***

### 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.
```

***

#### 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 %}