ChatGPT vs Gemini — Complete Comparison

Compare {{option_a}} vs {{option_b}} for {{use_case}}.

Structure your analysis as:

1. **Overview**: One sentence summary of each option
2. **Strengths**: Top 3 strengths of each, with specific examples
3. **Weaknesses**: Top 3 weaknesses of each, with workarounds where possible
4. **Cost comparison**: Break down pricing for a {{team_size}} team
5. **Verdict**: Recommend one for each of these scenarios:
   - Budget-constrained team
   - Performance-first team
   - Team already using {{existing_tool}}

Be opinionated. Don't hedge with "it depends" without specifying what it depends on.

I'm sharing {{media_type}} with you. Analyze it and provide:

1. **Description**: What you see/hear in detail (be specific about elements, layout, colors, text)
2. **Key information extraction**: Pull out all data points, names, numbers, dates, or actionable items
3. **Quality assessment**: Rate the {{media_type}} quality on a 1-10 scale with justification
4. **Suggestions**: {{num_suggestions}} specific, actionable improvements
5. **Accessibility**: Note any accessibility concerns (alt text needed, contrast issues, readability)

Format the extracted information as a structured table where applicable.

Write a {{language}} function that {{function_description}}.

Requirements:
- Input: {{input_description}}
- Output: {{output_description}}
- Handle edge cases: empty input, null values, invalid types
- Time complexity should be O({{complexity}}) or better
- Include JSDoc/docstring with parameter descriptions and return type

After the function, provide:
1. Three test cases covering normal, edge, and error scenarios
2. A brief explanation of your algorithmic approach
3. One alternative approach with its tradeoff

Do not include unnecessary comments in the code itself — the code should be self-documenting.

Analyze the following {{data_type}} data:

{{data_or_description}}

Perform this analysis:
1. **Summary statistics**: Key metrics, averages, ranges, distributions
2. **Trends**: Identify the top 3 most significant patterns or trends
3. **Anomalies**: Flag any outliers or unexpected data points with possible explanations
4. **Correlations**: Note relationships between variables (if multiple variables exist)
5. **Recommendations**: {{num_recommendations}} data-driven recommendations for {{stakeholder}}

Present findings in order of business impact (highest first). Use tables for numerical comparisons. If the data is insufficient to draw a conclusion, say so explicitly rather than speculating.

Write a {{content_type}} about {{topic}}.

Specifications:
- Tone: {{tone}}
- Target audience: {{audience}}
- Length: {{word_count}} words
- Purpose: {{purpose}}

Style guidelines:
- Open with a hook — not a definition or generic statement
- Use concrete examples and specific details over abstract claims
- Vary sentence length (mix short punchy sentences with longer flowing ones)
- End with a memorable closing line, not a summary

Avoid: cliches, passive voice where active is stronger, starting paragraphs with "In today's world" or "It's important to note that".

Research and summarize {{topic}} for a {{audience}} audience.

Structure:
1. **TL;DR** (2-3 sentences maximum)
2. **Background**: Essential context needed to understand the topic (keep under 150 words)
3. **Current state**: What's happening right now — key players, recent developments, numbers
4. **Key debates**: Where experts disagree and why
5. **What to watch**: 3 specific things that will shape this topic in the next {{timeframe}}
6. **Sources to explore**: Suggest 5 specific search queries to find primary sources on this topic

Important: Clearly distinguish between established facts and your analysis/predictions. Use "[Analysis]" tags before opinionated statements.

Draft an email for this situation:

Context: {{situation_context}}
Recipient: {{recipient_role}} at {{company_or_context}}
My goal: {{desired_outcome}}
Tone: {{tone}} (but not sycophantic)
Constraints: Under {{max_sentences}} sentences

Requirements:
- Subject line that gets opened (not clickbait)
- First sentence states why you're writing — no throat-clearing
- One clear ask or next step
- Close with a specific action and timeline, not "let me know your thoughts"

Provide two versions:
Version A: Direct and concise
Version B: Slightly warmer / more relationship-oriented

Create a learning plan for {{skill_or_topic}}.

My current level: {{current_level}}
Time available: {{hours_per_week}} hours/week for {{duration}}
Learning style: {{learning_preference}}
Goal: {{specific_goal}}

Structure the plan as:
- **Week-by-week breakdown** with specific topics and estimated time per topic
- **Resources** for each week (describe the type of resource, e.g., "interactive tutorial on X" — don't invent URLs)
- **Milestones**: What I should be able to do after each phase
- **Practice projects**: One hands-on project per phase that builds on the previous one
- **Assessment**: How to know when I'm ready to move to the next phase

Make it realistic — account for review time and assume I'll forget 20% between sessions.