200+ Best ChatGPT Prompts for Work, Writing, Coding & Creativity (2026)

Every high-performing prompt contains five essential elements. Miss one, and you'll get generic output that needs extensive editing. Include all five, and ChatGPT becomes your most productive team member.

Give ChatGPT a Role

Start by telling ChatGPT who they should be for this task. Are they a senior software engineer? A marketing copywriter? A friendly teacher? This isn't just theatrical—it fundamentally changes how the AI approaches your request. When you say "Act as a senior software engineer," ChatGPT draws from technical knowledge, uses industry terminology appropriately, and considers best practices. Say "Act as a friendly teacher" for the same topic, and suddenly the response becomes accessible, patient, and avoids intimidating jargon. The role sets the expertise level, tone, and perspective for everything that follows.

Define the Task Clearly

Vague tasks produce vague results. Instead of "help me with marketing," be explicit: "Write a blog post," "Debug this code," "Summarize this article," or "Generate 10 ideas." The clearer your task, the more focused ChatGPT's response. Think about how you'd assign work to a colleague—you wouldn't just say "do something with this." You'd specify exactly what deliverable you expect.

Provide Relevant Context

Context transforms generic responses into tailored solutions. Who's the audience? What's the situation? What constraints exist? Compare these two requests: "Explain databases" versus "Explain databases to a small business owner who's never coded but needs to understand why their developer is recommending PostgreSQL over Excel for customer management." The second provides context about audience knowledge level, their specific situation, and what decision they're trying to make. ChatGPT can now craft an explanation that actually helps.

Specify the Format

How should the output be structured? A 500-word article? A bulleted list? A code snippet with comments? A step-by-step tutorial? Without format specification, ChatGPT makes its best guess—which might not match what you need. Defining format ensures you get usable results without reformatting.

Set Clear Constraints

Constraints are boundaries that focus the output. "Avoid jargon," "Include 3 examples," "Use simple language," "No more than 10 items," "Professional tone," "Must be under 200 words"—these requirements prevent ChatGPT from wandering off-topic or including unwanted elements. Constraints are especially powerful for creative tasks where infinite possibilities could overwhelm useful output.

Let's look at real-world examples showing how slight changes in prompting create dramatically different results.

Why the Good Prompts Work

Notice the pattern? Every effective prompt follows the same structure we discussed earlier. The first example about email marketing transforms a three-word vague request into a comprehensive brief that specifies role (expert), task (blog post), context (B2B, specific audience level), format (numbered list, 400 words, examples required), and tone (professional but conversational). ChatGPT no longer has to guess what you want—it knows exactly what to deliver.

The debugging example shows why context matters so much in technical prompts. Saying "fix my code" is like calling tech support and hanging up before explaining the problem. You need to provide the code itself, describe what's happening (500 error on POST to /users), include the actual error message, and specify what kind of help you want (explanation plus corrected code with comments). Now ChatGPT can actually solve the problem instead of asking follow-up questions.

The business ideas prompt demonstrates the power of constraints. Without boundaries, ChatGPT generates random possibilities from "start a podcast" to "develop SaaS software" to "become a consultant"—technically business ideas, but useless without knowing your budget, skills, time, and timeline. By specifying exact constraints (under $500, solo part-time, targets remote workers, no technical skills, revenue within 60 days), every suggestion becomes immediately actionable for someone in that specific situation.

Here's a technique that consistently produces better results: ask ChatGPT to show its reasoning process. Instead of jumping straight to conclusions, telling ChatGPT to "think step-by-step" or "show your work" forces more thorough analysis and catches errors before they appear in the final output.

Consider a complex problem like improving website conversion rates. A simple prompt like "How do I improve my conversion rate?" gets generic advice you could find in any blog post: "Improve your headlines," "Add social proof," "Make CTA buttons more visible." Technically true, but not useful without knowing your specific situation.

Now try asking ChatGPT to reason through the problem: "Act as a data analyst. I need to increase website conversion rate from 2% to 3%. Show your step-by-step reasoning: (1) What data should I analyze first? (2) What are the most common causes of low conversion? (3) What are 5 high-impact experiments to test? (4) How should I prioritize them? Explain your reasoning for each step."

The difference is dramatic. Instead of generic advice, you get structured thinking: ChatGPT first identifies what metrics to examine (bounce rate, time on page, exit pages), then diagnoses common problems (unclear value proposition, slow load times, complicated checkout), then prioritizes solutions based on impact and ease of implementation, and finally explains the logic behind each recommendation. The chain-of-thought approach reveals the analytical process, making it easier to adapt the advice to your specific context and spot potential issues with suggested solutions.

Writing blog posts with ChatGPT is like having a research assistant, first-draft writer, and editor rolled into one—but only if you give clear direction. Here are prompts that transform generic AI writing into content that ranks and converts.

