50 Best Gemini Prompts in 2026: Templates for Google's AI

Write a 1,500-word blog post about [TOPIC].

Ground your claims in current information. For any statistic or trend 
you mention, verify it's accurate and recent (2025-2026). If you can't 
verify a specific number, say "approximately" and cite what you can confirm.

Audience: [TARGET READER]
Tone: [DESCRIBE — e.g., authoritative but conversational]
Structure: 
- Hook opening (not a question, not "In today's world")
- 4-5 sections with ## headers
- Concrete examples in every section
- Practical takeaway at the end

Avoid: filler phrases, unsupported claims, generic advice that 
could apply to any topic.

Create an SEO content brief for the keyword "[TARGET KEYWORD]".

Research the current search landscape for this term and include:

1. **Search Intent**: What is the searcher actually trying to accomplish?
2. **Top Ranking Content**: What do the current top results cover? 
   What angle do they take?
3. **Content Gaps**: What do existing articles miss that we could cover?
4. **Recommended Structure**: H1, H2s, H3s with suggested word count per section
5. **Related Keywords**: 10-15 semantic keywords to weave in naturally
6. **Recommended Length**: Based on what's ranking, how long should this be?
7. **Link Opportunities**: What internal and external links make sense?
8. **Featured Snippet Opportunity**: Is there a snippet to target? 
   If so, what format (paragraph, list, table)?

Be specific. "Write good content" isn't a brief.

Write a [NUMBER]-email marketing campaign for [PRODUCT/SERVICE].

Campaign goal: [WHAT YOU WANT RECIPIENTS TO DO]
Audience: [WHO THEY ARE]
Sending schedule: [CADENCE — e.g., 3 emails over 7 days]

