Back to guide/Developer Tools

Research with Source Grounding

Gemini's Google Search grounding provides more current data. Claude's careful reasoning produces better evidence assessment. The [Analysis] tag technique works on both to separate facts from interpretation.

claude-vs-geminitopicaudiencetimeframe
Edit View
Prompt
Research {{topic}} and provide a comprehensive briefing for a {{audience}} audience.

Structure:
1. **TL;DR**: 3 sentences maximum
2. **Background**: Essential context (under 150 words)
3. **Current landscape**: Key players, recent developments (past {{timeframe}}), and market/field dynamics
4. **Evidence review**: Summarize the strongest evidence on each side of the key debates. For each claim, note:
   - Source type (peer-reviewed study, industry report, expert opinion, anecdotal)
   - Confidence level (high/medium/low)
   - Potential bias of the source
5. **Contrarian view**: What's the strongest argument against the mainstream position?
6. **Practical implications**: What should {{audience}} actually do with this information?
7. **Search queries**: 5 specific search terms to find primary sources (not URLs)

Mark all speculative or analytical statements with [Analysis]. Keep factual claims and interpretation clearly separated.

Variables to customize

{{topic}}{{audience}}{{timeframe}}

Why this prompt works

Gemini's Google Search grounding provides more current data. Claude's careful reasoning produces better evidence assessment. The [Analysis] tag technique works on both to separate facts from interpretation.

Save this prompt to your library

Organize, version, and access your best prompts across ChatGPT, Claude, and Cursor.

Related prompts

Code Review Assistant

Get thorough code reviews with actionable feedback tailored to your language, framework, and standards.

Context-Aware Code Completion

Providing the surrounding code and project context lets the model match existing patterns exactly. The constraint against modifying existing code prevents unwanted side effects.

Inline Code Suggestion

Constraining suggestions to match existing style and scope produces insertions that feel native to the codebase. The 'no explanation' rule mimics real inline completion behavior.

Code Explanation

The audience level parameter adjusts complexity automatically. Requiring a usage example ensures the explanation is practical, not just theoretical.