For SEO-optimized blog posts, specificity is everything. Rather than asking ChatGPT to "write about email marketing," you need to define the exact keyword target, audience, structure, and optimization goals. A prompt like "Act as an SEO content writer. Write a 1,200-word blog post titled '[TITLE]' targeting the keyword '[KEYWORD]'. Include: (1) compelling introduction with hook, (2) 5-7 H2 subheadings with keyword variations, (3) FAQ section with 5 questions, (4) conclusion with call-to-action. Use conversational tone, short paragraphs, and include one real-world example per section. Optimize for featured snippets" produces content that follows SEO best practices while remaining readable.

Listicles require a different approach. The formula that works: "Write a listicle: '15 [TOPIC] That [BENEFIT]'. For each item: (1) catchy subheading, (2) 50-word explanation, (3) one actionable tip. Target audience: [AUDIENCE]. Tone: [TONE]. Include intro (100 words) and conclusion (75 words) with CTA." This structure ensures consistency across all list items while maintaining the scannable format readers expect.

When creating how-to tutorials, remember that beginners need hand-holding. Use: "Create a step-by-step tutorial: 'How to [TASK] in [TIMEFRAME]'. Write for complete beginners. Include: (1) what they'll learn, (2) what they'll need, (3) 7-10 numbered steps with screenshot descriptions, (4) common mistakes section, (5) troubleshooting tips. 800-1,000 words, friendly tone." The key is being explicit about the skill level—"complete beginners" prevents ChatGPT from assuming prior knowledge.

Case studies need concrete details to feel authentic. Try: "Write a case study: 'How [COMPANY] Achieved [RESULT] Using [METHOD]'. Structure: (1) Background/Challenge (150 words), (2) Solution/Strategy (250 words), (3) Implementation (200 words), (4) Results with metrics (150 words), (5) Key Takeaways (100 words). Use specific numbers and quotes." Even if you're using placeholder company names, the structured format forces ChatGPT to create believable, data-driven narratives.

For comparison articles, provide the exact structure you want: "Create comparison post: '[OPTION A] vs [OPTION B]: Which Is Better in 2026?' Include: (1) overview of both, (2) side-by-side feature table, (3) pros/cons for each, (4) use cases (when to choose each), (5) pricing comparison, (6) final verdict. 1,000 words, objective tone." The side-by-side table is crucial—it gives readers the quick visual comparison they came for before diving into detailed analysis.

Social media requires a completely different prompting strategy than long-form content. Each platform has its own culture, format constraints, and engagement patterns. Here's how to prompt ChatGPT for each major platform.

LinkedIn is professional but increasingly conversational. The sweet spot is thought leadership that teaches without being preachy. Use: "Act as a LinkedIn influencer. Write a 200-word post about [TOPIC] for [INDUSTRY] professionals. Start with a surprising statistic or question. Share one personal insight or lesson learned. Include 3 bullet points with actionable takeaways. End with an engaging question to drive comments. Professional yet conversational tone. Add relevant hashtags." The "engaging question" at the end is critical—LinkedIn's algorithm heavily weights comment engagement.

Twitter threads let you explain complex topics in digestible chunks. The prompt that works: "Create a Twitter/X thread (8-10 tweets) explaining [COMPLEX TOPIC] in simple terms for beginners. Tweet 1: Hook with surprising fact. Tweets 2-8: One clear point per tweet with example. Final tweet: Summary with CTA. Keep each tweet under 280 characters. Use emojis strategically. Make it shareable." The character limit forces clarity—each tweet must convey one complete idea.

Instagram captions need to grab attention in the first line since users see only the beginning before "more." Try: "Write an Instagram caption for [IMAGE DESCRIPTION]. Target: [AUDIENCE]. Include: (1) attention-grabbing first line (under 125 characters), (2) storytelling middle (2-3 sentences), (3) call-to-action, (4) 15-20 relevant hashtags (mix of popular and niche). Conversational, authentic tone with 1-2 emojis." The hashtag mix is crucial—popular hashtags give initial reach while niche ones find your exact target audience.

Facebook ads have one job: stop the scroll and drive action. Use: "Create Facebook ad copy for [PRODUCT/SERVICE]. Target: [AUDIENCE] struggling with [PROBLEM]. Include: (1) headline (5 words, benefit-focused), (2) primary text (125 words max, problem-agitate-solve format), (3) description (2 sentences, overcome objection), (4) call-to-action button text. Persuasive but not salesy." The problem-agitate-solve format works because it mirrors the customer's mental journey: "I have this problem" → "It's worse than I thought" → "Here's the solution."

YouTube scripts require pacing and retention strategy. Try: "Write a 10-minute YouTube video script about [TOPIC]. Include: (1) hook (first 10 seconds), (2) intro with what viewers will learn, (3) main content (5-7 key points with examples), (4) engagement prompts (like, subscribe, comment), (5) outro with CTA. Conversational tone, natural transitions, timestamp markers every 2 minutes." The first 10 seconds determine whether viewers stay or leave—make them count.

11. Welcome Email Series:

"Create a 5-email welcome sequence for new subscribers to [BUSINESS]. Email 1: Welcome + set expectations. Email 2: Share origin story + build trust. Email 3: Showcase main product/service. Email 4: Address common objection. Email 5: Special offer + urgency. Each email: subject line, 200-word body, clear CTA. Friendly, personal tone."

