40 Powerful AI Prompts for Claude That Produce Expert-Level Results

I tested 500+ prompts, and these are the 40 that produce expert-level output every single time.

Save this :)

Most prompt collections are generic. "Write me a blog post." "Summarize this text." "Explain this concept."

Those are not prompts. Those are wishes.

A real prompt is an engineered instruction that produces consistent, high-quality, production-ready output regardless of which model you use. It includes the role, the context, the constraints, the format, the quality standard, and specific examples.

These 40 prompts work on Claude, ChatGPT, AND Gemini. Tested on all three. Verified on all three. Copy-paste ready.

Organized by use case. Difficulty-rated. Save this.

Writing and Content (01 to 10)

01. The Expert Article Writer

You are a senior content strategist who has written for top-tier publications.

Write a [WORD COUNT]-word article about [TOPIC].

Audience: [WHO THEY ARE and WHAT THEY KNOW] Angle: [YOUR UNIQUE TAKE — what makes this different from every other article on this topic]

Structure:

• Hook: Open with a bold claim or surprising fact. No generic introductions.
• Problem: Why the current way of thinking about this topic is wrong or incomplete.
• Framework: Present your argument in 3-5 named sections with clear headers.
• Evidence: Each section must include one specific example, case study, or data point.
• Action: End with 3 specific things the reader can do THIS WEEK.

Rules:

• Paragraphs: 3 sentences maximum
• No filler phrases ("it is important to note", "in today's world")
• No hedge words ("might", "could potentially", "it seems like")
• Every claim must be specific, not vague
• Bold the most important sentence in each section

This article should be good enough to publish without editing.

02. The Thread Architect

Write a Twitter/X thread about [TOPIC].

Thread structure:

• Tweet 1: The hook. Bold claim, surprising stat, or contrarian take. Must stop the scroll in 2 seconds.
• Tweets 2-3: The problem. Why most people get this wrong.
• Tweets 4-10: The framework. Numbered steps, techniques, or insights. One per tweet. Each tweet must stand alone AND flow in sequence.
• Tweet 11-12: Real example or case study proving the framework works.
• Final tweet: One actionable takeaway + call to action.

Rules:

• Each tweet under 280 characters
• No hashtags
• No emojis unless they add meaning
• No "let me explain" or "here's the thing" — start each tweet with substance
• Thread should feel like learning from a sharp friend, not reading a textbook

Total: 12-15 tweets.

03. The Email Drafter

Draft an email for this situation: [DESCRIBE THE SITUATION, THE RECIPIENT, AND YOUR GOAL]

Tone: [professional/casual/direct/diplomatic]

Rules:

• Subject line: specific and action-oriented (not "Quick question" or "Following up")
• Opening: Get to the point in the first sentence. No "I hope this finds you well."
• Body: Maximum 3 short paragraphs. Each paragraph serves one purpose.
• Close: Clear next step or ask. The recipient should know exactly what you want them to do.
• Total length: Under 150 words

Generate 2 versions: Version A: [TONE 1 — e.g., direct and assertive] Version B: [TONE 2 — e.g., warm and collaborative]

04. The Content Repurposer

Take this content and repurpose it into 5 formats:

<original_content> [PASTE YOUR ARTICLE/POST/TRANSCRIPT] </original_content>

Create:

1. Twitter/X thread (12 tweets, each under 280 characters)

2. LinkedIn post (200-300 words, professional but not corporate)

3. Newsletter intro (100 words, teases the full content)

4. 3 standalone social media posts (each self-contained, each highlighting a different insight)

5. Short-form video script (60 seconds, conversational, designed to be spoken to camera)

Rules:

• Each format should feel native to its platform, not like a copy-paste
• Maintain the core argument and key insights across all formats
• Adjust tone per platform: X = punchy and direct, LinkedIn = professional and thoughtful, Newsletter = personal and exclusive

05. The Copywriting Converter

Rewrite this text to be more persuasive:

<original> [PASTE TEXT] </original>

Apply these copywriting principles:

• Lead with the benefit, not the feature
• Use specific numbers instead of vague claims
• Address objections before they form
• Create urgency without being manipulative
• End with a clear, low-friction call to action

Show the rewritten version, then explain the 3 most impactful changes you made and why they work psychologically.

06. The Blog Post Outliner

Create a detailed outline for a blog post about [TOPIC].

Target audience: [WHO] Goal: [WHAT THE READER SHOULD DO/FEEL/KNOW AFTER READING] Target length: [WORD COUNT]

For each section, provide:

• Header (compelling, specific, not generic)
• 2-3 sentence summary of what this section covers
• The key data point, example, or argument this section needs
• Transition to the next section

Also include:

• 3 alternative headline options (ranked by predicted click-through)
• Suggested meta description (under 160 characters)
• 5 internal/external linking opportunities

07. The Storytelling Transformer

Take this dry, factual information and transform it into a compelling narrative:

<facts> [PASTE DRY FACTS, DATA, OR TECHNICAL CONTENT] </facts>

Rules:

• Open with a specific scene, person, or moment — not a definition
• Weave the facts into a story arc: setup → tension → resolution
• Use analogies to make complex ideas feel intuitive
• Include one "aha moment" where the reader's understanding shifts
• End with a takeaway that connects the story back to the reader's life

Keep the facts accurate. Change the delivery, not the truth.

08. The Headline Generator

Generate 20 headline options for this content: [BRIEF DESCRIPTION OF THE CONTENT]

Categories:

• 5 curiosity-driven headlines (make them NEED to click)
• 5 benefit-driven headlines (make them see the value immediately)
• 5 contrarian headlines (challenge what they currently believe)
• 5 specific-number headlines (use exact quantities or timeframes)

For each headline, rate its predicted click-through on a scale of 1-10 and explain why.

Rank your top 3 overall with reasoning.

09. The Case Study Builder

Turn these raw facts into a compelling case study:

Client: [NAME/TYPE] Problem: [WHAT THEY STRUGGLED WITH] Solution: [WHAT WAS IMPLEMENTED] Results: [MEASURABLE OUTCOMES]

Structure:

1. The Challenge (2 paragraphs — make the reader feel the pain)

2. The Approach (3-4 paragraphs — specific steps taken, not generic descriptions)

3. The Results (1-2 paragraphs — specific numbers, before/after comparisons)

4. Key Takeaway (1 paragraph — the lesson that applies to the reader)

5. Pull Quote (one sentence the client would actually say, based on the results)

Rules:

• Use present tense for immediacy
• Include at least 3 specific numbers
• The pull quote should feel real, not like marketing copy

10. The Style Mimic

Analyze these 3 writing samples from the same author:

<sample_1>[PASTE]</sample_1> <sample_2>[PASTE]</sample_2> <sample_3>[PASTE]</sample_3>

Identify:

• Sentence length patterns (short, mixed, long)
• Vocabulary level (simple, technical, mixed)
• Tone (formal, casual, authoritative, conversational)
• Structural habits (paragraph length, use of headers, bullet patterns)
• Signature phrases or patterns they repeat
• Things they consistently avoid

Then write a 300-word piece about [NEW TOPIC] that matches this author's exact style. The reader should believe the original author wrote it.

Analysis and Strategy (11 to 20)

11. The SWOT Analyzer

Perform a comprehensive SWOT analysis of [COMPANY/PRODUCT/STRATEGY].

For each quadrant (Strengths, Weaknesses, Opportunities, Threats):

• List 5 specific items (not generic — tied to THIS specific situation)
• For each item: one sentence explaining WHY it belongs in this quadrant
• Rate each item's impact: High / Medium / Low

Then provide:

• The #1 strategic priority based on this analysis (one sentence)
• The biggest risk if this priority is ignored (one sentence)
• The first action to take this week (one specific, actionable step)

12. The Decision Matrix

I need to decide between these options: [LIST 2-4 OPTIONS]

Context: [RELEVANT BACKGROUND — budget, timeline, team, goals]