For each email:
- Subject line (under 50 characters — check that it doesn't trigger spam filters)
- Preview text (under 90 characters)
- Body (120-180 words)
- CTA button text (under 5 words)
- Optimal send time recommendation based on the audience type

Overall sequence logic: explain why each email is positioned where it 
is and how they build on each other. The sequence should work even if 
the reader skips some emails.

Write a detailed comparison between [PRODUCT A] and [PRODUCT B] for 
someone deciding which to buy/use.

Look up current pricing, features, and recent updates for both products. 
I want accurate, current information — not training data from months ago.

Structure:
1. Quick verdict (1-2 sentences for people who want the answer now)
2. Overview comparison table (features, pricing, platform support)
3. Where [Product A] wins (3-4 specific scenarios)
4. Where [Product B] wins (3-4 specific scenarios)
5. Head-to-head on: [CRITERION 1], [CRITERION 2], [CRITERION 3]
6. Who should pick which (clear recommendation by user type)

Be honest about weaknesses. This should help someone make a real 
decision, not read like a press release for either product.

Create a 2-week social media content calendar for [BRAND/BUSINESS] 
on [PLATFORM(S)].

Brand: [WHAT THE BRAND IS AND DOES]
Audience: [WHO FOLLOWS THEM]
Current trends: Look up what's trending or relevant on [PLATFORM] 
in [INDUSTRY] right now.
Content pillars: [LIST 3-4 THEMES — e.g., education, behind-the-scenes, 
customer stories, industry commentary]

For each post:
- Date and time (recommend optimal posting times for the platform)
- Content type (text, image, video, carousel, poll)
- Copy (full post text, platform-appropriate length)
- Visual direction (what the image/video should show)
- Hashtags (5-10, mix of broad and niche)
- Engagement prompt (question or CTA to drive comments)

Include 2-3 "reactive slots" for trending topics or timely content.

Write a press release for [ANNOUNCEMENT].

Details:
- Company: [NAME AND BRIEF DESCRIPTION]
- What's being announced: [THE NEWS]
- Why it matters: [SIGNIFICANCE]
- Key quote from: [PERSON, TITLE] (draft a quote that sounds human, 
  not corporate)
- Availability: [WHEN/WHERE/HOW]
- Supporting data: [ANY NUMBERS OR CONTEXT]

Format: Standard press release structure (dateline, headline, subhead, 
body paragraphs, boilerplate, media contact). Under 500 words total.

The headline should be newsworthy, not promotional. Write it as if a 
journalist needs to decide in 3 seconds whether to read further.

Write landing page copy for [PRODUCT/SERVICE/FEATURE].

Product: [WHAT IT IS AND WHAT IT DOES]
Target customer: [WHO]
Primary action: [SIGN UP / BUY / BOOK A DEMO / DOWNLOAD]
Biggest objection: [WHAT MAKES PEOPLE HESITATE]

Sections needed:
1. Hero: Headline (under 10 words) + subhead (under 25 words) + CTA button text
2. Problem: The pain the reader is experiencing (2-3 sentences, specific)
3. Solution: How the product solves it (features as benefits, 3-4 items)
4. Social proof: Framework for testimonial placement + draft testimonial template
5. How it works: 3-step process (simple enough for a 5-second scan)
6. Objection handling: Address the #1 hesitation directly
7. Final CTA: Different angle from the hero CTA, with urgency element

Don't write "we're passionate about [thing]." Nobody cares about 
your passion. They care about their problem being solved.

Translate the following text from [SOURCE LANGUAGE] to [TARGET LANGUAGE].

Don't do a literal translation. Adapt it culturally:
- Idioms should be replaced with equivalent idioms in the target language
- References that won't land with the target audience should be swapped 
  for culturally relevant equivalents
- Humor should work in the target culture (or be replaced if it won't)
- Formal/informal register should be appropriate for [CONTEXT — e.g., 
  "business email in Japan" or "casual marketing in Brazil"]

Text to translate:
[PASTE TEXT]

After the translation, provide a brief note on any significant 
adaptation choices you made and why.

Write a research report on [TOPIC].

Use current information — search for the latest data, studies, and 
expert opinions on this subject. I need information from 2025-2026, 
not older training data.

Structure:
1. Executive Summary (200 words)
2. Current State: What's happening right now?
3. Key Players: Who matters in this space and why?
4. Data & Trends: Specific numbers, growth rates, market data
5. Expert Perspectives: What are the leading viewpoints? Where do they disagree?
6. Implications: What does this mean for [MY CONTEXT — e.g., a startup 
   in this space / an investor / a consumer]?
7. Outlook: What's likely to happen in the next 12-24 months?

For each claim backed by a specific source, note where the information 
came from. Flag anything you're uncertain about.

Conduct a literature review on [ACADEMIC TOPIC].

Search for recent peer-reviewed research, meta-analyses, and key 
publications. Focus on work from [TIME RANGE — e.g., 2020-2026].

Organize the review by:
1. **Research question**: What is the field trying to answer?
2. **Major theories/frameworks**: The dominant lenses researchers use
3. **Key findings**: What do we know? (organized thematically, not 
   chronologically)
4. **Methodological approaches**: How are researchers studying this? 
   What methods dominate?
5. **Debates and contradictions**: Where does the evidence conflict?
6. **Gaps**: What hasn't been studied? What needs more work?
7. **Annotated bibliography**: 10-15 key papers with one-sentence 
   summaries of their contribution

Academic tone. Cite specific papers by author and year where possible.

Fact-check the following claims. For each claim, determine whether it's 
True, Mostly True, Misleading, Mostly False, or False.

Claims:
1. [CLAIM 1]
2. [CLAIM 2]
3. [CLAIM 3]
4. [CLAIM 4]
5. [CLAIM 5]

For each claim:
- Verdict: [Rating]
- Evidence: What does current data show? (cite specific sources)
- Context: Is the claim technically true but misleading? What nuance 
  is missing?
- Original source: Where did this claim likely originate?

Use current, verifiable information. If you can't verify something 
definitively, say so rather than guessing.

Research the market for [PRODUCT/SERVICE CATEGORY].

I need current market data — search for the latest reports, industry 
analyses, and market trends.

Deliverables:
1. **Market Size**: Current value and projected growth (with sources)
2. **Key Segments**: How the market breaks down by [geography / 
   customer type / price tier / use case]
3. **Top Competitors**: 5-10 major players with estimated market share
4. **Growth Drivers**: What's fueling market growth?
5. **Barriers to Entry**: What makes this market hard to enter?
6. **Customer Behavior**: How are buyers making decisions in this space?
7. **Emerging Trends**: What's changing in the last 6-12 months?
8. **Opportunities**: Where are the underserved segments?

Be specific with numbers. "The market is growing" isn't useful. 
"The market grew 23% YoY to $4.2B in 2025" is.

Evaluate [TECHNOLOGY/TOOL/FRAMEWORK] for use in [MY CONTEXT].

Research the current state of this technology — latest version, recent 
updates, community adoption, known issues.

Assessment:
1. **What it does**: Plain-language explanation
2. **Current version and status**: Latest release, stability, maintenance activity
3. **Adoption**: Who's using it? How large is the community?
4. **Strengths**: What it does well (with evidence)
5. **Weaknesses**: Where it falls short (check recent GitHub issues, 
   forum complaints, Stack Overflow pain points)
6. **Alternatives**: 3-5 competing options with quick comparison
7. **Fit for my use case**: Given [MY REQUIREMENTS], is this the right choice?
8. **Risks**: What could go wrong (abandonment, breaking changes, 
   vendor lock-in)?
9. **Recommendation**: Use it / Skip it / Watch it — with clear reasoning

Don't just list features from the docs. I can read the docs myself. 
Tell me what the docs don't say.

Give me a comprehensive briefing on [TOPIC/EVENT].

Search for the latest developments. I want to understand:

1. **What happened**: The facts, as reported by multiple sources
2. **Timeline**: Key events in chronological order
3. **Who's involved**: Major players and their positions
4. **Why it matters**: Impact on [SPECIFIC CONTEXT — e.g., the tech 
   industry / my investment portfolio / US policy]
5. **Different perspectives**: How is this being interpreted by 
   different sides? (present at least 2 viewpoints)
6. **What's next**: Expected developments in the coming days/weeks
7. **Sources**: Where you found this information

If sources disagree on facts (not just interpretation), flag the 
discrepancy. I'd rather know there's uncertainty than get a false 
sense of clarity.

Help me research prior art and existing patents related to [INVENTION/IDEA].

Search for:
1. Existing patents with similar concepts or mechanisms
2. Published academic research describing similar approaches
3. Commercial products that implement related functionality
4. Open-source projects tackling the same problem

For each finding:
- Title and source (patent number, paper title, product name)
- Date published/filed
- How it relates to my concept
- Key differences from my approach
- Relevance level: High / Medium / Low

My concept: [DESCRIBE YOUR INVENTION OR IDEA IN DETAIL]

I understand this isn't a formal patent search. I'm using this for 
initial research before engaging a patent attorney.

I need to understand the current state of [INDUSTRY].

Search for recent industry reports, analysis, and news. Compile a 
briefing that covers:

1. **Industry overview**: What defines this industry in 2026?
2. **Market dynamics**: Supply, demand, pricing trends
3. **Regulatory landscape**: Current and upcoming regulations
4. **Technology impact**: How is tech changing this industry?
5. **Key metrics**: The numbers that matter (with current values)
6. **Challenges**: Top 3 challenges facing the industry
7. **Outlook**: Consensus view on where things are heading
8. **Contrarian view**: What's a credible counterargument to the 
   consensus?

Write it as a briefing for someone entering this industry, not 
someone already in it. Define jargon on first use.

Build a complete [FEATURE] for a [TECH STACK] application.

Feature: [DESCRIBE WHAT IT SHOULD DO]
Tech stack: [e.g., Next.js 15, TypeScript, Prisma, PostgreSQL, Tailwind CSS]
Authentication: [e.g., NextAuth.js / Clerk / Supabase Auth]

Provide:
1. Database schema changes (migration file)
2. API route(s) with full implementation
3. Frontend component(s) with TypeScript types
4. Form validation (client and server)
5. Error handling (user-facing error messages + error boundaries)
6. Loading states
7. Tests for the critical path

Requirements:
- TypeScript strict mode, no `any` types
- Server-side validation (never trust the client)
- Optimistic UI updates where appropriate
- Mobile-responsive
- Accessible (keyboard navigation, screen reader support)

Don't stub anything out. Every function should be fully implemented.

Review this code. I'll tell you what it does and what concerns me.

What this code does: [EXPLAIN THE FEATURE/SYSTEM]
What concerns me: [SPECIFIC WORRIES — e.g., "I think there's a race 
condition" or "This feels over-engineered"]

Check for:
1. The specific concern I mentioned
2. Security issues (injection, auth bypass, data exposure)
3. Performance problems at scale (this handles [EXPECTED LOAD])
4. Error handling gaps
5. Edge cases the original author likely didn't consider
6. Whether the abstractions are at the right level

For each issue: describe it, explain the impact, provide the fix.
Rank issues by severity. End with an overall verdict.

Build a regex pattern for [WHAT YOU NEED TO MATCH].

Input examples (should match):
- [EXAMPLE 1]
- [EXAMPLE 2]
- [EXAMPLE 3]

Counter-examples (should NOT match):
- [EXAMPLE 4]
- [EXAMPLE 5]

Language/engine: [JavaScript / Python / Go / PCRE / etc.]

Provide:
1. The regex pattern
2. Breakdown explaining each part
3. Test results against all my examples
4. Edge cases you thought of that I should test
5. A simpler alternative if the regex is complex (sometimes a 
   combination of string methods is clearer)

Design a database schema for [APPLICATION/FEATURE].

Requirements:
[LIST WHAT THE SYSTEM NEEDS TO STORE AND THE RELATIONSHIPS]

Constraints:
- Database: [PostgreSQL / MySQL / MongoDB / etc.]
- Expected scale: [ROUGH NUMBERS — users, records, queries per second]
- Read/write ratio: [e.g., "read-heavy, 90/10"]

Deliverables:
1. Entity-relationship description
2. Complete schema (CREATE TABLE statements or equivalent)
3. Indexes (explain why each one)
4. Constraints (foreign keys, unique, check)
5. Common queries this schema is optimized for (with example SQL)
6. Queries that will be slow on this schema (and what to do about them)
7. Migration strategy if evolving from an existing schema
8. Data integrity considerations

Create the configuration for [WHAT YOU NEED — e.g., a GitHub Actions 
CI/CD pipeline / Docker Compose setup / Terraform infrastructure / 
Kubernetes deployment].

Application: [WHAT THE APP IS]
Environment: [DEV / STAGING / PRODUCTION]
Requirements:
- [REQUIREMENT 1 — e.g., "Run tests on every PR"]
- [REQUIREMENT 2 — e.g., "Deploy to AWS ECS on merge to main"]
- [REQUIREMENT 3 — e.g., "Send Slack notification on failure"]

Provide:
1. Complete configuration file(s) — not snippets, full files
2. Comments explaining non-obvious choices
3. Security considerations (what secrets are needed, how to store them)
4. Cost implications if applicable
5. Monitoring/alerting recommendations
6. Common failure modes and how to debug them

Generate a typed API client for this API.

API documentation or OpenAPI spec:
[PASTE SPEC OR DESCRIBE THE ENDPOINTS]

Language: [TypeScript / Python / Go / etc.]
HTTP client: [fetch / axios / httpx / etc.]

Requirements:
- Full type definitions for all request and response shapes
- Error handling with typed error responses
- Retry logic for transient failures (429, 503)
- Request/response logging (configurable, disabled by default)
- Authentication handling ([API KEY / OAUTH / BEARER TOKEN])
- Pagination helpers for list endpoints
- Rate limiting awareness

Provide the complete client as a single file (or module with clear 
file structure if it's complex). Include usage examples.

Optimize this code for performance.

Context:
- What this code does: [EXPLAIN]
- Current performance: [e.g., "Processes 1000 records in 4.2 seconds"]
- Target performance: [e.g., "Need it under 500ms"]
- Constraints: [MEMORY / CPU / NETWORK LIMITS]
- Environment: [WHERE THIS RUNS]

Instructions:
1. Profile: Identify the bottleneck(s) — what's actually slow?
2. Quick wins: Changes that improve performance with minimal code change
3. Structural changes: Algorithmic or architectural improvements
4. Optimized version: The rewritten code
5. Benchmarking approach: How to measure the improvement
6. Trade-offs: What does the optimized version sacrifice (readability, 
   memory, complexity)?

Help me migrate this code from [OLD STACK] to [NEW STACK].

Current code:

Migration details:
- From: [e.g., React class components / Express.js / Python 2]
- To: [e.g., React hooks / Fastify / Python 3.12]
- Must preserve: [BEHAVIOR THAT CAN'T CHANGE]
- Can change: [BEHAVIOR THAT CAN BE UPDATED]

Provide:
1. Migrated code (complete, not fragments)
2. Change log: what changed and why
3. Breaking changes: anything that behaves differently
4. Deprecated patterns replaced
5. New patterns/APIs used (with brief explanation if unfamiliar)
6. Testing checklist: what to verify after migration

Research [COMPETITOR COMPANY] and give me a competitive intelligence 
briefing.

Look up their latest:
- Product updates and announcements
- Pricing changes
- Leadership changes
- Funding or financial news
- Customer reviews and sentiment
- Job postings (these reveal strategic direction)
- Marketing messaging and positioning

My company: [YOUR COMPANY AND WHAT YOU DO]
We compete on: [WHERE YOU OVERLAP]

Organize the briefing as:
1. Recent developments (last 3-6 months)
2. Strategic direction (what their moves suggest)
3. Strengths we should respect
4. Weaknesses we can exploit
5. Actions we should consider in response

Write the [SECTION] of a grant proposal.

Project: [WHAT THE PROJECT IS]
Funding body: [WHO YOU'RE APPLYING TO]
Grant program: [SPECIFIC PROGRAM NAME]
Amount requested: [DOLLAR AMOUNT]

Section to write: [e.g., "Project Narrative" or "Methodology" or "Budget Justification"]

Requirements:
- Follow the funder's guidelines for this section (look up the 
  specific requirements for [GRANT PROGRAM] if possible)
- Length: [WORD/PAGE LIMIT]
- Tone: [ACADEMIC / PROFESSIONAL / COMMUNITY-FOCUSED]
- Include: [SPECIFIC REQUIREMENTS — e.g., "must address DEI impact" 
  or "must include measurable outcomes"]

Key information:
[PASTE YOUR NOTES, DATA, OR EXISTING DRAFT]

Create a Business Model Canvas for [BUSINESS IDEA].

Description: [WHAT THE BUSINESS DOES]
Target market: [WHO]
Stage: [IDEA / EARLY / GROWTH]

Fill in all 9 blocks with substance, not buzzwords:
1. Customer Segments (be specific — not "everyone who needs X")
2. Value Propositions (the actual promise, from the customer's perspective)
3. Channels (how you reach and deliver to customers)
4. Customer Relationships (how you acquire, retain, and grow accounts)
5. Revenue Streams (how money flows in — pricing model, unit economics)
6. Key Resources (what you need that's hard to replicate)
7. Key Activities (what you have to be great at)
8. Key Partnerships (who you can't do this without)
9. Cost Structure (where the money goes — fixed vs variable)

After the canvas, add:
- **Riskiest assumption**: What's the one thing that, if wrong, kills the model?
- **First experiment**: How to test that assumption with minimum spend

Create a sales battlecard for competing against [COMPETITOR] when 
selling [YOUR PRODUCT].

Research current information about [COMPETITOR]:
- Their latest features and pricing
- Common claims their sales team makes
- Known weaknesses and customer complaints

Battlecard sections:
1. **Quick Comparison**: Feature/pricing table (current, accurate)
2. **Their Pitch**: What their sales team likely says about us
3. **Our Response**: Rebuttal for each claim (factual, not dismissive)
4. **Landmines**: Questions to ask the prospect that expose competitor 
   weaknesses (without mentioning the competitor by name)
5. **Win Themes**: The 3 messages that win deals against this competitor
6. **Trap Themes**: The 3 messages that lose deals (avoid these)
7. **Proof Points**: Customer stories or data that support our position
8. **When We Lose**: Honest assessment of when the competitor is the 
   better choice (so reps stop wasting time on unwinnable deals)

Help me build the assumptions for a financial model for [BUSINESS].

Business: [DESCRIPTION]
Revenue model: [HOW YOU CHARGE]
Stage: [PRE-REVENUE / EARLY REVENUE / SCALING]
Timeframe: [e.g., 3-year projection]

Research current benchmarks for:
- Customer acquisition cost in [INDUSTRY]
- Conversion rates for [CHANNEL/MODEL]
- Average revenue per user for [SIMILAR BUSINESSES]
- Churn rates for [BUSINESS TYPE]
- Operating cost benchmarks

For each assumption, provide:
- Conservative estimate
- Base case estimate
- Optimistic estimate
- Source or reasoning behind the range
- Which assumptions have the biggest impact on the model 
  (sensitivity ranking)

Help me build a customer persona based on data, not imagination.

What we know:
[PASTE ANY DATA — analytics demographics, survey results, sales notes, 
support tickets, review text, CRM data]

Research:
Look up behavioral data for [TARGET DEMOGRAPHIC] in [INDUSTRY]. What do 
published studies say about how this audience makes purchasing decisions?

Build a persona that includes:
1. Demographics (grounded in the data provided)
2. Psychographics (values, priorities, fears — inferred from behavior data)
3. Buying journey (how they discover, evaluate, and decide)
4. Information sources they trust
5. Objections they'll raise (mapped to the data — e.g., support ticket themes)
6. Language they use (actual phrases from reviews/tickets/surveys)
7. What success looks like for them

Separate what the data shows from what you're inferring. I need 
to know which is which.

Help me respond to this RFP (Request for Proposal).

RFP Requirements:
[PASTE THE RFP OR KEY SECTIONS]

Our company:
- Name: [COMPANY]
- What we do: [DESCRIPTION]
- Relevant experience: [PAST PROJECTS OR CLIENTS]
- Team: [KEY TEAM MEMBERS AND THEIR QUALIFICATIONS]
- Differentiator: [WHAT MAKES US DIFFERENT]

For each RFP requirement, draft a response that:
1. Directly addresses what they asked (don't dodge tough requirements)
2. Demonstrates relevant experience with specific examples
3. Shows understanding of their actual problem, not just the stated requirements
4. Highlights our differentiators naturally (not as a sales pitch)

If we can't fully meet a requirement, be honest and propose an 
alternative approach. Evaluators notice evasion.

Help me structure a quarterly business review (QBR) presentation.

Data:
- Revenue: [THIS QUARTER VS LAST QUARTER VS PLAN]
- Key metrics: [LIST WITH VALUES]
- Notable wins: [WHAT WENT WELL]
- Notable misses: [WHAT DIDN'T GO WELL]
- Team changes: [IF ANY]
- Customer feedback themes: [TOP 3]

Build a QBR that covers:
1. Scorecard: metrics vs targets (table, green/yellow/red)
2. Performance narrative: what the numbers mean (not just what they are)
3. Win analysis: why good things happened (so we can repeat them)
4. Loss analysis: why misses happened (root cause, not blame)
5. Customer health: retention, expansion, at-risk accounts
6. Next quarter priorities: top 3, tied to the data
7. Resource asks: what we need (specific, justified by the data)

The audience is [WHO — executives / board / team]. Calibrate detail level accordingly.

Help me prepare for a negotiation.

Situation: [WHAT'S BEING NEGOTIATED — contract, salary, partnership, deal]
My position: [WHAT I WANT]
Their likely position: [WHAT THEY PROBABLY WANT]
My BATNA (best alternative): [WHAT I DO IF THIS FAILS]
Their likely BATNA: [WHAT THEY DO IF THIS FAILS]

Research any relevant market data:
[e.g., "salary ranges for [ROLE] in [CITY]" or "typical SaaS contract 
terms for [DEAL SIZE]"]

Prepare:
1. **My opening position**: Where to start (and why)
2. **Walk-away point**: My minimum acceptable outcome
3. **Their likely opening**: What to expect from them
4. **Concession strategy**: What I can give up (ranked by cost to me vs value to them)
5. **Anchoring points**: Data and comparables to cite
6. **Tough questions they'll ask**: And how to answer them
7. **Creative options**: Non-obvious trade-offs that create value for both sides
8. **Red flags**: Signs they're negotiating in bad faith

Create an onboarding plan for a new [ROLE] at [COMPANY TYPE].

Role details:
- Title: [TITLE]
- Department: [DEPARTMENT]
- Reports to: [WHO]
- Key responsibilities: [TOP 3-5]
- Tools they'll use: [LIST]

Create a 30-60-90 day plan:

**Days 1-30 (Learn):**
- Week-by-week schedule with specific activities
- Key people to meet (role, why, conversation topics)
- Documents/systems to review
- Quick win: one small, completable task that delivers visible value

**Days 31-60 (Contribute):**
- Increasing responsibility with specific milestones
- First solo project or deliverable
- Feedback checkpoint format

**Days 61-90 (Own):**
- Full ownership of [SPECIFIC AREA]
- Success metrics: how we evaluate their ramp
- 90-day review conversation guide

Include common onboarding failure modes and how this plan prevents them.

[UPLOAD IMAGE]

Analyze this [TYPE — photograph / design / UI screenshot / artwork] and 
provide detailed constructive feedback.

Assess:
1. Composition and visual hierarchy
2. Color usage and palette coherence
3. Typography (if applicable)
4. Technical quality (exposure, focus, resolution)
5. Emotional impact and mood
6. Target audience fit: [WHO THIS IS FOR]

Then provide:
- 3 specific things that work well (and why)
- 3 specific improvements with concrete suggestions
- An overall rating: [PURPOSE-FIT SCORE 1-10] with justification

Be specific. "The colors are nice" isn't useful. "The warm palette 
creates approachability but the red CTA button gets lost against the 
orange background — try a contrasting blue or dark green" is useful.

[UPLOAD SCREENSHOT OF A UI]

Analyze this user interface and provide:

1. **UX Assessment**: What's working, what's confusing, what's missing
2. **Accessibility Issues**: Color contrast, touch target sizes, 
   missing labels, keyboard navigation gaps
3. **Improved Layout**: Describe a better arrangement with reasoning
4. **Component Specification**: For each element, specify:
   - Size, spacing, padding
   - Colors (hex values)
   - Typography (font, weight, size)
   - Interactive states (hover, active, disabled)
5. **Implementation Code**: React component with Tailwind CSS that 
   implements the improved version

Focus on making it work better, not just look different.

Write a script for a [LENGTH — e.g., 5-minute] [TYPE — YouTube video / 
TikTok / Instagram Reel / course lesson] about [TOPIC].

Research current information about [TOPIC] to ensure accuracy.

Format:
| Timestamp | Visual | Audio/Script | Notes |
|-----------|--------|-------------|-------|
| 0:00-0:05 | [what's on screen] | [what's said] | [editing note] |

Include:
- Hook in the first 3 seconds (pattern interrupt, not a greeting)
- B-roll suggestions for every scene
- On-screen text/lower thirds callouts
- Transition cues
- Retention tricks at [30%, 50%, 70%] marks to prevent drop-off
- End screen strategy (subscribe CTA, next video suggestion)

Audience: [WHO]
Tone: [e.g., educational but casual]
Key takeaway: [THE ONE THING VIEWERS SHOULD REMEMBER]

[UPLOAD EXISTING SLIDES OR DESCRIBE CURRENT STATE]

Help me improve this presentation.

Context:
- Audience: [WHO]
- Duration: [MINUTES]
- Goal: [WHAT SHOULD HAPPEN AFTER THE PRESENTATION]
- Current problem: [WHY THE EXISTING VERSION ISN'T WORKING]

Provide:
1. Story arc: restructure the narrative flow
2. Slide-by-slide revision:
   - What to keep, cut, or add on each slide
   - Suggested visual for each slide (chart type, image concept, diagram)
   - Speaker notes (what to say, not what's on the slide)
3. Design direction: color palette, fonts, visual style
4. Data visualization: for any data slides, recommend the right chart 
   type and what to emphasize
5. Opening and closing: rewrite these for maximum impact

[UPLOAD AUDIO FILE or describe what you heard]

Analyze this audio and provide:

1. **Genre and style classification**
2. **Instrumentation**: What instruments/sounds are present
3. **Structure**: Verse, chorus, bridge — map the sections with timestamps
4. **Production quality**: Mix balance, clarity, frequency range
5. **Mood and emotional arc**: How the feeling changes through the piece
6. **Similar artists/tracks**: What this reminds you of and why
7. **Strengths**: What makes this compelling
8. **Suggestions**: Specific production or arrangement improvements

Context: This is for [PURPOSE — e.g., a podcast intro, a YouTube background 
track, a demo for a record label].

[UPLOAD PHOTO OF HANDWRITTEN NOTES / WHITEBOARD / PRINTED DOCUMENT]

Transcribe and organize the content in this image.

1. **Raw transcription**: Everything you can read, preserving the 
   original structure as much as possible
2. **Cleaned version**: Fix spelling, complete abbreviations, 
   organize into logical sections
3. **Structured format**: Convert to [DESIRED FORMAT — markdown / 
   spreadsheet / action items / outline]
4. **Unclear sections**: Flag anything you can't read with [ILLEGIBLE] 
   and your best guess

If there are diagrams or sketches, describe them in text and suggest 
how to recreate them digitally.

[UPLOAD IMAGE OF CHART, GRAPH, OR DATA VISUALIZATION]

Analyze this visualization and explain:

1. **What it shows**: Plain-language description of the data
2. **Key trends**: The 3 most important patterns
3. **Outliers**: Any data points that don't fit the pattern
4. **Insights**: What conclusions can be drawn?
5. **Limitations**: What this chart doesn't tell us (or what it 
   might mislead us about)
6. **Presentation critique**: Is this the right chart type for this 
   data? Would another format communicate better?

Context: This is from [SOURCE/PURPOSE]. The audience is [WHO].

[UPLOAD PHOTO OR FLOOR PLAN OF SPACE]

Help me plan this space for [PURPOSE — e.g., home office, retail store, 
event venue, classroom].

Current space dimensions: [IF KNOWN]
Budget: [RANGE]
Must accommodate: [NUMBER OF PEOPLE / EQUIPMENT / ACTIVITIES]
Style preference: [AESTHETIC]
Constraints: [FIXED ELEMENTS THAT CAN'T MOVE — e.g., windows, outlets, plumbing]

Provide:
1. Layout recommendation with furniture/element placement
2. Traffic flow analysis (how people move through the space)
3. Furniture/equipment list with specific product suggestions and 
   prices (search for current options)
4. Lighting plan
5. Storage solutions
6. Alternative layout for different use case (flexibility)

Prioritize function over aesthetics. A beautiful room that doesn't 
work for its purpose is a failure.

[USE IN GEMINI WITHIN GOOGLE WORKSPACE]

Search my emails and documents for everything related to [PROJECT/TOPIC] 
and create a comprehensive status summary.

Look through:
- Recent emails about [PROJECT]
- Documents in my Drive related to [TOPIC]
- Calendar events from the past [TIMEFRAME]

Compile:
1. Current status: Where do things stand?
2. Key decisions made (from email threads)
3. Open questions or unresolved items
4. Upcoming deadlines or meetings
5. People involved and their last contributions
6. Action items that were mentioned but may not have been completed

Format as a status report I can share with [AUDIENCE].

I'm going to give you [NUMBER] documents. Read all of them, then 
synthesize a unified analysis.

[PASTE OR UPLOAD ALL DOCUMENTS]

Don't summarize each document separately. Instead:

1. **Common themes**: What do all/most sources agree on?
2. **Contradictions**: Where do sources disagree? Who's more credible 
   and why?
3. **Unique contributions**: What does each source add that others don't?
4. **Gaps**: What none of them cover?
5. **Synthesis**: Based on all sources together, what's the most 
   defensible conclusion?
6. **Confidence assessment**: How confident should I be in this 
   synthesis? What would make you more or less confident?

Cite specific documents by number when making claims.

Plan a [DURATION] trip to [DESTINATION] for [NUMBER OF TRAVELERS].

Search for current information on:
- Best times to visit (weather, crowds, events)
- Current visa/entry requirements
- Flight and accommodation price ranges
- Must-see attractions and local recommendations
- Safety advisories or travel restrictions

Dates: [WHEN]
Budget: [TOTAL BUDGET]
Interests: [WHAT WE ENJOY — e.g., food, hiking, history, nightlife]
Pace: [PACKED / MODERATE / RELAXED]
Accommodation style: [HOTEL / AIRBNB / HOSTEL / MIX]

Provide:
1. Day-by-day itinerary with specific recommendations
2. Estimated budget breakdown (flights, accommodation, food, activities, transport)
3. Restaurant recommendations (mix of price points)
4. Practical tips (transport, tipping, local customs, apps to download)
5. Backup options for rainy days or closures
6. Booking timeline (what to book now vs. closer to travel)

Research the YouTube landscape for [TOPIC/NICHE].

Search for:
- Top-performing videos on this topic (last 6 months)
- Common video formats and lengths that perform well
- What top creators in this space do differently
- Comment section themes (what audiences want more of)
- Trending subtopics or angles

Deliverables:
1. **Content gap analysis**: What's been covered to death vs. what's underserved
2. **10 video ideas** with:
   - Title (optimized for search and click-through)
   - Thumbnail concept
   - Estimated search volume for the main keyword
   - Content angle that differentiates from existing videos
3. **Recommended format**: Length, style, pacing for this niche
4. **SEO strategy**: Tags, description optimization, chapter markers

I'm going to paste a large codebase (or key files from it). Generate 
comprehensive documentation.

[PASTE CODE FILES — Gemini handles 1M+ tokens, so paste generously]

Generate:
1. **Architecture overview**: High-level diagram description and system design
2. **Module documentation**: For each file/module:
   - Purpose (one sentence)
   - Key exports and their signatures
   - Dependencies (what it imports)
   - Usage examples
3. **Data flow**: How data moves through the system
4. **API documentation**: For each endpoint/function:
   - Signature, parameters, return type
   - Example usage
   - Error cases
5. **Getting started guide**: How a new developer sets up and 
   contributes to this project
6. **Glossary**: Domain-specific terms used in the code

Write for a developer joining the team tomorrow.

I'm going to share a collection of notes, bookmarks, highlights, 
and thoughts on [TOPIC]. Help me turn them into an organized 
knowledge base.

[PASTE ALL YOUR RAW NOTES, HIGHLIGHTS, LINKS, THOUGHTS]

Process them into:
1. **Core concepts**: The key ideas, defined clearly
2. **Relationships**: How concepts connect to each other
3. **Key takeaways**: The most important insights (ranked)
4. **Questions**: Things I should investigate further
5. **Action items**: Things I can do based on this knowledge
6. **Organized notes**: Restructured version of my raw notes, 
   grouped by theme, with duplicates merged
7. **Suggested reading**: Based on the gaps in my notes, what 
   should I read next?

Don't lose any of my original ideas or annotations. Restructure, 
don't replace.

I'm dealing with [PROBLEM] right now and need to make a decision 
in [TIMEFRAME].

Situation: [DESCRIBE WHAT'S HAPPENING]
Options I see: [LIST THE OPTIONS YOU'VE IDENTIFIED]
Constraints: [TIME / MONEY / PEOPLE / TECHNICAL LIMITATIONS]

Search for any relevant current information that could inform 
this decision:
[SPECIFIC THINGS TO LOOK UP — e.g., "current pricing for [SERVICE]" 
or "reported issues with [TOOL] version X"]

Help me:
1. Assess each option (pros, cons, risks)
2. Identify options I might be missing
3. Recommend the best path given the constraints
4. Provide a quick action plan (numbered steps, next 2 hours)
5. Identify the decision point where I should reassess if things 
   aren't working

Be decisive. I need a recommendation, not a balanced essay.

I frequently need AI help with these tasks:
1. [TASK 1 — e.g., writing client proposals]
2. [TASK 2 — e.g., debugging Python code]
3. [TASK 3 — e.g., analyzing sales data]
4. [TASK 4 — e.g., creating social media posts]
5. [TASK 5 — e.g., summarizing meeting recordings]

For each task, create:
- A reusable prompt template with [PLACEHOLDER] variables
- Explanation of what makes this prompt effective for Gemini specifically
- Variations for different subtypes of the task
- Common mistakes to avoid when using the template
- How to modify the prompt when results aren't right

Also create:
- A "meta prompt" I can use to generate new prompts for tasks 
  not on this list
- A quality checklist I can use to evaluate AI output before using it

Format everything so I can copy-paste directly.