12. Cold Outreach Email:

"Write cold email for [TARGET PERSONA] at [COMPANY TYPE]. Purpose: [GOAL]. Include: (1) subject line (curiosity-driven, under 50 chars), (2) personalized opening (reference their work), (3) value proposition (1-2 sentences), (4) social proof (one credible stat), (5) soft CTA (low-commitment ask). Total: 100-125 words. Professional, respectful tone."

13. Newsletter Content:

"Act as a newsletter writer. Create weekly newsletter for [AUDIENCE] about [TOPIC]. Include: (1) catchy subject line, (2) personal intro (50 words), (3) main article (300 words with subheadings), (4) 'Quick Tips' section (3 bullets), (5) curated links (3 resources with 1-sentence descriptions), (6) sign-off with next week's preview."

14. Re-engagement Campaign:

"Write re-engagement email for subscribers who haven't opened in 90+ days. Subject line ideas (3 options, under 50 chars). Body: (1) acknowledge absence (friendly, not guilt-trippy), (2) ask if they want to stay subscribed, (3) share what's new/improved, (4) special 'come back' incentive, (5) easy unsubscribe option. 150 words, genuine tone."

15. Product Launch Email:

"Create product launch email for [PRODUCT]. Include: (1) subject line with curiosity + urgency, (2) opening: tease the problem it solves, (3) introduce product with main benefit, (4) 3 key features (bullet points with benefits not features), (5) social proof (testimonial or stat), (6) limited-time offer details, (7) strong CTA button text. 250 words, exciting tone."

Debugging with ChatGPT is like pair programming with an experienced colleague who can spot issues you've been staring at for hours. But that colleague needs context to help effectively.

When you hit an error, resist the urge to just paste the error message and ask "what's wrong?" Instead, provide the complete picture: "Act as an expert [LANGUAGE] developer. This code produces [ERROR MESSAGE]: ```[PASTE CODE]```. Explain: (1) what's causing the error, (2) why it happens, (3) how to fix it. Provide corrected code with inline comments explaining changes. Also suggest best practices to prevent similar errors." The three-part explanation (what, why, how) gives you understanding, not just a fix you blindly copy-paste.

Code reviews are another area where ChatGPT excels with proper prompting. Use: "Review this [LANGUAGE] code for: (1) bugs/errors, (2) performance issues, (3) security vulnerabilities, (4) code style/readability, (5) best practices. Code: ```[PASTE CODE]```. For each issue found, explain problem, severity (high/medium/low), and provide improved version with explanation." The severity rating helps you prioritize fixes—tackle high-severity security issues before medium-severity style improvements.

Performance optimization requires analytical thinking. Try: "Act as a performance optimization expert. This [LANGUAGE] code works but is slow: ```[PASTE CODE]```. Analyze: (1) performance bottlenecks, (2) time complexity, (3) memory usage. Provide optimized version with: (1) explanation of improvements, (2) before/after performance comparison, (3) trade-offs if any." The trade-offs section is crucial—sometimes faster code is less readable or uses more memory.

For refactoring messy code: "Refactor this [LANGUAGE] code to be more maintainable and follow [FRAMEWORK] best practices: ```[PASTE CODE]```. Improve: (1) code organization, (2) naming conventions, (3) separation of concerns, (4) reusability. Explain each refactoring decision and why it's better." Good refactoring isn't just making code "prettier"—it's making future changes easier.

Security audits need systematic checking. Use: "Act as a security expert. Audit this code for vulnerabilities: ```[PASTE CODE]```. Check for: (1) SQL injection, (2) XSS attacks, (3) CSRF issues, (4) authentication flaws, (5) data exposure. For each vulnerability: explain risk, show exploit example, provide secure code fix with explanation." The exploit example helps you understand why the vulnerability matters, not just that it exists.

21. Build Full Feature:

"Act as a senior [LANGUAGE] developer. Build a [FEATURE] for [APP TYPE]. Requirements: [LIST REQUIREMENTS]. Include: (1) main implementation with error handling, (2) database schema if needed, (3) API endpoints, (4) basic tests, (5) usage examples. Follow [FRAMEWORK] conventions and include inline documentation."

22. API Integration:

"Create code to integrate [API NAME] API. Task: [WHAT TO DO WITH API]. Language: [LANGUAGE]. Include: (1) authentication setup, (2) API call functions with error handling, (3) response parsing, (4) rate limiting handling, (5) usage examples, (6) environment variable config. Add comments explaining each section."

23. Database Query:

"Write [SQL/MongoDB/etc.] query for: [DESCRIBE WHAT YOU NEED]. Database structure: [DESCRIBE TABLES/COLLECTIONS]. Optimize for performance. Include: (1) the query, (2) explanation of what it does, (3) indexes needed for performance, (4) example output, (5) alternative approaches if applicable."

24. Unit Tests:

