Battle-tested prompts for writing, coding, marketing, research, and productivity. No fluff. Just copy, paste, and get results.
Enter your email to unlock all 50 prompts. We'll also send you weekly AI tips.
No spam. Unsubscribe anytime. Privacy Policy
[topic]. Target audience: [audience]. Include a hook, 5-7 main sections with subpoints, and a conclusion with CTA. Make it actionable.
Pro tip: Replace placeholders, then ask for the full post section by section.
[paste text]
Pro tip: Works great for emails, docs, and landing page copy.
[purpose/offer]. Target: [audience]. Mix styles: curiosity, urgency, benefit-driven, question, and personalized. Keep under 50 characters.
Pro tip: Test 2-3 of these with your audience to find what resonates.
[topic]. Format: Hook tweet (max 280 chars), 5-7 value tweets, conclusion with CTA. Use short sentences, line breaks, and make each tweet standalone.
Pro tip: The hook is everything. If it doesn't grab attention, iterate on it first.
[product]. Include: headline, 3 key benefits (not features), social proof placeholder, and CTA. Tone: [professional/casual/luxury]. Max 150 words.
Pro tip: Focus on what the customer gets, not what the product does.
[insight/lesson/story]. Start with a hook line. Use short paragraphs (1-2 sentences). End with a question to encourage comments. Professional but human tone.
Pro tip: Personal stories + professional lessons = highest engagement.
[prospect type] offering [service/product]. Keep under 100 words. Personalize opening, show you understand their problem, provide proof, clear CTA. No salesy language.
Pro tip: The best cold emails sound like they were written just for that person.
[topic/experience]. Each hook should create curiosity and make the reader want to continue. Styles: in medias res, shocking stat, question, bold statement, scene-setting.
Pro tip: Test these hooks with friends. Pick the one that gets "wait, what happened?"
[topic]. Include the keyword [keyword] naturally. 150-160 characters. Include a benefit and implicit CTA. Make it click-worthy.
Pro tip: Check Google results for your keyword to see what competitors are doing.
Pro tip: Specific questions get better testimonials than "can you write a review?"
[language]. Code: [paste code]
Pro tip: Ask for specific focus areas like security, readability, or performance.
[error message]. Here's my code: [paste code]. Explain why this error occurs, provide the fix, and explain how to prevent it in the future.
Pro tip: Include the full stack trace if available.
[source language] to [target language]. Maintain the same functionality. Use idiomatic patterns for the target language. Add comments explaining key differences.
Pro tip: Great for porting projects or learning a new language.
[testing framework]. Cover: happy path, edge cases, error handling. Include descriptive test names. Function: [paste function]
Pro tip: Ask for additional tests for specific scenarios you're worried about.
[paste code]
Pro tip: Use this to understand unfamiliar codebases quickly.
[describe what you need]. Provide the pattern, explain each part, and give 3 example matches and 2 non-matches. Language context: [JS/Python/etc]
Pro tip: Regex varies by language. Always specify your environment.
[functionality]. Include: HTTP method, URL structure, request body schema, response schema, error responses, and example curl command. Framework: [Express/FastAPI/etc]
Pro tip: Ask for authentication and rate limiting patterns too.
[if known]. Target: faster execution/less memory. Explain the improvements and trade-offs. Code: [paste code]
Pro tip: Mention your scale (100 items vs 1M items) for relevant optimizations.
[application type]. Include tables, relationships, indexes, and constraints. Explain normalization decisions. Database: [PostgreSQL/MongoDB/etc]
Pro tip: Describe your query patterns for better index recommendations.
[bash/zsh/PowerShell] command to [task description]. Explain each part of the command. Include error handling if applicable. Provide safer alternatives if the command is destructive.
Pro tip: Always test destructive commands on a small sample first.
[product/service]. Target audience: [audience]. Main benefit: [benefit]. Format: What it is + who it's for + main benefit + differentiator.
Pro tip: Test with real customers. The one that makes them say "that's exactly what I need" wins.
[product] targeting [audience]. Include: headline (max 30 chars), description (max 90 chars), CTA. Styles: benefit-focused, problem-solution, social proof, urgency, curiosity.
Pro tip: Specify the platform (Google, Meta, LinkedIn) for format-appropriate copy.
[product]. Include: headline, subheadline, 3 benefit sections with icons, social proof section, FAQ (5 questions), and CTA. Conversion-focused, not feature-focused.
Pro tip: Include your best testimonial quote for the social proof section.
[competitor name/URL] vs our product [your product]. Compare: positioning, pricing, features, target audience, messaging. Identify gaps we can exploit and threats to address.
Pro tip: Provide competitor screenshots or copy for more accurate analysis.
[brand/product]. Platform: [platform]. Goal: [awareness/engagement/conversions]. Include post ideas, content types, and best posting times.
Pro tip: Mix educational, entertaining, and promotional content (70/20/10 rule).
[product/service]. Include: demographics, psychographics, pain points, goals, objections, where they hang out online, how they make decisions, and trigger phrases they use.
Pro tip: Base this on real customer interviews when possible.
[product/newsletter]. Goal: build trust and convert to [action]. Include subject lines and send timing. Tone: [professional/friendly/bold]
Pro tip: Email 1 should deliver immediate value, not pitch.
[customer success story]. Structure: challenge, solution, implementation, results (with numbers), key quote, and lessons learned. Make it skimmable.
Pro tip: Specific numbers (37% increase, not "significant increase") are more credible.
[product/service] and write rebuttals for each. Format: Objection, empathetic acknowledgment, reframe, evidence/proof, pivot to benefit.
Pro tip: Use these in sales calls, FAQ sections, and landing page copy.
[product/service]. Include: reward structure, messaging, email templates (invite + reward notification), and 3 share message templates for referrers.
Pro tip: Two-sided rewards (referrer + referee both get something) convert better.
[paste transcript]
Pro tip: Works great with auto-transcribed Zoom/Meet recordings.
[list tasks]. For each task, explain your reasoning. Then give me a recommended order.
Pro tip: Add deadlines and estimated effort for better prioritization.
[project description]. Estimate time for each task. Identify dependencies. Flag potential blockers. Suggest milestones for a [timeline] deadline.
Pro tip: Add buffer time for tasks you've never done before.
[options]. Criteria that matter to me: [criteria]. Create a weighted decision matrix. Score each option. Provide a recommendation with reasoning.
Pro tip: Rank your criteria by importance for more accurate weighting.
[complex topic] like I'm 10 years old. Use simple words, analogies, and examples from everyday life. Then give me the "adult version" with proper terminology I should learn.
Pro tip: Great for learning new domains quickly.
[challenge/goal]. Include a mix of safe, moderate, and wild ideas. Don't self-censor. After listing, highlight the 3 with highest potential and explain why.
Pro tip: The wild ideas often spark the best realistic solutions.
[process]. Include: purpose, scope, step-by-step instructions, decision points, common mistakes to avoid, and quality checks. Format for easy following.
Pro tip: Have someone unfamiliar with the process try following it and note where they get stuck.
[project/work]. Be specific about what feedback I need. Make it easy to respond. Include context about constraints and goals. Keep it short.
Pro tip: Ask 2-3 specific questions instead of "what do you think?"
[skill]. Current level: [beginner/intermediate]. Daily time available: [X hours]. Include resources, milestones, and practical exercises.
Pro tip: Build in review days. Spaced repetition beats cramming.
[wins]. Challenges: [struggles]. Ask me 5 reflection questions, then help me set 3 priorities for next week.
Pro tip: Schedule this as a recurring Friday afternoon ritual.
[topic]. Cover: history, current state, key players, trends, controversies, and future outlook. Include sources I should explore for deeper learning.
Pro tip: Follow up with "What are the most common misconceptions about this?"
[option A] vs [option B] for [use case]. Create a comparison table with: features, pricing, pros, cons, best for, and red flags. End with a recommendation.
Pro tip: Specify what matters most to you for a tailored recommendation.
[paste content]
Pro tip: For long documents, process in chunks and ask for a meta-summary at the end.
[industry]. Identify: unmet needs, underserved segments, emerging opportunities, and problems people are paying to solve badly. Think like a startup founder.
Pro tip: Cross-reference with Reddit/Twitter complaints in that industry.
[thesis/opinion]. Play devil's advocate. Give me the strongest arguments against my position. What evidence would change my mind? What am I missing?
Pro tip: Use this before making big decisions or publishing hot takes.
[paste feedback]. Identify: top 5 themes, sentiment distribution, specific pain points mentioned, feature requests, and quotable praise for marketing.
Pro tip: Include star ratings if available for sentiment calibration.
[industry/field] for the next 2-3 years? For each trend: evidence it's real, who's leading, implications for [my context], and how to prepare.
Pro tip: Ask which trends are overhyped and which are underestimated.
[field] about [topic]. Generate 15 interview questions: 5 foundational, 5 deep-dive, 5 provocative/contrarian. Order from rapport-building to challenging.
Pro tip: Include follow-up probes for each question.
[claim]. Rate confidence: high/medium/low. Provide supporting and contradicting evidence. Note what additional information would be needed for certainty.
Pro tip: For recent events, verify with authoritative sources directly.
[topic]. Give me: 5 foundational concepts to master first, 3 seminal papers/books, 5 experts to follow, 3 counterintuitive insights, and a learning path for 4 weeks.
Pro tip: This is how you go from zero to competent in any field fast.