Build a decision matrix:

1. Identify the 5 most important criteria for this decision (ask me if unsure)

2. Weight each criterion by importance (must total 100%)

3. Score each option against each criterion (1-10)

4. Calculate weighted scores

5. Present as a formatted table

Then write a 2-paragraph recommendation that:

• Clearly states which option to choose and why
• Acknowledges the strongest argument for the runner-up
• Identifies the one condition that would change the recommendation

13. The Root Cause Analyzer

Here is a problem I am facing: [DESCRIBE THE PROBLEM AND ITS SYMPTOMS]

Perform a root cause analysis:

1. Ask "Why?" 5 times in sequence (the 5 Whys technique), going deeper each time

2. For each level, identify whether this is a symptom or a root cause

3. At the deepest level, identify the TRUE root cause

4. Propose 3 solutions — one for the surface symptom, one for the mid-level cause, and one for the root cause

5. Recommend which solution to implement and why

Do not accept my initial framing of the problem at face value. The real problem is often not the one I described.

14. The Market Opportunity Scanner

Analyze the market opportunity for [PRODUCT/SERVICE IDEA].

Evaluate:

1. DEMAND: Who wants this? How many of them are there? How do you know they want it?

2. COMPETITION: Who else does this? What do they charge? Where are they weak?

3. TIMING: Why now? What changed that makes this viable today when it was not before?

4. MOAT: What would prevent competitors from copying this in 6 months?

5. UNIT ECONOMICS: What would this cost to deliver per customer vs. what could you charge?

For each section: be specific, use numbers where possible, and flag anything you are uncertain about.

End with a GO / CAUTIOUS GO / NO GO recommendation with your confidence level (high/medium/low).

15. The Meeting Strategist

I have a meeting about [TOPIC] with [WHO — their role, relationship, what they care about].

My goal for this meeting: [WHAT YOU WANT TO ACHIEVE]

Prepare:

1. Opening statement (2 sentences — sets the right frame for the conversation)

2. 3 key points I must communicate (in priority order)

3. 3 questions I should ask (ordered from most to least important)

4. 3 likely objections and how to respond to each

5. My ideal closing statement (summarizes agreement and next steps)

6. Walk-away point: what is the minimum acceptable outcome?

16. The Pricing Strategist

Help me price [PRODUCT/SERVICE].

Context:

• What it does: [DESCRIPTION]
• Who it is for: [TARGET CUSTOMER]
• What it costs me to deliver: [YOUR COSTS]
• Competitor pricing: [WHAT ALTERNATIVES CHARGE, if known]
• Value delivered: [WHAT THE CUSTOMER GETS — time saved, money earned, problems solved]

Design a pricing structure:

1. Three tiers (entry, core, premium) with names that reflect value, not size

2. What is included in each tier and WHY each boundary exists

3. The psychology behind each price point

4. Which tier most customers should land on and how to guide them there

5. One-time vs. recurring analysis — which model fits better and why

Show the pricing in a formatted comparison table.

17. The Competitive Teardown

Perform a competitive teardown of [COMPETITOR NAME/URL].

Analyze:

1. POSITIONING: What is their core message? Who are they targeting? What emotion are they selling?

2. PRODUCT: What do they actually offer? What is the core feature vs. nice-to-haves?

3. PRICING: How do they charge? What does each tier include? Where is the profit margin?

4. CONTENT: What topics do they publish about? How often? What format performs best?

5. WEAKNESS: Where are they vulnerable? What do their customers complain about? What are they not doing?

End with: "If I were competing directly with [COMPETITOR], the 3 things I would do differently are..."

18. The OKR Builder

Help me create OKRs for [TEAM/INDIVIDUAL/COMPANY] for [TIME PERIOD].

Context: [CURRENT SITUATION — where we are, where we want to go, what resources we have]

For each Objective (suggest 3):

• The Objective: ambitious but achievable, qualitative, inspiring
• 3-4 Key Results: specific, measurable, time-bound
• For each Key Result: the current baseline, the target, and how you would measure it
• A confidence level (1-10) that this Key Result is achievable in the timeframe

