Get More from Gemini with Better Prompts

I need a comprehensive research brief on [topic]. Structure it as: 1) Current state of the field (what's established), 2) Active debates and unresolved questions, 3) Key players and institutions, 4) Recent developments from the last 6 months, 5) Practical implications for [my context]. Cite specific studies, papers, or data points where possible. Flag any claims where the evidence is weak or contested.

Analyze [topic/debate] from three distinct perspectives: [perspective 1], [perspective 2], and [perspective 3]. For each perspective, explain: the core argument, the strongest evidence supporting it, the weakest point in the reasoning, and what someone holding this view would recommend. End with a synthesis: where do these perspectives overlap, and where are the genuine disagreements that can't be resolved by more data?

I believe the following things about [topic]: 1. [Assumption 1] 2. [Assumption 2] 3. [Assumption 3] 4. [Assumption 4] 5. [Assumption 5] For each assumption, tell me: Is it accurate, partially accurate, or wrong? What's the current evidence? Where might my understanding be outdated or oversimplified? If an assumption is common but misleading, explain why it persists.

I'm going to share a [document type — contract, research paper, report, transcript]. Please provide: 1) A 3-sentence executive summary, 2) The 5 most important points in bullet form, 3) Any red flags, inconsistencies, or notable omissions, 4) Three questions I should ask after reading this, 5) A one-paragraph "what this means for me" analysis given that I am [your role/context]. [Paste document]

Analyze this data and identify the three most significant trends: [Paste data — CSV, table, or description] For each trend: describe what's happening, hypothesize why it's happening, project where it's heading if the pattern continues, and identify what would cause the trend to reverse. Present your analysis in a format suitable for a [meeting/report/presentation].

I need you to write [type of content] in a voice that is [adjective 1], [adjective 2], and [adjective 3]. The audience is [describe reader]. The goal is to [desired outcome]. Here's an example of the voice I'm going for: [Paste a sample paragraph in the desired voice] Now write [content description] matching this voice exactly. Maintain the same sentence length patterns, vocabulary level, and tone throughout.

Here is [original content type — a blog post, a report, a transcript, meeting notes]: [Paste content] Transform this into [target format]: a Twitter/X thread (8-12 tweets), a LinkedIn post (hook + value + CTA), an email newsletter section (150 words), and a presentation outline (5-7 slides with speaker notes). Each format should emphasize the angle most relevant to that platform's audience.

Edit the following text for clarity, impact, and concision. Rules: 1) Cut any sentence that doesn't earn its place, 2) Replace jargon with plain language unless the jargon is necessary for the audience, 3) Strengthen weak verbs (replace "is," "was," "has" with action verbs where possible), 4) Break up any sentence over 25 words, 5) Preserve my voice — tighten, don't rewrite. Show me the edited version, then list every change you made and why. [Paste text]

Create a detailed content brief for an article targeting the keyword "[keyword]." Include: 1) Recommended title (under 60 characters), 2) Meta description (under 155 characters), 3) Suggested H2 and H3 structure, 4) Key questions the article must answer (based on what people searching this keyword actually want), 5) Related keywords to include naturally, 6) Recommended word count, 7) Content angle that differentiates this from what already ranks.

I just had a meeting about [topic] with [attendees/roles]. Here are my rough notes: [Paste messy notes] Draft a professional follow-up email that includes: 1) Summary of key decisions made, 2) Action items with owners and deadlines, 3) Open questions that need resolution, 4) Next steps and next meeting date if applicable. Tone: [professional/casual/executive-brief]. Keep it under [word count] words.

Here is my code that isn't working as expected: ```[language] [Paste code] ``` Expected behavior: [what it should do] Actual behavior: [what it does instead] Error message (if any): [paste error] Please: 1) Identify the bug and explain why it happens, 2) Show the corrected code, 3) Explain the fix so I understand the underlying concept, 4) Suggest any other issues or improvements you notice (but keep the focus on the bug first).

Review this code for: 1) Bugs or potential runtime errors, 2) Security vulnerabilities (injection, auth issues, data exposure), 3) Performance concerns, 4) Readability and maintainability, 5) Adherence to [language/framework] best practices. Prioritize issues by severity (critical > important > nice-to-have). For each issue, explain the problem, show the fix, and explain why it matters. ```[language] [Paste code] ```

I'm new to this codebase. Here are the key files: [Paste file contents or describe the structure] Explain: 1) What this code does at a high level, 2) The architecture and design patterns used, 3) How data flows through the system, 4) The entry points (where does execution start?), 5) The key dependencies and why they're used. Explain it as if I'm a [junior/mid/senior] developer joining the team.

Write comprehensive test cases for this function/component: ```[language] [Paste code] ``` Include: 1) Happy path tests (normal usage), 2) Edge cases (empty inputs, boundary values, type mismatches), 3) Error cases (what should fail and how), 4) Integration considerations (how this interacts with other components). Use [testing framework] syntax. Explain the reasoning behind each test case.

Here is a database query that's running slowly: ```sql [Paste query] ``` Table structure: [describe or paste schema] Approximate data volume: [number of rows] Current execution time: [time] Please: 1) Explain why this query is slow, 2) Suggest an optimized version, 3) Recommend any indexes that would help, 4) Explain the tradeoffs of your optimization (does it sacrifice readability? does the index slow writes?). Show the EXPLAIN plan difference if possible.