"Generate comprehensive unit tests for this function using [TESTING FRAMEWORK]: ```[PASTE FUNCTION]```. Cover: (1) happy path, (2) edge cases, (3) error conditions, (4) boundary values, (5) null/undefined inputs. Include setup/teardown if needed. Aim for 90%+ code coverage. Add descriptive test names."

25. Regex Pattern:

"Create regex pattern to [DESCRIBE WHAT TO MATCH]. Language: [LANGUAGE]. Requirements: [CONSTRAINTS]. Provide: (1) the regex pattern, (2) explanation of each part, (3) 5 test cases (should match), (4) 5 test cases (should NOT match), (5) alternative approaches if regex isn't ideal."

26. Code Documentation:

"Generate professional documentation for this code: ```[PASTE CODE]```. Include: (1) overview of what it does, (2) function/class descriptions with parameters and return values, (3) usage examples, (4) dependencies/requirements, (5) error handling notes, (6) performance considerations. Format in Markdown for README.md."

27. Explain Complex Code:

"Act as a patient programming teacher. Explain this code to a beginner: ```[PASTE CODE]```. Break down: (1) overall purpose, (2) step-by-step walkthrough of what each part does, (3) why certain approaches were used, (4) what beginners often misunderstand, (5) simplified analogy. Avoid jargon or explain it."

28. Architecture Design:

"Design system architecture for [APP DESCRIPTION]. Requirements: [LIST REQUIREMENTS]. Include: (1) high-level architecture diagram (describe components), (2) technology stack recommendations with rationale, (3) data flow explanation, (4) scalability considerations, (5) security measures, (6) potential bottlenecks and solutions. Format as technical design document."

29. Algorithm Explanation:

"Explain [ALGORITHM NAME] algorithm like I'm a CS student. Include: (1) what problem it solves, (2) how it works step-by-step with example, (3) pseudocode, (4) time/space complexity analysis, (5) when to use vs alternatives, (6) real-world applications. Use simple language with visual descriptions."

30. Code Comparison:

"Compare these two approaches to [TASK]: Approach A: ```[CODE A]``` Approach B: ```[CODE B]```. Analyze: (1) performance (time/space complexity), (2) readability/maintainability, (3) scalability, (4) error handling, (5) edge cases coverage. Recommend which to use when and why."

31. SWOT Analysis:

"Conduct SWOT analysis for [COMPANY/PRODUCT]. Industry: [INDUSTRY]. Context: [PROVIDE BACKGROUND]. Create detailed analysis: (1) Strengths (5-7 internal advantages), (2) Weaknesses (5-7 internal limitations), (3) Opportunities (5-7 external chances), (4) Threats (5-7 external risks). For each point, provide specific example and strategic implication."

32. Competitor Analysis:

"Analyze competitor [COMPETITOR NAME] in [INDUSTRY]. Research areas: (1) target audience, (2) unique value proposition, (3) pricing strategy, (4) marketing channels, (5) strengths we can't match, (6) weaknesses we can exploit, (7) their likely next moves. Conclude with 3 strategic recommendations for us."

33. Go-to-Market Strategy:

"Create go-to-market strategy for [PRODUCT/SERVICE]. Target: [AUDIENCE]. Include: (1) positioning statement, (2) ideal customer profile, (3) key messaging framework, (4) marketing channel mix with budget allocation, (5) sales strategy, (6) success metrics, (7) 90-day launch timeline with milestones. Format as executive brief."

34. Pricing Strategy:

"Design pricing strategy for [PRODUCT/SERVICE]. Current situation: [DESCRIBE CONTEXT]. Analyze: (1) value-based pricing calculation, (2) competitor pricing landscape, (3) psychological pricing tactics, (4) tier structure (if applicable), (5) discount strategy, (6) testing approach. Recommend final pricing with rationale."

35. Business Model Canvas:

"Create Business Model Canvas for [BUSINESS IDEA]. Include detailed breakdown of: (1) Customer Segments, (2) Value Propositions, (3) Channels, (4) Customer Relationships, (5) Revenue Streams, (6) Key Resources, (7) Key Activities, (8) Key Partners, (9) Cost Structure. For each section, provide 3-5 specific, actionable points."

36. Marketing Campaign:

"Plan marketing campaign for [PRODUCT/SERVICE]. Goal: [SPECIFIC GOAL]. Budget: [BUDGET]. Timeline: [TIMEFRAME]. Include: (1) campaign concept/theme, (2) target audience definition, (3) key messages, (4) channel strategy (organic + paid), (5) content calendar (week-by-week), (6) KPIs to track, (7) budget breakdown by channel."

37. Customer Persona:

"Create detailed customer persona for [PRODUCT/SERVICE]. Include: (1) demographics (age, location, income, job title), (2) psychographics (goals, values, fears), (3) behavior patterns (where they hang out online, how they research), (4) pain points (3 biggest problems), (5) buying triggers, (6) objections to purchase, (7) preferred communication style. Give persona a name and write in narrative format."

38. Sales Script:

"Write sales call script for [PRODUCT/SERVICE]. Target: [BUYER PERSONA]. Call purpose: [DISCOVERY/DEMO/CLOSE]. Include: (1) opening (build rapport, 30 seconds), (2) qualifying questions (5-7 questions), (3) pain point discussion, (4) solution presentation (3 key benefits), (5) handling objections (top 3 objections with responses), (6) closing techniques (3 options), (7) next steps. Natural, conversational tone."

39. Content Marketing Plan:

"Create 90-day content marketing plan for [BUSINESS]. Goals: [GOALS]. Audience: [AUDIENCE]. Include: (1) content pillars (3-5 themes), (2) content types and frequency, (3) keyword strategy (10 target keywords), (4) editorial calendar (week-by-week topics), (5) distribution channels, (6) promotion tactics, (7) success metrics and tracking."

40. Landing Page Copy:

"Write high-converting landing page copy for [PRODUCT/SERVICE]. Target: [AUDIENCE] who [PROBLEM]. Include: (1) headline (clear benefit, under 10 words), (2) subheadline (expand on benefit, under 20 words), (3) hero section (150 words, problem-agitate-solve), (4) features section (5 features as benefits), (5) social proof (3 testimonial prompts), (6) FAQ (5 questions addressing objections), (7) CTA (button text + surrounding copy). Persuasive, benefit-focused tone."

41. Meeting Agenda:

"Create meeting agenda for [MEETING PURPOSE]. Attendees: [ROLES]. Duration: [TIME]. Include: (1) meeting objective (1 sentence), (2) desired outcomes, (3) agenda items with time allocations, (4) pre-work required, (5) discussion questions for key topics, (6) decision points, (7) action items template. Format for easy sharing."

42. Project Plan:

"Develop project plan for [PROJECT]. Timeline: [DURATION]. Team: [TEAM SIZE/ROLES]. Include: (1) project objectives and success criteria, (2) key deliverables, (3) phases breakdown with milestones, (4) task list with dependencies, (5) resource allocation, (6) risk assessment with mitigation plans, (7) communication plan. Format as Gantt-friendly structure."

43. Performance Review:

"Write performance review for [ROLE] team member. Review period: [TIMEFRAME]. Include: (1) accomplishments (3-5 specific achievements with metrics), (2) areas of strength (3 strengths with examples), (3) areas for development (2-3 growth opportunities), (4) goals for next period (3-5 SMART goals), (5) development plan, (6) overall rating justification. Constructive, balanced tone."

44. Email Summary:

"Summarize this long email thread: [PASTE EMAIL THREAD]. Extract: (1) main issue/question, (2) key points from each participant, (3) decisions made, (4) action items (who, what, when), (5) open questions remaining, (6) recommended next steps. Format as executive summary under 200 words."

45. Process Documentation:

"Document standard operating procedure for [PROCESS]. Audience: [WHO WILL USE IT]. Include: (1) process overview and purpose, (2) when to use this process, (3) step-by-step instructions (numbered, detailed), (4) decision points with flowchart logic, (5) common mistakes to avoid, (6) tools/resources needed, (7) troubleshooting guide. Clear, scannable format."

46. Explain Concept:

"Act as an expert teacher. Explain [CONCEPT] to someone with [KNOWLEDGE LEVEL]. Include: (1) simple definition (one sentence), (2) detailed explanation with real-world analogy, (3) why it matters, (4) common misconceptions, (5) practical example, (6) how to remember it, (7) related concepts to explore next. Use simple language, avoid jargon."

47. Study Guide:

"Create comprehensive study guide for [TOPIC]. Exam date: [DATE]. Include: (1) key concepts outline with hierarchy, (2) must-know definitions (10-15 terms), (3) important formulas/rules, (4) practice questions (10 questions with difficulty levels), (5) study schedule (break into daily chunks), (6) memorization tips, (7) common exam traps. Format for easy review."

48. Practice Questions:

"Generate 20 practice questions for [TOPIC] at [DIFFICULTY LEVEL]. Include: (1) 10 multiple choice (with 4 options each), (2) 5 short answer, (3) 5 scenario-based. Provide: questions, correct answers, detailed explanations for each answer, and difficulty rating. Cover full breadth of topic."

49. Flashcards:

"Create 30 flashcards for [SUBJECT]. Format: Question on one side, answer on other. Cover: (1) key definitions, (2) important facts/dates, (3) formulas/equations, (4) cause-and-effect relationships, (5) comparisons. Make questions specific and answers concise. Group by subtopic. Include memory aids for difficult ones."

50. Essay Outline:

"Create detailed essay outline for topic: [ESSAY PROMPT]. Word count: [COUNT]. Include: (1) thesis statement (clear argument), (2) introduction strategy (hook + context), (3) body paragraphs (3-5 sections with main point, supporting evidence, analysis for each), (4) counterargument section, (5) conclusion approach, (6) suggested sources to research. Academic tone."

51. Research Summary:

"Summarize this research: [PASTE ARTICLE/STUDY]. Extract: (1) research question/hypothesis, (2) methodology, (3) key findings (3-5 main results), (4) significance/implications, (5) limitations, (6) how it compares to existing research, (7) future research suggestions. Target audience: [AUDIENCE]. 300-400 words, accessible language."