Flag any Key Results that might conflict with each other.

19. The Risk Assessor

I am about to [DESCRIBE THE INITIATIVE/DECISION/PROJECT].

Perform a risk assessment:

1. List the 7 most likely risks (things that could go wrong)

2. For each risk:

• Probability: High / Medium / Low
• Impact if it occurs: High / Medium / Low
• Early warning sign (how would I detect this risk materializing?)
• Mitigation strategy (what would I do to prevent it?)
• Contingency plan (what would I do if it happens anyway?)

3. Plot all risks on a 2x2 matrix (probability vs. impact)

4. Identify the top 3 risks I should actively monitor

Be pessimistic. I want to hear about risks I have not considered, not reassurance that everything will be fine.

20. The Retrospective Facilitator

Facilitate a retrospective for this project/period: [DESCRIBE WHAT HAPPENED]

Structure:

1. WHAT WENT WELL (identify 5 specific things that worked, with evidence)

2. WHAT WENT WRONG (identify 5 specific things that did not work, with root causes)

3. WHAT WE LEARNED (3 lessons that will change how we work going forward)

4. WHAT WE WILL DO DIFFERENTLY (3 specific, actionable changes — not vague intentions)

5. WHAT WE WILL STOP DOING (2 things we should deliberately stop)

Rules:

• Be specific. "Communication was bad" is useless. "The product team was not informed about the pricing change until 2 days before launch, causing a scramble to update marketing materials" is useful.
• For every problem identified, include a specific preventive action.

Technical and Development (21 to 28)

21. The Architecture Advisor

I want to build [DESCRIBE THE SYSTEM].

Requirements:

• [REQUIREMENT 1]
• [REQUIREMENT 2]
• [REQUIREMENT 3]
• Expected scale: [USERS/DATA VOLUME]
• Budget constraints: [ANY LIMITATIONS]

Propose 2 architectural approaches. For each:

1. Component diagram (described in text — list every service/module and how they connect)

2. Technology choices with reasoning for each

3. Pros and cons (be honest about tradeoffs)

4. Estimated complexity: Simple / Moderate / Complex

5. The #1 thing that could go wrong with this approach

Recommend one approach. Explain why. Then give me the first 5 implementation steps in order.

22. The Code Reviewer

Review this code:

<code> [PASTE CODE] </code>

Check for:

1. SECURITY: Injection vulnerabilities, exposed secrets, XSS, insecure data handling

2. LOGIC: Edge cases not handled, incorrect conditional logic, off-by-one errors

3. PERFORMANCE: N+1 queries, unnecessary computations, missing caching opportunities

4. READABILITY: Unclear naming, missing comments on complex logic, overly nested code

5. BEST PRACTICES: Violations of language conventions, missing error handling, unused imports

For each issue found:

• Severity: Critical / High / Medium / Low
• Exact location (line or function name)
• Why it is a problem (not just what is wrong, but what could happen)
• The fix (show corrected code)

If the code is clean, say so. Do not invent issues to seem thorough.

23. The Debug Diagnostician

I am getting this error: [PASTE COMPLETE ERROR MESSAGE AND STACK TRACE]

Context: [WHAT THE CODE IS SUPPOSED TO DO]

1. Do NOT jump to a fix immediately

2. First: explain what this error message means in plain English

3. Second: list the 3 most likely root causes in order of probability

4. Third: for each potential cause, explain what evidence would confirm it

5. Fourth: once the root cause is identified, show the fix

6. Fifth: explain what would prevent this type of bug in the future

[PASTE RELEVANT CODE]

24. The API Designer

Design a REST API for [DESCRIBE THE SYSTEM/FEATURE].

For each endpoint:

• Method and path (following REST conventions)
• Request body schema (with required/optional fields)
• Response schema (success and error cases)
• Authentication requirements
• Rate limiting recommendation

Also include:

• Error response format (consistent across all endpoints)
• Pagination approach for list endpoints
• Versioning strategy
• 3 potential security concerns and how to address each

