40 Best Grok Prompts in 2026: Templates for xAI's Real-Time AI

What's trending on X right now about [TOPIC]? Give me:

1. The 3 most-shared takes (summarize each in 2 sentences)
2. What the general sentiment is (positive, negative, split)
3. Who the most influential voices are in this conversation
4. What most people are getting wrong about this topic
5. A contrarian take that has merit but isn't mainstream

Don't sanitize the takes. I want to know what people are 
actually saying, not the polished version.

Search X for recent posts about [COMPETITOR COMPANY/PRODUCT].

I want to know:
1. What their customers are publicly complaining about (last 30 days)
2. What they're publicly praising
3. Any recent product announcements or changes
4. Public sentiment shift — are people more or less happy than 3 months ago?
5. Specific feature requests or pain points I could exploit

My product: [BRIEF DESCRIPTION]
Format the findings as a competitive intelligence brief.

What's happening right now with [EVENT/TOPIC]?

Give me:
1. Factual summary (what we actually know, confirmed only)
2. What's being reported but unconfirmed
3. Key sources and voices to follow for updates
4. How this compares to [RELATED PAST EVENT]
5. What happens next (most likely scenarios)

Separate facts from speculation clearly. I don't want hot takes 
dressed up as news.

Analyze public sentiment on X about [TOPIC/BRAND/POLICY].

Deliver:
1. Overall sentiment breakdown (positive / negative / neutral — estimate percentages)
2. Top 5 recurring arguments FOR
3. Top 5 recurring arguments AGAINST
4. Demographics of each side (if patterns are visible — e.g., tech workers vs. general public)
5. The most viral/shared take from each side
6. My honest assessment of which side has stronger arguments

Don't both-sides this if one side is clearly stronger. Tell me 
what you actually think.

I can't follow [EVENT — conference, product launch, sports event, 
political event] live. Give me a real-time briefing.