52. Literature Review:

"Organize literature review on [TOPIC]. I have [NUMBER] sources. Create: (1) thematic categorization (group sources by theme), (2) chronological overview (evolution of thinking), (3) methodology comparison, (4) key findings synthesis, (5) gaps in research, (6) contradictions to explore, (7) structure for writing review. Format as annotated outline."

53. Data Analysis:

"Analyze this data and extract insights: [PASTE DATA OR DESCRIBE DATASET]. Include: (1) data overview (what's included), (2) notable patterns/trends, (3) statistical summary (mean, median, outliers), (4) correlations identified, (5) surprising findings, (6) limitations of data, (7) actionable recommendations based on findings. Present with clear headings."

54. Fact-Check:

"Fact-check this claim: [PASTE CLAIM]. Analyze: (1) what's being claimed exactly, (2) source credibility, (3) supporting evidence quality, (4) contradicting evidence, (5) expert consensus on topic, (6) context that matters, (7) verdict (true/false/partially true/misleading) with confidence level and explanation."

55. Research Questions:

"Generate research questions for [TOPIC]. Area: [FIELD]. Include: (1) 3 broad exploratory questions, (2) 5 specific testable hypotheses, (3) 3 questions addressing gaps in current research, (4) 2 controversial/debate-generating questions. For each, note: difficulty level, required methodology, and why it matters."

56. Idea Generation:

"Brainstorm 20 unique ideas for [PROJECT TYPE] about [TOPIC]. Target audience: [AUDIENCE]. Constraints: [BUDGET/TIME/RESOURCES]. For each idea: (1) catchy title, (2) one-sentence description, (3) unique angle that makes it different, (4) estimated effort (low/medium/high). Prioritize ideas that are both creative and practical."

57. Creative Angles:

"I'm creating content about [TOPIC]. Generate 15 unique angles/perspectives that haven't been overused. For each angle: (1) the unique perspective, (2) why it's interesting, (3) target sub-audience, (4) headline example. Avoid obvious approaches. Think outside the box."

58. Naming Ideas:

"Generate 30 name ideas for [BUSINESS/PRODUCT/PROJECT]. Category: [CATEGORY]. Brand personality: [ADJECTIVES]. Requirements: (1) memorable, (2) easy to spell/pronounce, (3) .com domain likely available, (4) no negative connotations. Group into categories: descriptive, invented, metaphorical, acronyms, combinations. Note favorites."

59. Tagline Options:

"Create 20 tagline options for [BRAND/PRODUCT]. Key message: [WHAT TO COMMUNICATE]. Brand voice: [TONE]. Include: (1) 10 short taglines (3-5 words), (2) 10 longer taglines (6-10 words). For each, note: emotional appeal (rational/emotional), memorability score (1-10), and which audience segment it targets."

60. Story Ideas:

"Generate 15 story ideas in [GENRE]. Themes to explore: [THEMES]. For each idea: (1) logline (one-sentence hook), (2) main character description, (3) central conflict, (4) unique twist, (5) emotional core. Avoid clichés. Make each one I can't stop thinking about."

61. Character Development:

"Create detailed character profile for [CHARACTER TYPE] in [STORY CONTEXT]. Include: (1) basic details (name, age, appearance), (2) personality (5 traits with examples), (3) backstory (formative events), (4) motivations and fears, (5) character arc (how they change), (6) relationships with other characters, (7) unique quirks/habits, (8) dialogue style. Make them three-dimensional."

62. Plot Outline:

"Outline story plot for [GENRE] story. Premise: [ONE-SENTENCE PREMISE]. Structure using three-act structure: Act 1 (Setup - 25%): intro world, character, inciting incident. Act 2 (Confrontation - 50%): rising action, midpoint twist, obstacles, all-is-lost moment. Act 3 (Resolution - 25%): climax, resolution, new normal. Include 10-12 major plot points with emotional beats."

63. Dialogue Writing:

"Write dialogue scene between [CHARACTER A] and [CHARACTER B]. Context: [SITUATION]. Subtext: [WHAT'S REALLY HAPPENING]. Length: 15-20 exchanges. Requirements: (1) reveal character personalities, (2) advance plot, (3) include conflict/tension, (4) use subtext (characters don't say exactly what they mean), (5) natural speech patterns. Add brief action beats."

64. World-Building:

"Build fictional world for [GENRE] story. Era: [TIME PERIOD OR SETTING]. Include: (1) geography (major locations, climate), (2) society structure (government, classes, culture), (3) economy (how people make living), (4) technology level, (5) magic/special rules (if applicable), (6) conflicts/tensions in world, (7) daily life details. Make it feel lived-in and consistent."

65. Story Opening:

"Write compelling story opening (500 words) for [GENRE] story. Requirements: (1) hook reader immediately, (2) introduce protagonist through action, (3) establish tone and voice, (4) hint at larger conflict, (5) create vivid setting, (6) end with question or tension. Show don't tell. First line must be unforgettable."