Present as a formatted API reference document.

25. The Database Schema Designer

Design a database schema for [DESCRIBE THE APPLICATION].

Requirements:

• [LIST KEY ENTITIES AND RELATIONSHIPS]
• Expected scale: [DATA VOLUME AND GROWTH RATE]

For each table:

• Columns with types, constraints, and descriptions
• Primary key and indexes
• Foreign key relationships

Also provide:

• An entity relationship description (how tables connect)
• 3 common queries this schema must support efficiently
• Index recommendations for those queries
• One potential scaling concern and how to address it
• Migration strategy if requirements change later

26. The Test Case Generator

Generate comprehensive test cases for this function/feature:

<code_or_description> [PASTE CODE OR DESCRIBE THE FEATURE] </code_or_description>

Test categories:

1. HAPPY PATH: 3 tests for normal, expected usage

2. EDGE CASES: 5 tests for boundary conditions, empty inputs, maximum values

3. ERROR CASES: 3 tests for invalid inputs, missing data, system failures

4. SECURITY: 2 tests for injection attempts, unauthorized access

5. PERFORMANCE: 1 test for behavior under load or with large datasets

For each test:

• Test name (descriptive)
• Input
• Expected output
• Why this test matters

27. The Documentation Writer

Write developer documentation for this code/API/system:

<code_or_spec> [PASTE CODE OR SPECIFICATION] </code_or_spec>

Include:

1. Overview (what this does and why it exists — 2-3 sentences)

2. Quick Start (get up and running in under 5 minutes)

3. Core Concepts (explain the mental model, not just the API surface)

4. API Reference (every public function/endpoint with parameters, return values, and examples)

5. Common Patterns (3 typical usage patterns with code examples)

6. Troubleshooting (5 common issues and their solutions)

Write for a developer who is smart but has never seen this codebase before.

28. The Refactoring Planner

This code needs refactoring:

<code> [PASTE CODE] </code>

Analyze:

1. What are the top 3 code quality issues? (duplicated logic, mixed responsibilities, unnecessary complexity)

2. For each issue: explain WHY it is a problem, not just that it exists

3. Propose a refactoring plan with specific steps in order

4. For each step: show the before and after code

5. Verify that the refactored code maintains identical external behavior

6. Estimate the impact: how much does this improve maintainability, readability, and testability?

Do NOT change external behavior. Internal improvement only.

Productivity and Personal (29 to 35)

29. The Weekly Planner

Here are my goals for this quarter: [LIST THEM] Here is what I accomplished last week: [BRIEF SUMMARY] Here are my commitments this week: [MEETINGS, DEADLINES, OBLIGATIONS]

Create my weekly plan:

1. TOP 3 PRIORITIES (the things that matter most for my quarterly goals)

2. SCHEDULED (meetings and deadlines by day)

3. BUFFER TASKS (important but flexible)

4. DELIBERATELY SKIPPING (things I am choosing NOT to do this week and why)

The DELIBERATELY SKIPPING section is the most important. Saying no is how priorities stay priorities.

30. The Learning Accelerator

I want to learn [TOPIC/SKILL].

My current level: [BEGINNER/INTERMEDIATE/ADVANCED] Time available: [HOURS PER WEEK] Learning style: [PRACTICAL/THEORETICAL/MIXED] Goal: [WHAT I WANT TO BE ABLE TO DO AFTER LEARNING THIS]

Create a learning plan:

1. Prerequisites: what do I need to know first? (be honest if I am missing foundations)

2. Core concepts: the 5-7 key ideas I must understand, in the order I should learn them

3. Projects: for each concept, one hands-on project that teaches it through building

4. Resources: for each concept, the single best resource (not 10 options — ONE)

5. Milestones: how do I know I actually understand each concept? (specific test, not "feel comfortable with")

6. Timeline: realistic week-by-week plan given my available time

Do not pad the plan. If I can learn this in 3 weeks, do not stretch it to 8.

31. The Negotiation Prep

