These are 40 complete, paste-ready prompts for Google Gemini 3.1 Pro — the model with a 1M-token context window, three thinking levels, live Google Search grounding, and Google Workspace access to your Gmail, Drive, Docs, and Sheets. Every prompt follows the Intent → Context → Constraints (ICC) pattern, uses [bracketed placeholders] where you fill in your own details, and includes a one-line note on why it works.
Want the theory behind the strongest prompts here? Read how to prompt Gemini for deep research, and keep the Gemini prompt cheat sheet open while you copy these.
Work & productivity
Five prompts to turn scattered inputs into plans, briefs, and decisions. Medium thinking is the sweet spot for most of these; raise to High for the decision memo.
1. Turn a Messy Brain-Dump Into a Plan
Intent: Turn my brain-dump into an organized action plan.
Context: Here is everything on my mind right now:
[paste your unsorted notes, tasks, and half-formed ideas]
Constraints:
- Group items into themes and label each theme.
- For each item, mark it as a task, an idea, or a question.
- List the 3 highest-leverage tasks I should do first and why.
- End with any missing information you'd need from me.
Keep it scannable with short bullets.Why it works: Naming Intent, Context, and Constraints up front gives Gemini a clear job instead of a vague wall of text.
2. Meeting Prep Brief
Intent: Prepare me for a meeting so I walk in ready.
Context: The meeting is [topic] with [who is attending and their roles]. My goal is [what I want out of it]. Background:
[paste agenda, prior notes, or emails]
Constraints:
- Give me a 5-line situation summary.
- List 3 outcomes I should push for and 3 objections to expect.
- Draft 5 sharp questions I should ask.
- Flag anything I'm missing that could derail the meeting.Best for: Walking into any meeting with a point of view instead of reacting on the fly.
3. Prioritize My Week
Intent: Help me plan a realistic, high-impact week.
Context: My goals this week are [goals]. My commitments and deadlines:
[paste tasks with any due dates]
I have roughly [X] focused hours per day available.
Constraints:
- Sort tasks by impact vs. effort and explain the ranking briefly.
- Build a day-by-day plan that fits my available hours — do not overload any day.
- Call out what to drop or delegate if everything won't fit.Why it works: Giving Gemini your real available hours forces a plan you can actually execute, not a wish list.
4. Summarize a Long Document
Intent: Summarize a long document for a busy reader.
Context: I'm attaching/pasting a [report / contract / PDF / transcript]. The reader is [role] who cares most about [their priority].
Constraints:
- Open with a 3-sentence executive summary.
- Then give the 7 key points as bullets, in priority order.
- Pull out any numbers, dates, deadlines, or commitments verbatim.
- End with the 2-3 questions this document leaves unanswered.Best for: Gemini's 1M-token context — you can paste an entire 900-page PDF and still get one clean summary.
5. Decision Memo From Options
Intent: Help me make a defensible decision and write it up.
Context: The decision is [decision]. My options are:
[Option A]
[Option B]
[Option C]
Constraints I care about: [budget, timeline, risk, team, etc.].
Constraints:
- Use High thinking.
- Score each option against my constraints in a table.
- Give a clear recommendation with your reasoning.
- Write a one-page decision memo I can send to my manager.
- List the top 2 risks of the recommended option.Why it works: Asking for High thinking makes Gemini reason through trade-offs before committing to a recommendation.
Google Workspace (Gmail, Docs, Sheets)
Five prompts that use Gemini's Workspace connection. Connect Workspace in the app first, then reference your files, threads, and transcripts by name.
6. Triage My Inbox From Gmail
Intent: Triage my email so I know what needs me.
Context: Using my Gmail from the last 7 days.
Constraints:
- List every email that needs a reply from me, with sender, subject, and a one-line summary of what they want.
- Separate "reply today", "reply this week", and "just FYI".
- For each reply-needed item, suggest a one-sentence response angle.
- Ignore newsletters and automated notifications.Best for: Clearing a backlog fast — Gemini reads your connected Gmail so you don't scroll through it yourself.
7. Draft a Reply From an Email Thread
Intent: Draft a reply to an email thread in my voice.
Context: Reply to the Gmail thread with [sender] about [subject]. I want to [your goal for the reply]. My tone should be [warm and professional / direct / apologetic].
Constraints:
- Keep it under 150 words.
- Address every open question in the thread.
- Do not invent facts — if you need info I haven't given, leave a [bracketed placeholder].
- Give me two versions: one concise, one slightly warmer.Why it works: Pointing Gemini at the real thread means the reply matches the actual context, not a generic template.
8. Summarize a Meet Transcript Into Actions
Intent: Turn a meeting into a clear follow-up.
Context: Use the Google Meet transcript from my meeting titled "[meeting name]" on [date].
Constraints:
- Write a 5-bullet summary of what was decided.
- List every action item as: owner — task — due date (mark "unassigned" or "no date" where missing).
- Flag any disagreements or unresolved questions.
- Draft a short recap email I can send to attendees.Best for: Meetings you attended but didn't have time to take notes in — the transcript does the capture, Gemini does the structure.
9. Build a Sheet Formula and Explain It
Intent: Give me a working Google Sheets formula and teach me why it works.
Context: In my Sheet named "[sheet name]", I have [describe columns, e.g. dates in A, amounts in B, categories in C]. I want to [what you want to calculate].
Constraints:
- Give me the exact formula to paste, using real column references.
- Explain each part in one line.
- Offer a pivot-table or QUERY alternative if it's cleaner.
- Warn me about any edge cases (blanks, text vs. numbers).Why it works: Describing your real columns lets Gemini return a formula that references your sheet correctly, not a placeholder.
10. Turn a Drive Doc Into Slides
Intent: Turn a document into a presentation outline.
Context: Using my Drive doc named "[doc name]". The audience is [audience] and the talk is [X] minutes.
Constraints:
- Propose a [N]-slide deck: give each slide a title and 3-4 concise bullet points.
- Add a one-line speaker note per slide.
- Suggest one chart or visual per data-heavy slide.
- Keep the narrative arc clear: problem, insight, recommendation, ask.Best for: Reusing a doc you already wrote as the backbone of a Slides deck instead of starting from a blank slide.
Writing & communication
Five prompts for drafting, rewriting, and adjusting tone. Flash handles most of these quickly; use Pro when nuance matters.
11. Rewrite in a Chosen Tone
Intent: Rewrite my text in a specific tone without changing the meaning.
Context: Here is my draft:
[paste text]
Target tone: [confident and warm / formal / plain and direct / friendly].
Audience: [who reads this].
Constraints:
- Preserve every fact and the original intent.
- Cut filler and hedging.
- Give me the rewrite, then a one-line note on what you changed and why.Why it works: Locking the tone and audience separately from the content stops Gemini from drifting off-message while it polishes.
12. Cold Outreach Email
Intent: Write a cold outreach email that gets a reply.
Context: I'm [you / your company] reaching out to [recipient and their role] because [genuine reason]. What I want them to do next is [clear ask].
Constraints:
- Under 120 words, no fluff, no "I hope this finds you well".
- Lead with why I'm relevant to them, not why they're relevant to me.
- One specific, low-friction call to action.
- Write 3 subject lines to A/B test.Best for: Sales, partnerships, or job outreach where a short, specific email beats a long pitch.
13. Shorten Without Losing Meaning
Intent: Cut this down to a target length.
Context: Here is the text:
[paste text]
Target length: [e.g. 100 words / a single tweet / one paragraph].
Constraints:
- Keep every essential fact and the core argument.
- Remove repetition, hedging, and throat-clearing.
- Do not add anything new.
- Show me the trimmed version and the final word count.Why it works: A hard target length plus "add nothing new" forces genuine compression instead of a light edit.
14. Blog Outline From a Topic
Intent: Outline a blog post that's actually useful.
Context: Topic: [topic]. Audience: [who it's for and their level]. Search intent I'm targeting: [what the reader wants].
Constraints:
- Propose a working title and 2 alternates.
- Give an H2/H3 outline with a one-line note on what each section covers.
- Suggest where to add an example, a checklist, or a table.
- List 3 questions the piece must answer to be worth publishing.Best for: Starting a draft with structure and intent already decided so the writing goes faster.
15. Explain This to a Non-Expert
Intent: Explain a complex thing simply and accurately.
Context: Explain [concept or text] to [audience, e.g. a smart 12-year-old / a busy executive / a new hire].
Constraints:
- Start with a one-sentence plain-English definition.
- Use one concrete analogy.
- Give a short real-world example.
- Avoid jargon; if a technical term is unavoidable, define it inline.
- Keep it under 200 words.Why it works: Naming a specific audience calibrates the reading level far better than "explain simply".
Coding & technical
Five prompts for real engineering work. Set thinking to High for anything involving bugs, architecture, or logic. Gemini's 1M context lets you paste large files or a whole module.
16. Review Code for Bugs
Intent: Review this code for bugs and risks.
Context: Language/framework: [e.g. Python 3.12 / React]. What it's supposed to do: [behavior]. Here is the code:
[paste code]
Constraints:
- Use High thinking.
- List concrete bugs and edge cases, most severe first, each with the line and a fix.
- Flag security issues, race conditions, and unhandled errors.
- Suggest 3 tests that would catch these.
- Don't rewrite the whole file unless I ask — point to the specific changes.Why it works: High thinking plus "most severe first" makes Gemini prioritize real defects over style nitpicks.
17. Explain an Unfamiliar Codebase
Intent: Help me understand a codebase I just inherited.
Context: I'm pasting [files / a module / the whole repo]. I'm a [your level] developer new to this project.
Constraints:
- Give me a high-level map: what the main components are and how they connect.
- Trace one full request/flow from entry point to output.
- List the 5 files I should read first and why.
- Flag anything that looks fragile, outdated, or unusual.Best for: Onboarding — the 1M-token window means you can drop in an entire small codebase at once.
18. Write a Function From a Spec
Intent: Write a well-tested function from a spec.
Context: Language: [language]. The function should [inputs → behavior → outputs]. It must handle [edge cases].
Constraints:
- Write clean, commented code following [style/convention].
- Include input validation and clear error handling.
- Add unit tests covering the happy path and the edge cases I listed.
- Explain any non-obvious decision in one line.Why it works: Stating inputs, outputs, and edge cases up front gets you code that matches the spec instead of a rough sketch.
19. Write a Regex and Test It
Intent: Build a regex I can trust.
Context: I need to match [describe the pattern] in [language/flavor, e.g. JavaScript, PCRE].
Here are examples that should match:
[list]
And examples that should NOT match:
[list]
Constraints:
- Give me the final regex and a plain-English breakdown of each part.
- Show it passing every match example and rejecting every non-match example.
- Note any edge cases it won't handle.Best for: Getting a regex right the first time by giving Gemini both positive and negative examples to satisfy.
20. Debug an Error Message
Intent: Diagnose and fix an error.
Context: I'm getting this error:
[paste the full error and stack trace]
Relevant code:
[paste code]
What I expected to happen: [expected]. What actually happens: [actual].
Constraints:
- Use High thinking.
- Give the most likely root cause first, then 2 alternates.
- Provide the exact fix and where it goes.
- Tell me how to confirm it's resolved.Why it works: Expected-vs-actual plus the full trace gives Gemini enough signal to reason about the real cause, not guess.
Research & learning
Five prompts for going deep. Turn on Google Search grounding for anything current, and switch to Deep Research when you need a cited, multi-source report.
21. Deep Research a Topic
Intent: Produce a thorough, cited research report.
Context: Research question: [specific question]. My purpose: [decision or output this feeds]. What I already know: [context].
Constraints:
- Use Deep Research and cite every claim with sources.
- Cover: current state, key players/options, trade-offs, and what's changed recently.
- Include a comparison table where relevant.
- End with a clear recommendation and the 3 open questions worth further digging.Best for: Reports where you need breadth and sources — Deep Research browses hundreds of sites and cites them. See how to prompt Gemini for deep research for the full workflow.
22. Learn a Concept With a Study Plan
Intent: Build me a study plan to learn something properly.
Context: I want to learn [topic/skill]. My current level: [beginner / some experience]. I can spend [X hours/week] and want to be [target ability] in [timeframe].
Constraints:
- Break it into weekly milestones with a concrete outcome each week.
- For each milestone, list one thing to read/watch and one thing to build or practice.
- Point out the concepts people usually get stuck on.
- Suggest how I'll know I've actually learned each part.Why it works: Tying the plan to your real weekly hours and a target ability produces a schedule you can follow, not a reading list.
23. Compare Options With Current Data
Intent: Compare my options using up-to-date information.
Context: I'm choosing between [Option A], [Option B], and [Option C] for [purpose]. What matters most to me: [criteria, e.g. price, features, support].
Constraints:
- Verify with Google Search and use current pricing and features — do not rely on memory.
- Build a comparison table scored against my criteria.
- Note anything that changed recently that I should know.
- Recommend one, with a one-line "choose X instead if..." caveat.Best for: Buying decisions and tool comparisons where stale info would lead you wrong — grounding keeps it current.
24. Summarize a Research PDF
Intent: Understand a dense paper or report quickly.
Context: I'm attaching a [research paper / whitepaper / PDF]. My background in this area is [level].
Constraints:
- Summarize the core claim in 2 sentences.
- Explain the method and why it matters, in plain language.
- List the key findings with the numbers that back them.
- Note the stated limitations and anything that seems overclaimed.
- Give 3 questions I could ask to test the paper's strength.Why it works: Asking for limitations and overclaims turns a summary into a critical read, not just a shorter version.
25. Quiz Me on a Topic
Intent: Test my understanding with active recall.
Context: Quiz me on [topic] at [difficulty level]. Base the questions on [my notes / this doc / general knowledge].
Constraints:
- Ask one question at a time and wait for my answer.
- After each answer, tell me if I'm right, correct any mistake, and explain briefly.
- Mix recall, application, and one "explain why" question per round.
- After 10 questions, summarize what I know well and what to review.Best for: Studying for an exam or interview — active recall beats re-reading, and Gemini adapts to your answers.
Business & marketing
Five prompts for founders and marketers. Use Search grounding for anything about competitors or markets so the output reflects reality.
26. Draft a One-Page Business Plan
Intent: Draft a tight one-page business plan.
Context: The business is [what it does] for [target customer], solving [problem]. Model: [how it makes money]. Stage: [idea / early / scaling].
Constraints:
- Cover: problem, solution, target customer, revenue model, go-to-market, key risks.
- Keep each section to 2-3 sentences.
- Add 3 assumptions I must validate before investing more.
- Be honest about the weakest part of this plan.Why it works: Forcing honesty about the weakest part surfaces the risk you're most likely to be avoiding.
27. Marketing Campaign Concepts
Intent: Generate campaign concepts I can actually run.
Context: Product: [product]. Audience: [who]. Goal: [awareness / signups / sales]. Budget vibe: [scrappy / mid / big]. Channels available: [list].
Constraints:
- Give me 5 distinct campaign concepts, each with a hook, the channel, and the core message.
- For each, note the one metric that would prove it worked.
- Rank them by likely ROI for my budget.
- Flag which are quick to test this week.Best for: Getting past the blank page with concepts tied to your real channels and budget.
28. Competitor Snapshot With Search
Intent: Build a current snapshot of my competitors.
Context: My competitors are [list]. My product is [product] for [audience].
Constraints:
- Verify with Google Search — use current positioning, pricing, and messaging.
- For each competitor: one-line positioning, pricing, key strengths, and visible gaps.
- Identify 3 gaps in the market I could own.
- Cite where you found pricing and positioning claims.Why it works: Grounding with Search keeps competitor pricing and messaging current, and citations let you verify before acting.
29. Landing Page Copy
Intent: Write conversion-focused landing page copy.
Context: Product: [product]. Audience: [who and their main pain]. Primary action: [what they should do]. Proof I have: [testimonials, numbers, logos].
Constraints:
- Write a hero headline, subhead, and 3 benefit-led sections (heading + 2 lines each).
- Add a clear CTA and one FAQ that handles the top objection.
- Lead with the customer's outcome, not our features.
- Give me 2 headline variants to test.Best for: Turning a rough offer into structured page copy you can drop into a builder.
30. Customer Persona From Data
Intent: Build grounded customer personas from real inputs.
Context: Here is my input — [paste survey responses, reviews, support tickets, or a Sheet of customer data]. My product is [product].
Constraints:
- Identify the 2-3 distinct personas actually present in this data.
- For each: goals, pains, objections, and the trigger that makes them buy.
- Quote 1-2 real phrases from the data per persona.
- Note where the sample is too thin to be confident.Why it works: Grounding personas in your actual customer data — and quoting it — beats invented archetypes.
Data & analysis
Five prompts for working with numbers. Paste a CSV or point Gemini at a connected Sheet; use High thinking for anything involving inference or forecasting.
31. Analyze a CSV or Sheet
Intent: Analyze a dataset and tell me what matters.
Context: I'm attaching a [CSV] / using my Sheet named "[name]". It contains [describe columns]. The question I care about is [question].
Constraints:
- Start with a quick data-quality check: row count, missing values, obvious anomalies.
- Answer my question with the specific numbers that support it.
- Show the 3 most important findings, ranked.
- Suggest one chart that would communicate the main finding.Why it works: Leading with a data-quality check catches missing or dirty data before it corrupts the conclusion.
32. Find the Story in a Dataset
Intent: Find the narrative hidden in my data.
Context: Here is the dataset: [paste CSV or reference Sheet]. Audience for the story: [exec / team / customers].
Constraints:
- Use High thinking.
- Surface the 3 most surprising or decision-relevant patterns.
- For each, state the finding, the evidence, and the "so what".
- Note any correlation you'd be wrong to read as causation.
- End with the single headline finding, in one sentence.Best for: Turning a raw export into an insight your audience can act on.
33. Clean and Structure Messy Data
Intent: Clean messy data into something usable.
Context: Here is the raw data:
[paste it]
I want it structured as [target format, e.g. a table with columns X, Y, Z].
Constraints:
- Normalize inconsistent formats (dates, casing, units, spelling).
- Flag rows that look duplicated or suspect instead of silently dropping them.
- Output the clean version as a table I can paste into Sheets.
- List every transformation you applied so I can audit it.Why it works: Requiring a log of transformations makes the cleanup auditable instead of a black box.
34. Build a KPI Dashboard Spec
Intent: Design a KPI dashboard before I build it.
Context: The business/team is [context]. The goal we're steering toward is [goal]. Data I have access to: [sources].
Constraints:
- Recommend 5-7 KPIs that actually map to the goal, not vanity metrics.
- For each: definition, formula, target, and how often to review it.
- Group them into leading vs. lagging indicators.
- Suggest the chart type for each and a sensible dashboard layout.Best for: Deciding what to measure — the spec is the hard part; the chart tool is easy.
35. Forecast From Historical Numbers
Intent: Make a defensible forecast from my history.
Context: Here is my historical data: [paste time series, e.g. monthly revenue]. I want to forecast [metric] for [period].
Constraints:
- Use High thinking.
- State the trend and any seasonality you detect.
- Give a base, optimistic, and conservative projection with the assumptions behind each.
- List what could break the forecast.
- Be explicit that this is an estimate, not a guarantee.Why it works: Three scenarios with stated assumptions is far more useful — and honest — than a single confident number.
Personal & everyday
Five prompts for life outside work. Attach photos, PDFs, or documents where useful — Gemini is multimodal and reads them directly.
36. Plan a Trip Itinerary
Intent: Plan a realistic trip itinerary.
Context: Destination: [place]. Dates: [dates]. Travelers: [who]. Budget: [range]. We're into [interests] and want the trip to feel [pace: relaxed / packed].
Constraints:
- Verify with Google Search for current opening hours, events, and closures.
- Give a day-by-day plan grouped by area to minimize travel time.
- Include 1-2 food suggestions per day and a rough daily budget.
- Add a rainy-day backup for each day.Best for: Trips where you want a plan grounded in current, real details rather than generic suggestions.
37. Weekly Meal Plan and Grocery List
Intent: Plan meals and the shopping to match.
Context: [Number] people, [dietary needs/preferences]. Budget: [range]. I have about [X] minutes to cook on weeknights. Things I'm sick of: [list].
Constraints:
- Give 5 dinners with a one-line description and prep time each.
- Reuse ingredients across meals to cut waste.
- Produce a single grocery list grouped by store section.
- Keep it within budget and note the rough total.Why it works: Reusing ingredients across meals and grouping the list by aisle turns a plan into an actually efficient shop.
38. Explain a Bill or Contract
Intent: Understand a document before I sign or pay.
Context: I'm attaching a [contract / bill / policy / lease]. I'm worried about [your concern, e.g. hidden fees, cancellation terms].
Constraints:
- Summarize what this document commits me to, in plain language.
- List every fee, deadline, and obligation as a bullet.
- Flag anything unusual, one-sided, or worth questioning.
- Give me 3 questions to ask before I agree.
- Note that this is general help, not legal advice.Best for: Catching the terms buried in fine print — attach the PDF and let Gemini read all of it.
39. Draft a Difficult Personal Message
Intent: Help me say something hard, well.
Context: I need to [message a friend / decline / apologize / set a boundary] with [who]. The situation: [context]. I want them to feel [respected / clear / cared for].
Constraints:
- Keep it honest, kind, and not passive-aggressive.
- Own my part where fair; don't over-apologize.
- Give me two versions: one softer, one more direct.
- Keep each under 120 words.Why it works: Naming how you want the other person to feel steers the tone better than just describing the situation.
40. Build a Habit Plan
Intent: Help me build a habit that actually sticks.
Context: The habit I want is [habit]. My motivation: [why]. My past failures: [what's gone wrong before]. My daily routine: [rough shape].
Constraints:
- Anchor the habit to something I already do (habit stacking).
- Start absurdly small and scale over 4 weeks — give me the weekly targets.
- Design one "if I slip" recovery rule so one miss doesn't end it.
- Suggest a simple way to track it.Best for: Making a change realistic — anchoring, tiny starts, and a recovery rule are what survive past week one.
Once these feel natural, save the ones you reuse as Gems so you can trigger them without retyping, and keep the Gemini prompt cheat sheet handy. For pre-built skeletons you fill in, see the Gemini prompt templates.
Frequently Asked Questions
Which Gemini model should I use for these prompts?
Gemini 3.1 Pro is the default for everything here — it has the 1M-token context window and the strongest reasoning. Use Gemini 3.1 Flash when you want fast, cheap answers on simple tasks. The prompt text is identical either way; you pick the model in the app or API.
What are thinking levels and when should I change them?
Gemini 3.1 Pro lets you set Low, Medium, or High thinking. Low is fast for simple lookups and rewrites, Medium is the balanced default, and High spends more time reasoning for coding, math, analysis, and multi-step planning. Several prompts here suggest a level, but you can override it in the app or API.
Can Gemini actually read my Gmail, Drive, and Docs?
Yes, if you connect Google Workspace in the Gemini app. Once connected it can read Gmail, Drive, Docs, Sheets, Slides, Calendar, and Meet transcripts when you reference them by name — for example "using my Drive doc named Q3 Plan" or "summarize my last 7 days of Gmail". It only accesses your own account's data.
How does Google Search grounding work?
When you ask Gemini to "verify with current data" or "use Google Search", it pulls live results from the web and cites sources instead of relying only on its training data. Use it for anything time-sensitive — prices, news, current tools, recent changes — where an outdated answer would be wrong.
When should I use Deep Research instead of a normal prompt?
Use a normal prompt for quick answers and single-source tasks. Switch to Deep Research (or Deep Research Max) when you need a multi-page, cited report that pulls from hundreds of sites and, if connected, your own Gmail and Drive. It takes minutes rather than seconds but returns a structured, sourced document.
Can I use these prompts and Gemini's output commercially?
The prompt text is free to use and adapt. Whether Gemini's output is cleared for commercial use depends on your Google plan and Gemini's current usage terms, so check the terms tied to your account before shipping paid or branded work, and always review and fact-check output first.
How do I adapt these prompts to my own situation?
Replace every [bracketed placeholder] with your real details, keep the Intent, Context, and Constraints structure intact, and attach or reference any file, Drive doc, or dataset the task needs. Add "verify with Google Search" for anything current, and raise the thinking level to High for hard reasoning.
What is a Gem and should I save these as Gems?
A Gem is a saved custom assistant with its own instructions and default tools. If you reuse a prompt often — a weekly report, a code reviewer, a brand-voice writer — paste it into a Gem so you can trigger it without retyping. The prompts here work as one-off messages or as the base for a Gem.