What it is: Providing examples of desired output format before asking for new content.

Example:

"I need product descriptions following this format:

Example 1:

Product: Wireless Earbuds

Description: Crystal-clear sound meets all-day comfort. These wireless earbuds deliver premium audio quality with 8-hour battery life and instant Bluetooth pairing. Perfect for commutes, workouts, and conference calls.

Key Features: • Noise cancellation • Water-resistant • Touch controls

Example 2:

Product: Smart Coffee Maker

Description: Wake up to perfectly brewed coffee every morning. This programmable coffee maker connects to your phone, learns your preferences, and starts brewing before your alarm goes off. Never drink mediocre coffee again.

Key Features: • App-controlled • Thermal carafe • Auto-scheduling

Now create product description for: [YOUR PRODUCT] following the same format and tone."

Why it works: ChatGPT learns your exact style and structure from examples, producing consistent, on-brand output.

What it is: Building on ChatGPT responses with follow-up prompts for perfection.

Initial Prompt:

"Write LinkedIn post about time management for entrepreneurs. 200 words."

Refinement Prompts:

→ "Make it more actionable—add 3 specific tips"

→ "Change tone to be more conversational and less formal"

→ "Add a surprising statistic in the opening"

→ "End with a question that drives engagement"

→ "Reduce to 150 words without losing key points"

Why it works: Rather than writing perfect prompts, you refine iteratively like working with a real assistant.

What it is: Combining multiple expert roles for nuanced output.

Example:

"Act as a combination of: (1) technical SEO expert, (2) psychology researcher, (3) direct-response copywriter. Analyze this landing page and provide recommendations that: optimize for search engines, leverage psychological triggers, and increase conversion rates. For each suggestion, explain which role's perspective it comes from and why it matters."

Why it works: Merges multiple viewpoints for well-rounded, sophisticated analysis.

What it is: Adding creative constraints to force innovative thinking.

Example:

"Generate 10 blog post ideas about productivity. Constraints: (1) no mention of common apps like Notion or Todoist, (2) must include uncommon perspective, (3) must be actionable in under 10 minutes, (4) avoid clichés like 'morning routines' or 'inbox zero'. Force yourself to think differently."

Why it works: Constraints eliminate obvious answers, forcing ChatGPT to generate more creative, unique ideas.

What it is: Explicitly stating what you DON'T want to avoid unwanted output.

Example:

"Write LinkedIn post about career growth. DO NOT: use buzzwords like 'synergy' or 'leverage', mention hustle culture, be overly formal, exceed 150 words, use generic advice like 'network more'. DO: be specific, use personal anecdote, give one actionable tip, end with thought-provoking question."

Why it works: Eliminates common ChatGPT patterns you dislike, producing more tailored output.

Picture this: you're frustrated with your marketing results, so you ask ChatGPT "Tell me about marketing." Five seconds later, you get a 500-word encyclopedia entry covering everything from the 4 Ps of Marketing to the history of advertising to modern digital strategies. Technically informative, practically useless for solving your actual problem.

The issue isn't that ChatGPT gave a bad answer—it answered the vague question you asked. You needed specific, actionable advice about your situation, but you didn't communicate that. It's like going to a doctor and saying "I feel bad" without describing symptoms, duration, or what you've tried.

Notice how the specific versions communicate exactly what you need, who it's for, what format you want, and what level of detail to provide. ChatGPT no longer has to guess your intent—it knows exactly what deliverable you expect.

❌ Bad: "Write a blog post about AI"

Problem: ChatGPT doesn't know your audience, purpose, or what angle to take.

✅ Fix: Provide context about audience, purpose, and desired outcome.

"Write blog post about AI for small business owners (non-technical, budget-conscious) explaining how AI tools can automate customer service without replacing human staff. Goal: reduce fear and encourage adoption. 800 words, conversational tone."

❌ Bad: Using whatever ChatGPT generates first without refinement

Problem: First drafts are rarely perfect; you miss opportunity for improvement.

✅ Fix: Use follow-up prompts to refine:

→ "Make this more concise"

→ "Add specific examples"

→ "Change tone to be more [formal/casual/urgent]"

→ "Rewrite opening to hook reader better"

→ "Remove jargon and simplify for beginners"

❌ Bad: "Give me information about project management"

Problem: You get walls of text when you needed a checklist, table, or bullet points.

✅ Fix: Specify exact format needed.

"Create project management checklist for software launches. Format as: Category headers, checkbox items under each, brief explanation for complex items. Categories: Pre-Launch, Launch Day, Post-Launch. 30-40 items total."

❌ Bad: Assuming all ChatGPT outputs are factually accurate

Problem: ChatGPT can confidently state incorrect information (hallucination).

✅ Fix: Verify facts, especially:

• Statistics and data points

• Historical events and dates

• Technical specifications

• Legal or medical information

• Current events (training data has cutoff)

Use ChatGPT for structure, ideas, and drafts—then fact-check critical details.

Blog Post:

"Write [WORD COUNT]-word blog post titled '[TITLE]' for [TARGET AUDIENCE]. Include [NUMBER] [H2/H3] subheadings. Tone: [TONE]. Cover: [3-5 KEY POINTS]. End with [CTA TYPE]."

Social Media:

"Create [PLATFORM] post about [TOPIC] for [AUDIENCE]. Length: [CHARACTER/WORD COUNT]. Include: [HOOK TYPE], [KEY MESSAGE], [CTA]. Tone: [TONE]. Add [EMOJI/HASHTAG REQUIREMENTS]."

Email:

"Write [EMAIL TYPE] email for [AUDIENCE]. Purpose: [GOAL]. Include: subject line, [WORD COUNT]-word body, CTA. Tone: [TONE]. Address: [PAIN POINT/OBJECTION]."

Video Script:

"Create [LENGTH]-minute video script about [TOPIC]. Target: [AUDIENCE]. Structure: [INTRO/BODY/OUTRO REQUIREMENTS]. Include: [HOOKS/TRANSITIONS/CTA DETAILS]."

Newsletter:

"Write [FREQUENCY] newsletter for [AUDIENCE]. Include: [SECTIONS]. Word count: [COUNT]. Featured topic: [MAIN TOPIC]. Additional: [SECONDARY CONTENT TYPES]."

Strategy Document:

"Create [STRATEGY TYPE] for [PRODUCT/SERVICE]. Context: [SITUATION]. Include: [SECTIONS NEEDED]. Format: [EXECUTIVE BRIEF/DETAILED PLAN/PRESENTATION]. Timeline: [PERIOD]."

Analysis:

"Analyze [SUBJECT] from [PERSPECTIVE]. Focus on: [SPECIFIC AREAS]. Provide: [DELIVERABLES]. Depth: [HIGH-LEVEL/DETAILED]. Consider: [CONSTRAINTS/FACTORS]."

Plan:

"Develop [PLAN TYPE] for [GOAL]. Duration: [TIMEFRAME]. Include: [MILESTONES/RESOURCES/RISKS]. Format: [STRUCTURE]. Success metrics: [KPIS]."

Competitive Research:

"Research [COMPETITOR/MARKET]. Focus: [AREAS]. Deliverables: [WHAT TO PRODUCE]. Sources: [WHERE TO LOOK]. Conclude with: [RECOMMENDATIONS/INSIGHTS]."

Presentation:

"Create [PRESENTATION TYPE] on [TOPIC]. Audience: [WHO]. Duration: [TIME]. Slides: [NUMBER]. Key message: [MAIN POINT]. Include: [REQUIRED ELEMENTS]."

Explanation:

"Explain [CONCEPT] to [KNOWLEDGE LEVEL]. Include: [DEFINITION/EXAMPLES/APPLICATIONS]. Use: [ANALOGIES/VISUALS/SIMPLE LANGUAGE]. Address: [COMMON CONFUSION POINTS]."

Summary:

"Summarize [SOURCE TYPE]: [PASTE OR DESCRIBE]. Extract: [WHAT TO PULL OUT]. Length: [WORD COUNT]. Format: [STRUCTURE]. Audience: [WHO WILL READ]."

Study Material:

"Create [STUDY MATERIAL TYPE] for [TOPIC]. Cover: [SCOPE]. Difficulty: [LEVEL]. Include: [COMPONENTS]. Format for: [USE CASE]."

Research:

"Research [TOPIC]. Questions to answer: [SPECIFIC QUESTIONS]. Sources: [WHERE TO LOOK]. Deliverable: [FORMAT]. Depth: [DETAIL LEVEL]."

Comparison:

"Compare [OPTION A] vs [OPTION B] for [USE CASE]. Criteria: [FACTORS TO COMPARE]. Include: [PROS/CONS/SCENARIOS]. Conclude: [RECOMMENDATION/NEUTRAL ANALYSIS]."

Code Generation:

"Write [LANGUAGE] code to [TASK]. Requirements: [SPECS]. Include: [ERROR HANDLING/COMMENTS/TESTS]. Follow: [CONVENTIONS/FRAMEWORK]. Optimize for: [PERFORMANCE/READABILITY]."

Debugging:

"Debug this [LANGUAGE] code: ```[CODE]```. Error: [MESSAGE]. Explain: [CAUSE/FIX/PREVENTION]. Provide: [CORRECTED CODE WITH COMMENTS]."

Documentation:

"Document this code: ```[CODE]```. Include: [OVERVIEW/PARAMS/RETURNS/EXAMPLES/NOTES]. Format: [MARKDOWN/DOCSTRINGS/README]. Audience: [WHO READS IT]."

Architecture:

"Design [SYSTEM TYPE] for [PURPOSE]. Requirements: [SPECS]. Include: [COMPONENTS/DATA FLOW/TECH STACK]. Consider: [SCALE/SECURITY/PERFORMANCE]."

Review:

"Review [CODE TYPE]: ```[CODE]```. Check: [ASPECTS]. Report: [ISSUES/SEVERITY/FIXES]. Format: [STRUCTURE]."