I am about to negotiate [WHAT] with [WHO].

Context: [RELEVANT BACKGROUND — relationship, history, power dynamics] My ideal outcome: [BEST CASE] My acceptable outcome: [MINIMUM I WILL ACCEPT] Their likely position: [WHAT THEY PROBABLY WANT]

Prepare:

1. My opening position and the reasoning behind it

2. 3 concessions I can offer (ordered from smallest to largest)

3. 3 things I should ask for in return for each concession

4. Their 3 most likely objections and my response to each

5. 2 creative options that give both sides more value (expand the pie)

6. My walk-away line and the exact words I would use to exit gracefully

32 — The Habit Designer

I want to build this habit: [DESCRIBE THE HABIT]

My current routine: [WHAT MY TYPICAL DAY LOOKS LIKE] Past attempts: [WHAT I HAVE TRIED BEFORE AND WHY IT FAILED]

Design a habit implementation plan:

1. The smallest possible version of this habit (2-minute starter version)

2. The trigger: what existing habit or event will I attach this to?

3. The environment design: what physical change makes the habit easier?

4. The reward: what immediate positive feedback reinforces the habit?

5. The tracking method: how do I measure consistency?

6. The failure protocol: what do I do when I miss a day? (because I will)

7. The progression: how does the 2-minute version grow over 4 weeks?

Be realistic. I would rather build a tiny habit that sticks than design a perfect routine I abandon in a week.

Data and Research (33 to 37)

33. The Data Interpreter

Analyze this data:

<data> [PASTE DATA — CSV, table, numbers, survey results, etc.] </data>

Provide:

1. Summary statistics (key numbers at a glance)

2. The 3 most important patterns or trends

3. 2 surprising findings that are not immediately obvious

4. 1 potentially misleading aspect of this data (what could be misinterpreted?)

5. 3 questions this data raises that would require additional data to answer

Audience: [WHO WILL READ THIS ANALYSIS AND THEIR TECHNICAL LEVEL] Present findings in plain English first, then include the supporting numbers.

34. The Survey Analyzer

Analyze these survey results:

<survey_data> [PASTE SURVEY RESPONSES] </survey_data>

Provide:

1. Key demographics/segments in the respondent pool

2. Top 5 findings ranked by significance

3. Areas of consensus (where respondents strongly agree)

4. Areas of division (where opinions are split)

5. Surprising findings that contradict common assumptions

6. Actionable recommendations based on the data (3 specific things to do)

7. Limitations of this data (sample size, bias, what we cannot conclude)

35. The Research Synthesizer

I have gathered research from multiple sources on [TOPIC]:

<source_1>[PASTE OR SUMMARIZE]</source_1> <source_2>[PASTE OR SUMMARIZE]</source_2> <source_3>[PASTE OR SUMMARIZE]</source_3>

Synthesize:

1. Key themes across all sources (what do they agree on?)

2. Contradictions (where do sources disagree? who is more credible and why?)

3. Gaps (what questions remain unanswered?)

4. The 3 most important conclusions I can confidently draw

5. What I should research next to strengthen my understanding

Do not just summarize each source separately. I want genuine SYNTHESIS — connections and patterns across sources that are not obvious from reading them individually.

Communication (36 to 40)

36. The Difficult Conversation Prep

I need to have a difficult conversation about [TOPIC] with [WHO — role, relationship].

Situation: [WHAT HAPPENED AND WHY THIS CONVERSATION IS NECESSARY] My goal: [WHAT I WANT TO ACHIEVE — not just what I want to say] Their likely reaction: [HOW I EXPECT THEM TO RESPOND]

Prepare:

1. Opening statement (direct but empathetic — does not avoid the issue but does not attack the person)

2. The core message in one sentence (what MUST be communicated regardless of how the conversation goes)

3. How to handle defensiveness (specific responses to "that's not fair" / "you're wrong" / emotional reactions)

4. How to listen actively (what questions to ask to understand their perspective)

5. How to reach resolution (3 possible outcomes ranked from best to acceptable)

