Expert prompts for Google Gemini Advanced — research and document analysis, multimodal tasks, coding, creative writing, and strategic decision-making with the 1M token context window.
Long-document research synthesis
I'm sharing [document/research paper/report]. Please: 1. Summarise the core argument or findings in 3–5 sentences 2. Extract the top 5 most important insights with supporting evidence 3. Identify methodological limitations or gaps in the analysis 4. Flag any claims that require external verification 5. Suggest 3 follow-up questions this document raises
Targeted extraction from long documents
Using the document I've attached, answer the following questions with direct quotes and page/section references where possible: [Question 1] [Question 2] [Question 3] If any question cannot be answered from the document, say so explicitly rather than inferring.
Multi-document competitive landscape
I'm sharing [3–5 competitor reports/articles/websites]. Analyse them together and produce: - A comparison table of positioning, pricing, and key features - Where each competitor is strongest and weakest - White space opportunities none of them are addressing - The messaging angles that appear most frequently across all of them
Structured data extraction from unstructured text
Extract the following data fields from the document I've shared and output as a structured table: Fields: [Field 1], [Field 2], [Field 3], [Field 4] Where a field is missing or ambiguous, mark it as "N/A" and note why. After the table, summarise any patterns or anomalies you notice in the data.
Emotionally resonant brand narrative
Write a brand origin story for [company name] that: - Opens with the specific problem the founder experienced (not "we noticed a gap in the market") - Shows the moment of insight that led to the solution - Explains why this team is uniquely qualified to solve it - Ends with a forward-looking statement about the impact they're building toward Tone: [warm/bold/authoritative]. Length: 250–300 words.
Multi-angle content brief for one topic
Generate 5 distinct content angles for the topic "[topic]" — each targeting a different audience segment or emotional need: 1. [Angle name]: Hook + 3 key talking points + best format 2. (repeat for all 5) For each angle, specify: target audience, primary emotion/motivation, and whether it's better as short-form, long-form, or video.
High-converting landing page copy
Write landing page copy for [product/service] targeting [audience]. Structure: - Headline (problem-aware, benefit-led) - Subheadline (one sentence expanding on the headline) - 3 feature/benefit pairs (feature → what it means for the user) - Social proof section (placeholder for real testimonials with suggested format) - FAQ (3 objections + answers) - CTA section (two variations: high-intent and low-intent) Match the tone to: [conversational/professional/urgent]
5-email nurture sequence
Create a 5-email nurture sequence for [product/service] for leads who signed up for [lead magnet]. For each email include: subject line, preview text, opening hook, main body (150–200 words), CTA, and send timing. Email 1: Deliver value from lead magnet + set expectations Email 2: Address the #1 objection Email 3: Social proof / case study Email 4: Product education — one key feature Email 5: Direct offer with urgency
Senior engineer code review
Review the code I've shared as a senior software engineer would. Assess: 1. Correctness — will this work as intended? Are there edge cases it misses? 2. Performance — any inefficiencies, N+1 queries, or unnecessary computations? 3. Security — injection risks, improper validation, or exposed credentials? 4. Readability — naming conventions, comment quality, structure 5. Testability — can this be unit tested cleanly? Prioritise issues as Critical, Moderate, or Minor. Suggest specific fixes for Critical and Moderate items.
System design for scalability
Design a system architecture for [use case — e.g. "a real-time notification system handling 1M daily active users"]. Include: - Core components and their responsibilities - Data flow diagram (described in text) - Database design choices and trade-offs - Scaling strategy (horizontal vs vertical) - Failure modes and mitigation - Technology stack recommendations with justification
Root cause analysis from error logs
I'm seeing this error: [paste error message and stack trace] Relevant code context: [paste code] Environment: [language/framework/version] Please: 1. Identify the most likely root cause 2. Explain why this error occurs at a conceptual level 3. Provide a specific fix with code 4. Suggest a test case that would catch this in future 5. Note if there are related issues I should check
Technical documentation from code
Generate comprehensive developer documentation for the code I've shared. Include: - Overview: what this module/function does in plain English - Parameters: name, type, description, whether required - Return value: type and description - Example usage (2–3 examples covering common cases) - Error handling: what errors can be thrown and when - Dependencies: external libraries or internal modules required Format as Markdown suitable for a README or wiki.
SWOT to strategic initiatives
Conduct a SWOT analysis for [company/product] in [market context]. Then — this is the important part — synthesise the SWOT into: - 3 SO strategies (leverage strengths to capture opportunities) - 2 ST strategies (use strengths to counter threats) - 2 WO strategies (address weaknesses using opportunities) - 1 WT defensive move (minimise weaknesses, avoid threats) For each strategy, specify a concrete initiative, timeline, and the metric that would indicate success.
Structured decision analysis
I need to decide between [Option A] and [Option B] for [context/goal]. Analyse this decision using: 1. Criteria matrix: score each option on [Cost, Risk, Time-to-value, Strategic fit, Reversibility] out of 10 2. Second-order effects: what are the non-obvious consequences of each option 6–12 months out? 3. What assumptions does each option depend on being true? 4. What would have to happen for the lower-scoring option to actually be the better choice? 5. Your recommendation and the one piece of evidence that would change your mind
Market sizing and opportunity analysis
Help me size the market for [product/service] using both approaches: Top-down: Start from [total addressable market] → narrow by [geography/segment/adoption rate] Bottom-up: Start from [ICP characteristics] × [# of qualifying companies/people] × [price point] Then assess: - Market growth rate and key tailwinds - Realistic market share capture in year 1, year 3, year 5 - The 2–3 factors that most influence whether this market is as large as it appears
Pre-mortem risk analysis
Run a pre-mortem on [initiative/project/decision]. Assume it's 18 months from now and this has failed badly. Working backwards: 1. The 5 most likely failure modes (ranked by probability) 2. For each failure mode: the early warning signs we should have caught 3. Mitigation we can put in place now to reduce likelihood 4. Mitigation we can put in place now to reduce impact if it does fail 5. The one risk that is most underestimated by the team
Insights narrative from raw data
I'm sharing [dataset/dashboard screenshot/chart]. Analyse it and produce: 1. The single most important finding in one sentence 2. Top 5 insights in priority order, each with supporting numbers 3. Anomalies or outliers that warrant investigation 4. What this data does NOT tell us (important gaps) 5. The 2–3 decisions this data should inform, and what additional data would make those decisions clearer
Chart and diagram interpretation
Analyse the chart/diagram I've shared. Provide: - What type of chart this is and what it's measuring - The key trend or pattern (with specific numbers from the chart) - Whether the visualisation is presenting data fairly or could be misleading - What the most important takeaway is for someone making a business decision - One thing the chart creator should have included but didn't
Trend analysis and projection
Based on the historical data I've shared (or described below), build a forecast for the next [6/12] months. Include: - Base case, optimistic case, and pessimistic case projections - The key assumptions driving each scenario - Seasonal patterns or cyclicality to account for - Leading indicators I should watch that would signal which scenario is unfolding - Confidence level in the forecast and the main source of uncertainty Historical data: [paste data or describe it]
Customer segmentation analysis
Analyse the customer data I've shared and identify distinct segments. For each segment, describe: - Defining characteristics (demographics, behaviour, purchase patterns) - Size and revenue contribution - Core need or job-to-be-done - Churn risk and growth potential - Recommended messaging and product strategy Then: which segment should we prioritise and why?