Cover:
1. Key announcements or moments so far
2. Biggest surprises (what wasn't expected)
3. Public reaction on X (what's blowing up)
4. What flopped or got criticized
5. Most quotable moment
6. Your one-line summary of the whole thing

Update this if I ask again in a few hours.

What's the current conversation on X about [INDUSTRY] this week?

I want:
1. The 3 hottest topics being discussed
2. New tools, products, or companies getting attention
3. Any drama, controversy, or feuds
4. Hiring/layoff signals
5. The smartest thread or take you can find from this week

I'm a [YOUR ROLE] in this industry. Flag anything I should 
actually care about vs. noise.

This claim is going viral: "[PASTE CLAIM OR DESCRIBE IT]"

Fact-check it:
1. What's being claimed exactly?
2. What evidence supports it?
3. What evidence contradicts it?
4. What context is being left out?
5. Verdict: true, mostly true, misleading, mostly false, or false
6. Why it's spreading (what makes it emotionally compelling regardless of accuracy)

Be direct. Don't hedge if the answer is clear.

What news in the last 24 hours could affect [MARKET/INDUSTRY/STOCK]?

Cover:
1. Any regulatory or policy changes
2. Major company announcements
3. Economic data releases
4. Geopolitical events with market impact
5. Social media buzz that's moving sentiment

For each item:
- What happened
- Why it matters for [MY SPECIFIC INTEREST]
- Likely direction of impact (positive/negative/neutral)

Write an X thread about [TOPIC]. 10-12 tweets.

My voice: [DESCRIBE — e.g., "sharp, data-driven, occasionally sarcastic"]
Audience: [WHO FOLLOWS ME]
Goal: [EDUCATE / BUILD AUTHORITY / DRIVE TRAFFIC / START A CONVERSATION]

Thread rules:
- Tweet 1: hook that makes people stop scrolling (controversial take, 
  surprising stat, or bold claim)
- Each tweet stands alone but builds the narrative
- Include 1-2 specific data points or examples
- End with a CTA or question that generates replies
- No "🧵 Thread:" opener (amateur move)
- No numbered tweets unless it's a list thread

Be punchy. Every word earns its spot.

I need honest feedback on this writing. Not "great job with some 
minor suggestions" — actual, useful critique.

[PASTE YOUR WRITING]

Tell me:
1. What works (be specific — which sentences or sections are strong)
2. What's weak and exactly why
3. Where I'm being boring, vague, or pretentious
4. One structural change that would make the biggest difference
5. Rewrite the worst paragraph to show me what you mean

Don't protect my feelings. I want to be a better writer, not feel 
good about mediocre work.

Write an op-ed arguing [POSITION] on [TOPIC].

Audience: [WHO READS THIS PUBLICATION/PLATFORM]
Length: 800-1,000 words
Tone: confident, direct, willing to be unpopular

Structure:
- Open with a provocative statement or counterintuitive observation
- Acknowledge the best argument against your position (then dismantle it)
- Support with 3 specific pieces of evidence
- Close with a call to action or memorable final line

Don't hedge. Take the position and defend it. If there's a genuine 
weakness in the argument, acknowledge it and explain why the position 
still holds.

Here's the copy from my landing page. Roast it.

[PASTE LANDING PAGE TEXT]

Product: [WHAT IT IS]
Target customer: [WHO]
Conversion goal: [SIGN UP / BUY / BOOK DEMO]

Tell me:
1. Where a visitor would bounce (and why)
2. Sentences that say nothing
3. Claims without proof
4. Where the CTA is buried or weak
5. What my competitor does better (check their site if you can)

Then rewrite the hero section (headline + subheadline + CTA) to 
show me what good looks like for this product.

Read these samples of my writing and extract my voice:

[PASTE 2-3 EXAMPLES OF YOUR WRITING]

Now write [CONTENT TYPE — email, blog post, bio, about page] in 
my voice about [TOPIC].

Rules:
- Match my sentence length patterns
- Use my vocabulary (not yours)
- Mirror my level of formality
- If I use humor, match the type and frequency
- If I'm direct, don't add qualifiers

After writing, show me 3 specific choices you made to match my 
voice and what you drew them from.

I wrote this for [TECHNICAL AUDIENCE]. Rewrite it for [NON-TECHNICAL AUDIENCE].

Original:
[PASTE JARGON-HEAVY TEXT]

Rules:
- Replace every piece of jargon with plain language
- Keep the accuracy — don't dumb it down, translate it
- Use analogies for complex concepts
- If something genuinely can't be simplified, define it in one sentence
- Maintain approximately the same structure and length
- Flag anything where simplification loses important nuance

This code has a bug I can't find. Help me debug it.

Language: [LANGUAGE]
Framework: [IF APPLICABLE]
What should happen: [EXPECTED BEHAVIOR]
What actually happens: [BUG DESCRIPTION]
What I've already tried: [LIST ATTEMPTS]

Code:
[PASTE CODE]

Don't just spot the bug — walk me through your debugging thought 
process. What would you check first, second, third? I want to 
learn the approach, not just the answer.

Convert this code from [SOURCE LANGUAGE] to [TARGET LANGUAGE].

Source code:
[PASTE CODE]

Requirements:
- Idiomatic [TARGET LANGUAGE] — don't just translate syntax
- Use [TARGET LANGUAGE] standard library equivalents where possible
- Preserve all error handling (adapt patterns to target language conventions)
- Add comments where the translation involved a non-obvious design choice
- Note any features that don't have a direct equivalent and how you handled them

I need to decide between these approaches for [FEATURE/SYSTEM].

Option A: [DESCRIBE APPROACH A]
Option B: [DESCRIBE APPROACH B]
Option C: [DESCRIBE APPROACH C — if applicable]

Context:
- Tech stack: [LANGUAGES, FRAMEWORKS]
- Team size: [NUMBER]
- Expected scale: [USERS, REQUESTS, DATA VOLUME]
- Priority: [SHIP FAST / SCALE WELL / EASY TO MAINTAIN]

For each option:
1. Pros (be specific, not generic)
2. Cons (be honest, not diplomatic)
3. When it becomes painful (at what scale or complexity does it break down)
4. Migration effort if we need to switch later

Give me your actual recommendation. Don't end with "it depends."

I need a regex pattern for [DESCRIBE WHAT YOU WANT TO MATCH].

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

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

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

Provide:
1. The regex pattern
2. Breakdown of what each part does (annotated)
3. Edge cases it handles
4. Edge cases it DOESN'T handle (be honest)
5. A test function I can run to verify it

This code is slow. Help me optimize it.

Code:
[PASTE CODE]

Context:
- Current performance: [HOW SLOW — response time, throughput, etc.]
- Acceptable target: [WHAT "FAST ENOUGH" LOOKS LIKE]
- Dataset size: [HOW MUCH DATA]
- Constraints: [WHAT I CAN'T CHANGE]

Steps:
1. Identify the bottleneck(s) — be specific about which lines
2. Explain WHY it's slow (algorithmic complexity, I/O, etc.)
3. Propose fixes ranked by impact
4. Show the optimized code for the highest-impact fix
5. Estimate the improvement (order of magnitude is fine)

Build a CLI tool that does [WHAT IT SHOULD DO].

Language: [LANGUAGE PREFERENCE]
Input: [WHAT THE USER PROVIDES — args, files, stdin]
Output: [WHAT THE TOOL PRODUCES]

Requirements:
- Clean argument parsing with --help
- Useful error messages (not stack traces)
- Handle edge cases (missing files, bad input, permissions)
- Exit codes (0 for success, non-zero for different error types)
- One-liner usage example in the help text

Make it the kind of tool a developer would actually alias and use daily.

I believe [THESIS/POSITION]. Stress test it.

My reasoning:
[EXPLAIN YOUR ARGUMENT]

Attack it:
1. Strongest counterargument I'm probably not considering
2. Evidence that contradicts my position
3. Logical fallacies in my reasoning (if any)
4. Assumptions I'm making that might be wrong
5. What would need to be true for my position to be wrong
6. Steel-man the opposing view — make the best case against me

Then tell me: after this analysis, is my position still defensible? 
If so, how should I modify it to be stronger? If not, what position 
should I actually hold?

Explain [COMPLEX TOPIC] to me. I'm intelligent but have no 
background in this field.

Rules:
- No jargon without immediate definition
- Use analogies from [FIELD I KNOW — e.g., software, cooking, sports]
- Build from first principles — don't assume I know the basics
- Include one counterintuitive fact that makes the topic interesting
- Tell me what most introductions to this topic get wrong
- End with: the one thing I should learn next if this interests me

Length: 500-800 words. Dense but not rushed.

Perform a SWOT analysis for [COMPANY/PRODUCT/STRATEGY].

Context: [RELEVANT BACKGROUND]

For each quadrant:
- 3-5 items (specific, not generic)
- For each item: why it matters and what to do about it

After the standard SWOT:
1. Cross-analysis: which strength best addresses which threat?
2. Critical vulnerability: the one weakness-threat combo that could kill us
3. Biggest opportunity: the one strength-opportunity combo we're underexploiting
4. 90-day action plan based on findings

Don't give me a textbook SWOT. Give me one that changes how I 
think about the situation.

Review this document and flag everything I should pay attention to.

[PASTE DOCUMENT]

I am not a lawyer and you are not my lawyer. But as a smart 
reader, help me:

1. Summarize what this document actually says in plain English
2. Flag clauses that are unusual, aggressive, or one-sided
3. Identify anything that limits my rights or creates obligations
4. Point out vague language that could be interpreted against me
5. List questions I should ask a lawyer about
6. On a 1-10 scale, how favorable is this document to me?

Highlight specific sections with quotes. Don't generalize.

Something went wrong: [DESCRIBE THE PROBLEM/INCIDENT].

Known facts:
[LIST EVERYTHING YOU KNOW]

Timeline:
[WHAT HAPPENED AND WHEN]

Apply the "5 Whys" method:
- Start with the surface problem
- Dig into each layer with "Why did that happen?"
- Continue until you reach a systemic or actionable root cause

Then:
1. Root cause (one sentence)
2. Contributing factors (things that made it worse)
3. Why existing safeguards failed
4. Short-term fix (stop the bleeding)
5. Long-term fix (prevent recurrence)
6. What we should monitor going forward

Here's some data. Tell me what it actually means.

Data:
[PASTE RAW DATA, METRICS, OR RESULTS]

Context: [WHAT THIS DATA IS FROM AND WHAT DECISIONS DEPEND ON IT]

Analysis:
1. What's the headline finding? (one sentence)
2. What's the second thing most people would miss?
3. Are there confounding factors or alternative explanations?
4. What does this data NOT tell us that we'd need to know?
5. If I had to make a decision based on this alone, what should it be?
6. What additional data would make the decision more confident?

Be straight with me about confidence levels. "This data suggests X" 
is more useful than "This data proves X" if that's the truth.

Help me position [PRODUCT] in the market.

What it does: [DESCRIPTION]
Current customers: [WHO'S BUYING AND WHY]
Competitors: [TOP 3 ALTERNATIVES]
Our price: [AMOUNT]
Our actual advantage: [BE HONEST]

Create:
1. Positioning statement (format: For [target], [product] is the [category] 
   that [key benefit] unlike [alternative] because [reason])
2. Three positioning options (premium, challenger, niche) with pros/cons
3. Homepage headline for each positioning
4. Elevator pitch (30 seconds, for each positioning)
5. Your recommendation with reasoning

Analyze these customer feedback snippets and extract actionable insights.

Feedback:
[PASTE REVIEWS, SUPPORT TICKETS, SURVEY RESPONSES, OR NPS COMMENTS]

Deliver:
1. Top 3 themes (what keeps coming up)
2. Top 3 specific feature requests (with frequency)
3. Most common frustration (exact quotes)
4. What customers love most (exact quotes)
5. Churn risk signals (warning signs in the language)
6. Priority matrix: what to fix first based on frequency × severity
7. One insight that isn't obvious from reading individual reviews

Create interview questions for a [ROLE] position.

Level: [JUNIOR / MID / SENIOR / LEAD]
Key skills: [LIST 3-5]
Team context: [SIZE, CULTURE, CURRENT CHALLENGES]
Biggest past hiring mistake for this role: [WHAT WENT WRONG]

Provide:
1. 5 technical/skill questions (with what a good answer looks like)
2. 3 behavioral questions (with red flag and green flag responses)
3. 1 scenario/case question (realistic to your company)
4. 2 culture-fit questions (that aren't "tell me about a time")
5. 1 question designed to test specifically for [YOUR CONCERN]

For each question: what signal are you looking for, and what's the 
typical bad answer that sounds good on the surface.

Help me draft communications for this situation:

The crisis: [WHAT HAPPENED]
Who's affected: [CUSTOMERS, EMPLOYEES, PUBLIC, etc.]
What we know: [CONFIRMED FACTS]
What we don't know yet: [UNCERTAINTIES]
Our responsibility: [OUR ROLE — caused it, affected by it, responding]

Write:
1. Internal team message (honest, detailed, calming)
2. External customer communication (transparent but controlled)
3. Social media statement (short, human, no corporate speak)
4. Q&A document (10 likely questions with answers)
5. Follow-up communication (for 24-48 hours later with updates)

Rules:
- Never lie or mislead, even by omission
- Don't over-apologize or under-acknowledge
- Specific next steps, not vague promises

Evaluate this potential partnership opportunity.

Partner: [WHO THEY ARE]
Proposed deal: [WHAT THEY'RE OFFERING]
What they want from us: [THEIR ASK]
Our current situation: [RELEVANT CONTEXT]

Analyze:
1. Strategic fit (does this advance our goals?)
2. Risk assessment (what could go wrong)
3. Power dynamics (who needs whom more)
4. Hidden costs (beyond what's on the term sheet)
5. Alternatives (what else could achieve the same goal)
6. Deal-breakers to watch for
7. Negotiation leverage points (theirs and ours)
8. Recommendation: proceed, pass, or counter with [MODIFICATION]

I'm considering these revenue models for [BUSINESS/PRODUCT]:

Option A: [MODEL — e.g., subscription, freemium, one-time, marketplace]
Option B: [MODEL]
Option C: [MODEL]

My context:
- Product type: [DESCRIPTION]
- Target customer: [WHO]
- Market size estimate: [NUMBER]
- Current stage: [PRE-LAUNCH / EARLY / GROWING / MATURE]

For each model:
1. Revenue projection logic (how money flows)
2. Key metrics to track
3. When it works best (market conditions, product type)
4. Biggest risk
5. Example companies using this model successfully
6. How it affects product decisions and user experience

Which model should I start with and why? Which should I layer on later?

Switch to your most creative, unfiltered mode. I need ideas for 
[CREATIVE CHALLENGE] and I want them weird.

Context: [WHAT THIS IS FOR]
Audience: [WHO SEES THIS]
Constraints: [WHAT'S OFF-LIMITS — if anything]

Give me:
- 5 ideas that would make a marketing VP nervous
- 5 ideas that are actually brilliant but sound stupid at first
- 3 ideas that combine two things nobody has combined before
- 1 idea so good it makes the others look boring

Don't self-censor. I'll decide what's too far. Your job is to go there.

Roast my business idea. Be merciless but constructive.

The idea: [DESCRIBE IT]
My target market: [WHO]
Why I think it'll work: [YOUR REASONING]
How far along I am: [STAGE]

I want:
1. The most devastating criticism you can make (that's also fair)
2. The thing I'm definitely wrong about
3. The competition I'm underestimating
4. The customer objection that'll kill me
5. Whether any version of this idea has legs (brutal honesty)

After the roast: if you were going to build this anyway, what's the 
one change that would give it the best chance?

Write [TYPE — standup bit, sketch, satirical article, roast] about [TOPIC].

Tone: [DRY / ABSURD / DARK / SELF-DEPRECATING / OBSERVATIONAL]
Audience: [WHO'S LAUGHING]
Length: [TARGET]

Rules:
- Actually be funny. Not "corporate humor" funny. Actually funny.
- Specific observations beat generic jokes
- Setup-punchline structure where it works
- Callbacks to earlier material if doing longer form
- One joke that's probably too far (let me decide)

Also tell me which joke you think is the strongest and why it works 
mechanically (the surprise, the reversal, the recognition).

Create 10 meme concepts about [TOPIC/INDUSTRY/SITUATION].

For each meme:
1. Format (which meme template)
2. Top text
3. Bottom text (or caption)
4. Why it's funny to people in [NICHE]

Mix of:
- Self-deprecating industry humor
- "It's funny because it's true" observations
- References the community will get
- At least 2 that are spicy enough to get engagement

I'll create the images. You just need to nail the concepts.

Write two versions of a cover letter for [JOB].

Version 1: What I'd actually send (professional, compelling, human)
Version 2: What I actually want to say (honest to the point of 
absurdity — the inner monologue version)

Job: [ROLE AND COMPANY]
My background: [BRIEF SUMMARY]
Why I actually want this job: [HONEST REASON]

The contrast between the two versions should be funny but also 
reveal real insight about the hiring process.

Explain [MODERN CONCEPT] to someone from [HISTORICAL PERIOD].

The concept: [e.g., social media, cryptocurrency, remote work]
The audience: [e.g., a medieval farmer, a Roman senator, a 1920s detective]

Rules:
- Use only concepts and analogies they'd understand
- Stay in character for the explainer
- Include their likely reaction and follow-up questions
- Make it accurate AND entertaining
- End with the one aspect they'd find most absurd

Give me hot takes about [INDUSTRY/TOPIC] that would start a debate.

I want:
- 5 genuinely contrarian positions (not just "unpopular opinion: popular thing")
- Each take should be defensible with evidence
- For each: the take (one sentence), the argument (3 sentences), 
  and the counterargument you'd face
- Rate each 1-10 on "how angry this would make the average [INDUSTRY] 
  person on X"

I'm not trying to rage-bait. I want takes that make smart people 
think "wait, actually..."

Pitch me [RIDICULOUS PRODUCT IDEA] as if it's the next billion-dollar startup.

The product: [DESCRIBE SOMETHING ABSURD]

Give me the full pitch:
- Problem statement (make it sound legitimate)
- Solution (with total conviction)
- Market size (creative math encouraged)
- Competitive moat
- Go-to-market strategy
- 5-year vision
- The slide that makes investors cry

Commit fully to the bit. No winking at the camera. The humor comes 
from how seriously you take something ridiculous.