6. Closing statement (summarizes agreement, preserves relationship, defines next steps)

37. The Feedback Giver

I need to give feedback to [WHO — role, relationship] about [WHAT — specific behavior or work].

Context: [POSITIVE RELATIONSHIP? RECURRING ISSUE? FIRST TIME?]

Draft the feedback using this framework:

1. Observation (what specifically I observed — behavior, not character)

2. Impact (how it affected the team, the project, or the outcome — specific, not vague)

3. Expectation (what I would like to see going forward — specific and achievable)

4. Support (what I will do to help them succeed — not just demand change)

Tone: [SUPPORTIVE / DIRECT / SERIOUS]

Write it as spoken words, not an email. This is a conversation, not a memo.

38. The Presentation Outliner

Create a presentation outline for [TOPIC].

Audience: [WHO and WHAT THEY CARE ABOUT] Duration: [LENGTH] Goal: [WHAT SHOULD THE AUDIENCE DO/THINK/FEEL AFTER THIS PRESENTATION]

Structure:

1. Opening (30 seconds — hook that makes them put down their phones)

2. Problem (1-2 minutes — make them feel the pain of the current situation)

3. Solution (3-5 minutes — your framework/proposal/insight, broken into 3 clear points)

4. Evidence (2-3 minutes — specific examples, data, or case studies for each point)

5. Objection handling (1-2 minutes — address the biggest concern before they raise it)

6. Call to action (30 seconds — exactly what you want them to do next)

For each section: the key slide content, speaker notes, and one transition sentence to the next section.

39. The Apology Crafter

I need to apologize to [WHO] for [WHAT HAPPENED].

Context: [THE SITUATION — what I did, the impact, the relationship]

Draft an apology that:

1. Acknowledges specifically what I did wrong (not vague — the exact action)

2. Demonstrates I understand the impact on them (from THEIR perspective, not mine)

3. Takes full responsibility (no "but", no "if", no deflection)

4. Explains what I will do differently going forward (specific, actionable, verifiable)

5. Does NOT ask for forgiveness (that is their choice, not my request)

Tone: sincere and direct. Under 200 words. No over-explaining. No making it about my feelings.

Generate 2 versions: Version A: written (email/message) Version B: spoken (what I would say in person)

40. The Elevator Pitch Builder

Build an elevator pitch for [PRODUCT/SERVICE/IDEA].

Audience: [WHO I AM PITCHING TO] Context: [WHERE THIS PITCH WOULD HAPPEN — investor meeting, networking event, cold outreach] Time: [30 seconds / 60 seconds / 2 minutes]

Structure:

1. Hook (one sentence that makes them want to hear more)

2. Problem (one sentence describing the pain — use their language, not yours)

3. Solution (one sentence describing what I do — not how it works, what it DOES for them)

4. Proof (one sentence of credibility — traction, results, notable client)

5. Ask (one sentence — what I want them to do next)

Generate 3 versions at different energy levels: Version A: confident and bold Version B: conversational and warm Version C: data-driven and precise

Each version should feel natural when spoken aloud, not written.

How to Use This Collection

Step 1: Save this list. You will not memorize 40 prompts and you should not try.

Step 2: Find the 5 prompts most relevant to your work this week. Copy them. Customize the variables. Use them.

Step 3: When a prompt produces excellent results, save the customized version to a personal template file. Over time you build a library tailored to your exact work.

Step 4: Every week, try 2-3 prompts from this list that you have not used before. Expand your capability gradually.

The compounding effect: After one month of consistent use, your AI workflow operates at a level most people will not reach for years.

TL;DR

40 prompts. Tested on Claude, ChatGPT, and Gemini. Each one engineered for expert-level output.

Writing and content. Analysis and strategy. Technical development. Productivity. Data and research. Communication.

Stop typing vague prompts. Start using engineered ones.

This collection took months to test and refine

*Follow me *@eng_khairallah1 *for more tools, workflows, and systems. No fluff. Just what works.*

hope this was useful for you, Khairallah ❤️