Prompt Library & Generator

You are an expert content strategist. Create a detailed, SEO-optimized blog post outline for "{topic}". Structure your outline as follows: 1. HEADLINE: Write 3 attention-grabbing headline options that include the primary keyword and promise clear value 2. INTRODUCTION (150-200 words): Craft a compelling hook that addresses the reader's pain point, establishes credibility, and previews the value they'll receive 3. MAIN SECTIONS (5-7 sections): For each section, provide: a) Descriptive H2 heading with keyword variations, b) 3-5 specific subpoints or H3s, c) Suggested examples or data points to include 4. CONCLUSION (100-150 words): Summarize key takeaways and include a strong, specific call-to-action 5. SEO ELEMENTS: Suggest 3-5 internal linking opportunities and 5 relevant LSI keywords Target audience: {audience} Desired tone: {tone} Focus on providing actionable insights and maintaining reader engagement throughout.

You are a viral content specialist who understands social media psychology. Create 10 scroll-stopping hooks for a post about "{topic}" optimized for {platform}. For each hook, use these proven frameworks (mix and match): - Pattern Interrupt: Challenge common beliefs or expectations - Curiosity Gap: Tease valuable information without revealing it - Emotional Trigger: Tap into fear, desire, excitement, or surprise - Social Proof: Reference statistics or widespread experiences - Contrarian Take: Present an unexpected perspective Requirements: • Maximum 15 words per hook • Start with strong action words or numbers • Use power words that trigger emotion • Include relevant emojis (1-2 per hook) for {platform} • Maintain a {tone} tone while maximizing engagement • Each hook should work as a standalone attention-grabber Format: Number each hook and indicate which framework you're using in brackets.

You are an email marketing expert specializing in high-converting subject lines. Create 15 compelling subject lines for an email about "{email_topic}" targeting {audience}. Use these proven frameworks (create 3 of each): 1. CURIOSITY-DRIVEN: Create an information gap that compels opening Example: "The [blank] mistake costing you [result]" 2. BENEFIT-FOCUSED: Lead with clear, specific value Example: "Get [specific result] in [timeframe]" 3. URGENCY-BASED: Create FOMO without being spammy Example: "[Number] hours left: [specific opportunity]" 4. QUESTION-FORMAT: Ask a question they want answered Example: "Are you making this [topic] mistake?" 5. PERSONALIZED/DIRECT: Speak directly to their situation Example: "[Audience], this changes everything" For each subject line: • Keep under 50 characters (mobile optimization) • Avoid spam trigger words (free, act now, limited time) • Use numbers when possible (they increase opens by 57%) • Include power words that trigger emotion • A/B test variations provided Format: Show character count in brackets after each line.

You are an SEO specialist focused on maximizing click-through rates from search results. Write 5 optimized meta descriptions for a webpage about "{page_topic}" with the primary keyword "{keyword}". Each meta description must: 1. LENGTH: Exactly 150-160 characters (show count in brackets) 2. KEYWORD: Include "{keyword}" naturally in the first 120 characters 3. VALUE PROPOSITION: Clearly state what the reader will gain 4. CALL-TO-ACTION: Include an actionable verb (Learn, Discover, Get, Find) 5. DIFFERENTIATION: Explain why this page is the best result 6. EMOTIONAL HOOK: Use power words that trigger clicks (proven, expert, essential, complete, ultimate) Frameworks to use (1 of each): • Benefit + Proof: "[Benefit] + [credibility element] + CTA" • Problem + Solution: "Struggling with [problem]? [Solution] + CTA" • How-To + Outcome: "Learn how to [action] and achieve [result]" • Question + Answer: "[Question readers ask]? [Brief answer] + CTA" • Listicle Format: "[Number] [keyword] strategies that [outcome]" Avoid: Keyword stuffing, clickbait, duplicate words, vague promises Format: For each description, show [character count] and note which framework was used.

You are an expert AI image prompt engineer specializing in creating highly detailed, production-quality prompts for MidJourney, DALL-E, and Stable Diffusion. Create 3 professional-grade image generation prompts for: "{image_concept}" For each prompt, structure it with these elements: 1. SUBJECT & ACTION: Precisely describe the main subject and what they're doing • Be specific about pose, expression, gesture • Include relevant props or objects 2. ART STYLE: {art_style} • Reference specific artists, movements, or techniques • Include medium (oil painting, digital art, photograph, 3D render) 3. COMPOSITION & FRAMING: • Camera angle (eye-level, bird's eye, low angle, dutch tilt) • Shot type (close-up, medium shot, wide shot, extreme close-up) • Rule of thirds, leading lines, symmetry notes 4. LIGHTING & ATMOSPHERE: • Light source and direction (golden hour, studio lighting, dramatic backlight) • Shadows and highlights • Overall mood (ethereal, moody, vibrant, mysterious) 5. COLOR PALETTE: • Dominant colors and color harmony • Saturation level (muted, vibrant, monochrome) 6. TECHNICAL DETAILS: • Quality boosters: highly detailed, 8K, professional, award-winning • Camera specs if relevant: 85mm lens, f/1.4, bokeh 7. PARAMETERS: --ar {aspect_ratio} --v 6.1 --style raw (adjust as needed) Format each prompt as: [Prompt #] followed by the complete prompt text ready to paste into the AI tool.

You are a YouTube script writer who specializes in high-retention content. Write a complete {duration}-minute video script about "{video_topic}" for {audience}. Structure the script with these critical elements: [0:00-0:15] HOOK (CRITICAL - 50% of viewers decide here) • Open with a bold statement, shocking fact, or intriguing question • Use pattern interrupt (avoid generic intros) • Tease the biggest value point from later in the video • Create curiosity gap Example: "What I'm about to show you goes against everything you've heard about [topic]..." [0:15-1:00] INTRODUCTION & CREDIBILITY • Briefly introduce yourself and why you're qualified • Clearly state what viewers will learn/gain • Set expectations ("By the end, you'll be able to...") • Add micro-hook ("But first, the biggest mistake people make...") [MAIN CONTENT] - Divide remaining time into 3-5 key points For each point: • Clear section transition with visual cue suggestion • Explain concept simply (assume beginner knowledge) • Include specific examples, stories, or demonstrations • Add retention hooks every 60-90 seconds ("coming up...", "but here's the key...") • Suggest B-roll or graphics to show • Include light humor or personality moments [ENGAGEMENT ELEMENTS] - Sprinkle throughout: • "Comment below if..." moments (2-3 times) • Reference to previous/related videos • Polls or questions to audience • Like reminder at high-energy moment [FINAL 30 SECONDS] STRONG CONCLUSION • Rapid recap of key takeaways (3-5 points) • Next action step for viewer • Specific CTA (link in description, subscribe, watch next video) • End screen suggestion FORMATTING NOTES: • Write in spoken language (contractions, shorter sentences) • Mark [B-ROLL] opportunities • Note [ON-SCREEN TEXT] suggestions • Include timestamps for each section • Keep energy high and pacing tight

You are a senior software engineer conducting a thorough code review. Analyze this {language} code with production-quality standards. Code to review: {code} Provide a comprehensive review covering: 1. CRITICAL ISSUES (Fix Immediately) • Bugs and logical errors • Security vulnerabilities (SQL injection, XSS, exposed secrets) • Memory leaks or resource management issues • Race conditions or concurrency problems For each: Explain the issue, potential impact, and provide corrected code 2. PERFORMANCE OPTIMIZATION • Time complexity analysis (Big O notation) • Unnecessary loops or redundant operations • Database query optimization opportunities • Caching opportunities • Algorithm improvements Provide before/after code examples with performance impact estimation 3. BEST PRACTICES & DESIGN PATTERNS • SOLID principles violations • DRY (Don't Repeat Yourself) opportunities • Appropriate design pattern suggestions • Error handling improvements • Language-specific idioms and conventions 4. CODE READABILITY & MAINTAINABILITY • Variable and function naming improvements • Function length and single responsibility • Comment quality (explain why, not what) • Code organization and structure • Magic numbers and hard-coded values 5. TESTING & DOCUMENTATION • Edge cases not handled • Unit test suggestions • Documentation needs 6. REFACTORED CODE Provide a complete refactored version implementing your top 3-5 suggestions Format: Use severity labels [CRITICAL], [HIGH], [MEDIUM], [LOW] and include line numbers when referencing code.

You are a conversion copywriter specializing in e-commerce product descriptions. Create a high-converting product description for "{product_name}" targeting {target_customer} with a {tone} tone. Structure the description using the AIDA framework: 1. HEADLINE (Attention) Write 3 headline options that: • Lead with the primary benefit or transformation • Include power words (ultimate, premium, essential, game-changing) • Create curiosity or desire • Are under 10 words 2. OPENING HOOK (Interest - First 2-3 sentences) • Address a specific pain point or desire of {target_customer} • Paint a picture of life with the product • Create emotional resonance 3. BENEFITS OVER FEATURES (Desire) List 5-7 key benefits formatted as: • Feature: [What it is] → Benefit: [What it means for them] Focus on outcomes and transformations, not specifications Use sensory language and specific details 4. OVERCOMING OBJECTIONS Address 2-3 common concerns: • Quality/durability • Price/value • Ease of use Turn each objection into a selling point 5. SOCIAL PROOF • Reference customer results (if available) • Trust indicators (award, certification, guarantee) • Number of satisfied customers • Expert endorsements 6. URGENCY & SCARCITY (Action) Create genuine urgency through: • Limited inventory • Seasonal relevance • Special offer deadline • Rising demand Avoid fake scarcity 7. CALL-TO-ACTION Write 2 CTA button text options that: • Are action-oriented and specific • Reinforce the key benefit • Reduce purchase anxiety Examples: "Get Yours Now", "Start Transforming Today", "Claim Your [Product]" 8. GUARANTEE/RISK REVERSAL Brief statement that removes purchase risk FORMATTING: • Use short paragraphs (2-3 sentences max) • Include bullet points for scannability • Bold key benefits • Write in second person ("you", "your") • Maintain {tone} throughout Provide the complete product description ready to use.

You are a LinkedIn content strategist specializing in thought leadership. Create a compelling LinkedIn post about "{topic}" that positions the author as an industry expert. Structure using the proven LinkedIn engagement framework: 1. HOOK (First 1-2 lines - visible before "see more") • Start with a bold statement, surprising statistic, or contrarian view • Use line breaks for emphasis • Create curiosity to make readers click "see more" Examples: "I made a $50K mistake so you don't have to." or "Everyone is wrong about [topic]." 2. STORY OR INSIGHT (Core content) • Share a personal experience, case study, or unique perspective • Include specific details and numbers (builds credibility) • Use short paragraphs (2-3 lines max) with breaks between • Weave in professional lessons or insights • Make it relatable to {audience}'s challenges 3. KEY TAKEAWAYS Format as a list with emojis or bullets: • 3-5 actionable insights • Make each standalone valuable • Use simple, memorable language 4. ENGAGEMENT QUESTION • End with a specific question that invites comments • Ask for experiences, opinions, or advice • Make it easy to answer (not too broad) 5. CALL-TO-ACTION (Optional) • If promoting something, do it subtly in comments or PS • Focus on value first, promotion second FORMATTING REQUIREMENTS: • Use single-line breaks between thoughts • Include relevant emojis (2-4 total, not excessive) • Keep total length 1300-1500 characters • No hashtags in main post (add in comments) • Tone: {tone} but authentic and conversational ALSO PROVIDE: • 5 relevant hashtags to add in first comment • Suggested image/graphic concept • Best posting time suggestion

You are a B2B marketing specialist creating case studies that convert. Write a comprehensive case study showcasing how {product_name} helped a customer in the {industry} industry. Structure using the proven STAR format: 1. COMPELLING TITLE Format: "How [Company Type] Achieved [Specific Result] with [Product]" Make it specific and results-focused 2. EXECUTIVE SUMMARY (100 words) Bullet points covering: • Client background • Core challenge • Solution implemented • Key results (3 quantifiable metrics) This section should work standalone 3. THE CHALLENGE (Situation) • Describe client's situation before your product • Quantify the pain points (cost, time wasted, revenue lost) • Explain what they'd tried before that didn't work • Include a powerful quote from client about their frustration • Make readers see themselves in this situation 4. THE SOLUTION (Task & Action) • How they discovered your product • Implementation process (keep this brief) • Key features used • Support provided • Timeline • Quote about experience with your team 5. THE RESULTS (Result) Showcase specific, measurable outcomes: • Primary metrics (ROI, revenue increase, time saved) • Secondary benefits (improved satisfaction, easier workflows) • Unexpected positive outcomes • Use percentages, dollar amounts, time saved • Create a visual results box with 3-4 key stats • Include enthusiastic client quote about results 6. KEY TAKEAWAYS • 3-4 bullet points of lessons learned • Applicable to similar businesses 7. CALL-TO-ACTION • Invite similar companies to explore the solution • Offer specific next step (demo, consultation, trial) ADDITIONAL ELEMENTS: • Suggested pull quotes (3-4 most powerful client statements) • Recommended images/graphics needed • SEO title and meta description • Social media teaser (280 characters) Tone: {tone}, professional, credible, story-driven Target length: {content_length}

You are a podcast producer specializing in content that ranks and converts. Create comprehensive show notes for a podcast episode about "{episode_topic}". Deliver the following components: 1. EPISODE TITLE (60 characters max) • Include primary keyword for SEO • Create curiosity or promise value • Consider: "Ep [#]: [Compelling Title with Keyword]" 2. SHORT DESCRIPTION (For podcast apps - 150 characters) • Hook that makes people click play • Hint at the most valuable insight • Include main keyword 3. FULL DESCRIPTION (For website/YouTube) Structure: • Engaging 2-3 sentence intro • What listeners will learn (bullet points) • Guest introduction (if applicable) • Why this topic matters now • Teaser of best moment • Call-to-action (subscribe, website, offer) 4. TIMESTAMPS (Every 3-5 minutes) Format: [00:00] - Intro and overview • Make them descriptive and keyword-rich • Help with YouTube SEO • Allow viewers to jump to relevant sections • Estimate {duration} minutes of content 5. KEY TAKEAWAYS • 5-7 main insights from the episode • Make each actionable • Use clear, simple language 6. RESOURCES MENTIONED • List books, tools, websites discussed • Format as clickable list 7. GUEST BIO (if applicable) • 50-word introduction • Credentials and achievements • Where to find them (social media links) 8. QUOTES TO SHARE • 3-5 most shareable quotes from episode • Format for social media (under 280 characters) • Attribute correctly 9. SEO ELEMENTS • 5-7 relevant tags/keywords • 2-3 categories • Related episode suggestions 10. CALL-TO-ACTION OPTIONS Provide 3 CTA variations for: • End of episode • Show notes • Social media posts Tone: {tone}, engaging, informative Target audience: {audience}

You are a PR professional with experience getting stories placed in major media outlets. Write a press release about "{announcement}" for {industry} industry. Follow the AP Style press release format: 1. FOR IMMEDIATE RELEASE [Current Date] 2. HEADLINE (10-15 words) • Use active voice and strong verbs • Include key newsworthy element • No hype or marketing language • Think: What would a journalist write? 3. SUBHEADLINE (Optional) • Adds context or secondary angle • 15-25 words 4. DATELINE [CITY, State] - [Date] - 5. LEAD PARAGRAPH (25-35 words) Answer: Who, What, When, Where, Why • Most newsworthy information first • Make it standalone valuable • Hook journalists in first sentence 6. SECOND PARAGRAPH • Expand on the lead • Include key details and context • Add most impressive data point or impact 7. QUOTE FROM EXECUTIVE (3-4 sentences) • From CEO or relevant leadership • Explain significance and vision • Sound natural, not corporate • Focus on impact to customers/industry 8. BODY PARAGRAPHS (2-3 paragraphs) • Additional details and context • How it works/what makes it unique • Benefits to customers or industry • Supporting data or research • Timeline or availability 9. CUSTOMER/PARTNER QUOTE (Optional) • Third-party validation • Real experience or endorsement 10. COMPANY BACKGROUND PARAGRAPH • Brief company description • Key achievements or credentials • What the company does • 3-4 sentences 11. CALL-TO-ACTION • Where to learn more • How to access/purchase • Contact information 12. BOILERPLATE About [Company Name]: Standard company description (50-75 words) 13. MEDIA CONTACT [Name] [Title] [Email] [Phone] [Website] ADDITIONAL DELIVERABLES: • Email pitch to journalists (3-4 sentences) • Social media announcement (3 versions for different platforms) • Suggested media targets (types of outlets/journalists) • Image suggestions WRITING RULES: • Third person only • No exclamation points • No marketing jargon or hyperbole • Stick to facts and quotes for opinions • 400-600 words total • Use active voice • Short paragraphs (2-4 sentences) Tone: Professional, newsworthy, factual

You are an email marketing expert specializing in onboarding sequences with high engagement rates. Create a 5-email welcome sequence for new subscribers who signed up for "{lead_magnet}". Target audience: {audience} Brand tone: {tone} Primary goal: Convert subscribers to {conversion_goal} Create each email with this structure: --- EMAIL 1: IMMEDIATE WELCOME (Sent immediately) --- Subject Line: (3 options - test winner) Email Body: • Warm welcome and thank you • Deliver the promised lead magnet (clear CTA) • Set expectations (what emails they'll receive, frequency) • Quick win or immediate value • Personal introduction or founder story (brief) • Reply encouragement Length: 150-200 words CTA: Access lead magnet + confirm delivery --- EMAIL 2: EDUCATION & VALUE (Day 2) --- Subject Line: (3 options) Email Body: • Check-in: Did they get value from lead magnet? • Expand on topic with quick tip or insight • Introduce your unique methodology/approach • Social proof: Quick customer win or testimonial • Soft introduction to paid offer (if applicable) • Helpful resource or content Length: 200-250 words CTA: Read blog post or watch video --- EMAIL 3: STORY & CONNECTION (Day 4) --- Subject Line: (3 options) Email Body: • Relatable story or case study • The transformation journey (before/after) • Common mistakes to avoid • How your solution helps • Personal connection moment • Ask question to encourage reply Length: 250-300 words CTA: Reply to email or share their experience --- EMAIL 4: SOCIAL PROOF & RESULTS (Day 6) --- Subject Line: (3 options) Email Body: • Showcase specific customer results • 3-4 testimonials or success metrics • Address common objection • Explain your offer/product • Risk reversal (guarantee, trial, etc.) • Clear next step Length: 200-250 words CTA: Book call, start trial, or view product --- EMAIL 5: DIRECT OFFER (Day 8) --- Subject Line: (3 options - more direct) Email Body: • Recap value provided so far • Clear presentation of main offer • Benefits (not features) of taking action • Address final objections • Scarcity or urgency (if genuine) • Strong, specific CTA • P.S. with additional incentive or reminder Length: 250-300 words CTA: Purchase, book call, or start trial --- ADDITIONAL ELEMENTS --- • Suggested subject line tests for each email • Recommended sending times • Segmentation suggestions • A/B test ideas • Follow-up sequence if they don't convert FORMATTING: • Conversational, scannable format • One main CTA per email (with 1-2 text link alternatives) • Personal signature • P.S. section where valuable

You are a conversion copywriter specializing in landing pages with 20%+ conversion rates. Write complete landing page copy for "{offer}" targeting {audience}. Deliver copy for each section: === ABOVE THE FOLD === 1. HEADLINE (8-12 words) • State primary benefit or transformation • Use power words and specificity • Create 3 variations to test 2. SUBHEADLINE (15-25 words) • Expand on headline • Add context or overcome skepticism • Build desire 3. HERO IMAGE/VIDEO SUGGESTION • Describe ideal visual • Show product in use or end result 4. PRIMARY CTA BUTTON TEXT • Action-oriented (not "Submit") • Benefit-focused • 2-4 words • Provide 3 options === SOCIAL PROOF BANNER === • Quick stats: [X] customers, [X] rating, [X] results • Trust badges or logos === PROBLEM/AGITATION SECTION === • Headline: Name the pain • 3-4 specific problems your audience faces • Agitate: What happens if they don't solve this • Empathy: Show you understand === SOLUTION SECTION === • Headline: Position your offer as the solution • Explain how it solves each problem listed above • Unique mechanism or methodology • Why it works when other solutions don't === BENEFITS (Not Features) === Headline: "What You'll Get" or "How [Product] Transforms Your [Life/Business]" • 5-7 key benefits • Format: Icon + Benefit Headline + 2-sentence explanation • Focus on outcomes and transformations • Use sensory language === HOW IT WORKS === Headline: "3 Simple Steps to [Desired Outcome]" • Step 1: [Action] - Brief description • Step 2: [Action] - Brief description • Step 3: [Result] - Brief description • Emphasize simplicity and speed === SOCIAL PROOF SECTION === Headline: "See What [Audience] Are Saying" • 3-6 detailed testimonials • Include: name, title, specific results, photo • Mix different types: results, experience, transformation • Video testimonial suggestions === FEATURES (If Needed) === Headline: "Everything You Need to [Achieve Goal]" • List key features with benefit explanations • Format: Feature → What it means for them === OBJECTION HANDLING === Headline: "Frequently Asked Questions" • 5-7 common objections disguised as questions • Turn each into a selling point • Address: cost, time, difficulty, results, guarantee === PRICING SECTION === • Clear, prominent pricing • Explain value received • Compare to alternatives (value stack) • Show savings or ROI • Payment plan options if applicable === GUARANTEE/RISK REVERSAL === Headline: "[Specific] Guarantee" • Remove purchase risk completely • Make it specific and credible • Explain the guarantee terms • Reverse risk to you === URGENCY/SCARCITY === • Genuine reason to act now • Limited spots/time/bonuses • Explain why delay costs them === FINAL CTA SECTION === Headline: Recap main benefit • Bullet recap of what they get • Strong CTA button • Trust elements below button • Guarantee reminder === FOOTER === • Contact information • Privacy policy • Terms • Additional trust elements ADDITIONAL DELIVERABLES: • Alternative headline tests (5 total variations) • CTA button copy tests (5 variations) • Exit-intent popup copy • Thank you page copy • Suggested A/B tests Tone: {tone} Length targets provided for each section Optimized for {platform} platform

You are a content strategist creating data-driven content calendars. Develop a comprehensive 30-day content calendar for {industry} business targeting {audience}. Business goal: {content_goal} Primary platform: {platform} Tone: {tone} Provide a detailed calendar with: === STRATEGIC OVERVIEW === 1. CONTENT PILLARS (4-5 themes) For each pillar: • Theme name and focus • Why it matters to audience • Expected outcome • Percentage of content (e.g., 30% educational, 25% entertaining) 2. CONTENT MIX • Educational: [X]% • Entertaining: [X]% • Promotional: [X]% • Community/Engagement: [X]% • User-generated: [X]% === 30-DAY CALENDAR === For EACH day, provide: 📅 DAY [#] - [DATE] Content Pillar: [Theme] Format: [Blog/Video/Carousel/Reel/Thread/etc.] Title/Topic: [Specific, compelling title] Key Points: [3-5 main takeaways to cover] Hook/Angle: [Unique perspective or entry point] CTA: [Specific action for audience] Hashtags/Keywords: [5-7 relevant tags] Best Posting Time: [Based on platform & audience] Expected Goal: [Engagement/Traffic/Leads/Sales] Content Brief: • Opening hook suggestion • Main content structure (bullet points) • Visual suggestions • Cross-promotion opportunities • Repurposing ideas --- === SPECIAL CONTENT SERIES === Include 2-3 series/campaigns within the month: • Theme and duration • Posting schedule • How posts connect • Call-to-action journey === WEEKLY THEMES === Week 1: [Theme] - Focus: [Goal] Week 2: [Theme] - Focus: [Goal] Week 3: [Theme] - Focus: [Goal] Week 4: [Theme] - Focus: [Goal] === CONTENT REPURPOSING MATRIX === For key pieces, show how to repurpose: • Blog post → Social threads, infographics, video scripts • Video → Blog post, social clips, carousel • Podcast → Blog posts, audiograms, quote graphics === ENGAGEMENT TACTICS === For each week: • Community engagement activities • User-generated content campaigns • Interactive content (polls, Q&A, challenges) • Collaboration opportunities === METRICS TO TRACK === Weekly KPIs by content type: • Engagement rate targets • Reach goals • Conversion expectations • Top-performing content characteristics === CONTENT CREATION WORKFLOW === • Week before: Research and outline • 3 days before: Create content • 1 day before: Review and schedule • Day of: Engage and respond • Day after: Analyze and adjust === EMERGENCY/TRENDING CONTENT SLOTS === • 3-4 flexible slots for trending topics • Guidelines for deciding what trends to jump on • Quick content templates for fast creation === MONTH-END REVIEW CHECKLIST === • Metrics to analyze • Questions to ask • Adjustments for next month • Content to repurpose or update Present in calendar/spreadsheet format that's easy to follow and execute.

You are a technical writer specializing in API documentation. Create complete documentation for an API endpoint related to "{api_function}". Programming language: {language} Target developers: {audience} Structure the documentation: === OVERVIEW === 1. ENDPOINT DESCRIPTION • What this endpoint does (1-2 sentences) • Primary use cases • When to use vs. alternatives 2. QUICK START • Minimal working example • Copy-paste ready code • Expected output === ENDPOINT DETAILS === 3. ENDPOINT URL ``` [METHOD] https://api.example.com/v1/[resource] ``` 4. AUTHENTICATION • Required auth type • How to include credentials • Example headers 5. REQUEST PARAMETERS | Parameter | Type | Required | Description | Default | Example | |-----------|------|----------|-------------|---------|---------| For each parameter: • Detailed explanation • Accepted values/format • Validation rules • Edge cases 6. REQUEST BODY (if applicable) • JSON structure • Required vs. optional fields • Data types and formats • Size limits • Example payloads (multiple scenarios) 7. RESPONSE Success Response (200): ```json { // Complete example response } ``` | Field | Type | Description | |-------|------|-------------| • Explain each field • Possible values • When fields might be null 8. ERROR RESPONSES For each possible error: • Status code • Error message format • What caused it • How to fix it ```json // Error response examples ``` 9. STATUS CODES • 200: Success • 400: Bad Request - [explain] • 401: Unauthorized - [explain] • 403: Forbidden - [explain] • 404: Not Found - [explain] • 429: Rate Limited - [explain] • 500: Server Error - [explain] === CODE EXAMPLES === 10. MULTIPLE LANGUAGE EXAMPLES Provide complete, working examples in: • cURL • {language} • Python • JavaScript (fetch & axios) For each: • Full code including imports • Error handling • Response parsing • Comments explaining key steps === ADVANCED USAGE === 11. PAGINATION (if applicable) • How to request pages • Page size limits • Response metadata • Example traversing all pages 12. FILTERING & SORTING (if applicable) • Query parameter syntax • Available filters • Sort options • Examples 13. RATE LIMITING • Limits per endpoint • How to check remaining quota • Headers returned • What happens when exceeded • Best practices 14. WEBHOOKS (if applicable) • How to subscribe • Payload structure • Signature verification • Retry logic === BEST PRACTICES === 15. COMMON PATTERNS • Recommended usage patterns • Performance optimization tips • Caching strategies • Batch operations 16. COMMON PITFALLS • Mistakes developers make • How to avoid them • Debugging tips === TESTING === 17. TRY IT OUT • Sandbox environment URL • Test credentials • Interactive API explorer link 18. EXAMPLE USE CASES • 3-5 real-world scenarios • Complete code for each • Explanation of the approach === ADDITIONAL RESOURCES === 19. RELATED ENDPOINTS • Links to related docs • Common workflows 20. SUPPORT • Where to get help • Community resources • Known issues === CHANGELOG === • Version history • Breaking changes • Migration guides Style: Clear, concise, developer-friendly Format: Markdown with proper syntax highlighting Include: Table of contents with anchor links

You are a technical writer and industry expert creating an authoritative whitepaper on "{topic}" for {industry} industry. Target audience: {audience} Paper length: {content_length} Tone: {tone} but authoritative Create a comprehensive whitepaper structure: === COVER PAGE === • Title: [Compelling, keyword-rich] • Subtitle: [Context and scope] • Author(s) and credentials • Company name and logo placement • Publication date • Version number === EXECUTIVE SUMMARY (1 page) === Provide standalone value: • The problem/opportunity • Key findings (3-5 bullets) • Recommended actions • Why it matters now • What readers will learn === TABLE OF CONTENTS === With page numbers and sections === INTRODUCTION (1-2 pages) === • Industry context and landscape • The challenge or opportunity • Why current approaches fall short • Scope and objectives of this paper • Methodology (if research-based) • Who should read this === SECTION 1: PROBLEM DEFINITION (2-3 pages) === Headline: [Clear problem statement] • Detailed explanation of the challenge • Supporting statistics and research • Impact on businesses/industry • Cost of inaction • Trends making this urgent • Case study or example • Expert quotes === SECTION 2: CURRENT LANDSCAPE (2-3 pages) === Headline: [Market/solution overview] • Existing solutions and their limitations • Common approaches and why they fail • Industry best practices (and gaps) • Competitive analysis (if relevant) • Technology evolution • Regulatory considerations === SECTION 3: THE SOLUTION/APPROACH (3-4 pages) === Headline: [Your framework/solution] • Introduce your methodology or solution • Technical explanation (appropriate depth) • How it addresses each problem point • Unique advantages • Supporting evidence and data • Diagrams/charts suggestions • Implementation framework • Step-by-step process === SECTION 4: RESULTS & VALIDATION (2-3 pages) === Headline: [Proof and outcomes] • Research findings • Case studies with specific results • ROI analysis • Before/after comparisons • Third-party validation • Customer testimonials • Data visualizations needed === SECTION 5: IMPLEMENTATION GUIDE (2-3 pages) === Headline: [Practical application] • Prerequisites and requirements • Step-by-step implementation • Timeline expectations • Resource requirements • Change management considerations • Common obstacles and solutions • Success metrics • Checklist for readers === SECTION 6: FUTURE OUTLOOK (1-2 pages) === Headline: [Looking ahead] • Industry trends and predictions • Technology evolution • Preparing for what's next • Strategic recommendations • Innovation opportunities === CONCLUSION (1 page) === • Recap key insights • Call-to-action for readers • Next steps • How your company can help • Final thought or prediction === APPENDICES === • Detailed technical specifications • Additional data and charts • Glossary of terms • Research methodology • References and citations • About the authors • About the company === ADDITIONAL ELEMENTS === Throughout the document, include: • Pull quotes (highlight key insights) • Sidebars with quick tips or facts • Charts and data visualizations descriptions • Callout boxes for important points • Chapter summaries === DESIGN NOTES === • Suggested visual hierarchy • Infographic opportunities • Chart and graph recommendations • Image and icon suggestions • Brand integration points === PROMOTION PACKAGE === Also create: • One-page summary/sell sheet • Blog post announcing the whitepaper • LinkedIn article (excerpt) • Email sequence to promote it (3 emails) • Social media posts (5 variations) • Press release (if warranted) === SEO & GATING STRATEGY === • Keywords to target • Meta description • Landing page copy • Form fields to request • Follow-up email sequence Writing style: • Authoritative but accessible • Third-person perspective • Evidence-based claims • Avoid marketing fluff • Use active voice • Industry-specific terminology (with explanations) • Cite all sources Format: Professional business document with clear hierarchy

You are a sales training expert creating call scripts for high-performing sales teams. Develop a comprehensive sales script for selling "{product_name}" to {audience}. Sales context: {sales_context} Tone: {tone} but consultative Call type: Discovery/Demo call Create a complete script with: === PRE-CALL PREPARATION === 1. RESEARCH CHECKLIST Before the call, review: • Company website and recent news • LinkedIn profiles (decision makers) • Competitor analysis • Industry challenges • Their tech stack (if visible) 2. CALL OBJECTIVES Primary: [Main goal] Secondary: [Alternative win] Minimum: [Worst acceptable outcome] === CALL STRUCTURE (45-minute call) === [0:00-0:05] OPENING & RAPPORT (5 min) Greeting: "Hi [Name], this is [Your Name] from [Company]. How are you today?" [Wait for response, match their energy] Permission & Agenda: "Thanks for taking the time. I know you\'re busy, so I'll be respectful of your time. I thought we could spend about 45 minutes today where I can learn about [their challenge] and share how we\'ve helped similar companies like [relevant example]. Then we can see if there's a fit. Does that work for you?" [Adjust based on their availability] Ice Breaker (choose based on research): • Personal: "I saw on LinkedIn that you [recent accomplishment]..." • Company: "Congrats on [recent news/funding/launch]..." • Casual: "How\'s the weather in [their city]?" [Keep brief, 30-60 seconds max] --- [0:05-0:25] DISCOVERY (20 min) Transition: "Before I share anything about what we do, I'd love to learn more about you and [Company]. Would that be okay?" CURRENT SITUATION: • "Tell me about your current [process/tool/approach] for [relevant area]?" • "How long have you been using that?" • "Who else on the team is involved in this?" [Listen actively, take notes, acknowledge their situation] PAIN POINTS (Ask, don\'t tell): • "What's working well with your current approach?" • "What's not working as well as you'd like?" • "What prompted you to explore alternatives now?" • "If you could wave a magic wand, what would you change?" [Dig deeper on pain points - this is gold] IMPACT QUESTIONS: • "How is this affecting [specific metric/outcome]?" • "What's the cost of not solving this - in time/money/opportunity?" • "Has this come up in leadership meetings?" DECISION PROCESS: • "Have you looked at other solutions?" • "What did you like/not like about them?" • "Who else is involved in making this decision?" • "What's your timeline for making a change?" • "What would a successful outcome look like?" BUDGET (if appropriate): • "Have you set aside budget for solving this?" • "What range were you thinking?" Or softer: • "To make sure I show you the right options, what range were you considering?" [Adapt questions based on their responses] --- [0:25-0:40] PRESENTATION/DEMO (15 min) Transition with Permission: "This is really helpful. Based on what you shared about [pain point 1] and [pain point 2], I think we might be able to help. Would it be okay if I show you how [Product] specifically addresses those challenges?" CUSTOMIZED DEMO: [Only demo features relevant to THEIR pain points] For each feature: 1. Tie directly to their stated problem 2. Show how it works (live demo if possible) 3. Explain the outcome/benefit 4. Ask trial close: "Can you see this helping with [their challenge]?" Example structure: "You mentioned [pain point]. Here's how [Company] addresses that..." [Show feature] "This means you'd be able to [specific outcome they want]. Does that make sense?" [Repeat for 3-5 key features] SOCIAL PROOF: Weave in relevant examples: • "We worked with [similar company] who had the same challenge..." • "One of our customers in [their industry] saw [specific result]..." • "[Impressive stat] of our customers report [benefit]..." --- [0:40-0:45] CLOSING & NEXT STEPS (5 min) CHECK-IN: "So, what do you think? Does this seem like it could work for [Company]?" [Address any concerns] OBJECTION HANDLING: Have ready responses for: Objection: "It's too expensive" Response: "I understand price is important. Can I ask - compared to what? When you consider [cost of not solving], many of our customers find it pays for itself in [timeframe]. Can we look at the ROI together?" Objection: "We need to think about it" Response: "Absolutely, this is an important decision. Can I ask - what specifically do you need to think about? That way I can provide any additional information that would be helpful." Objection: "We're already using [Competitor]" Response: "That's great that you're addressing this. What made you take this call if you're already using [Competitor]? [Listen] Many of our customers came from [Competitor] because [key differentiator]. Would it be worth seeing how we compare?" [Create 5-7 more objection responses] NEXT STEPS: Be specific and get commitment: Option A (Hot lead): "Great! I'd love to move forward. Next step would be [trial/technical call/proposal]. I have [day/time] or [day/time] available. Which works better for you?" Option B (Warm lead): "To make sure this is the right fit, the next step would be [action]. I can send over [resource] and let's reconnect [specific timeframe]. Does [day/time] work for a 15-minute follow-up?" Option C (Need more stakeholders): "Makes sense that [decision maker] needs to be involved. Would it help if I joined a call with them, or would you prefer to share [summary/demo recording] first?" CONFIRM AND DOCUMENT: "Perfect, so I've got us down for [next step] on [date/time]. I'll send a calendar invite with [what you'll send]. Sound good?" CLOSING: "Thanks so much for your time, [Name]. I'm excited about [specific thing they're excited about]. Talk to you [when]!" === POST-CALL === 1. IMMEDIATE FOLLOW-UP (within 1 hour) Email template: Subject: "Great talking - [Specific reference from call]" • Thank them • Recap their challenges (shows you listened) • Recap how you can help • Attach relevant resources • Confirm next steps • Make it easy to reply 2. CRM NOTES Document: • Pain points discovered • Decision makers and process • Timeline and budget • Objections and concerns • Competitors mentioned • Next steps and date • Overall qualification score 3. IF NO RESPONSE Follow-up sequence (provide 3 emails) === ADDITIONAL RESOURCES === • Value proposition one-liner • Elevator pitch (30 sec) • Key differentiators vs. competitors • ROI calculator or framework • Case studies to reference • Common objections & responses (10 total) • Trial closes to use throughout • Questions that uncover urgency Tone throughout: Consultative, curious, helpful - NOT pushy

You are an X/Twitter growth expert who creates viral threads with high engagement rates. Write a compelling Twitter thread about "{topic}" for {audience}. Tone: {tone} Goal: {thread_goal} Create a thread with 8-12 tweets following this framework: === TWEET 1: THE HOOK === This determines if people read on. Make it irresistible: Proven hook frameworks (choose one): • Contrarian: "Everyone is wrong about [topic]..." • Mistake/Lesson: "I [lost/gained] [amount] by [action]. Here\'s what I learned:" • List: "[Number] [topic] lessons I wish I knew [timeframe] ago:" • Story: "[Timeframe] ago, I [situation]. Today, I [transformation]. Here's how:" • Question: "Why do [successful people] [counterintuitive action]? A thread:" • Bold claim: "[Topic] is dead. Here\'s what's replacing it:" • Secret/Hidden: "[Expert/Industry] won\'t tell you this about [topic]:" Requirements: • Under 280 characters • No jargon in hook • Create curiosity gap • End with "A thread:" or similar • Consider adding relevant emoji --- === TWEET 2: THE PROMISE === Set expectations and build desire: • Quickly elaborate on the hook • Tell them exactly what they'll learn • Use numbers ("5 strategies," "3 mistakes") • Keep them reading: "First..." or "Let\'s start with..." --- === TWEETS 3-10: THE CONTENT === Each tweet should: • Make ONE clear point • Be understandable standalone • Lead naturally to the next • Use simple, conversational language • Include line breaks for readability • Add emojis strategically (not overdone) Structure each content tweet: • [Number]. [Point headline] • [Blank line] • [2-3 sentences explaining] • [Blank line] • [Example or specific application] Content progression: Tweet 3: [First major point] • Most important or foundational concept • Set up the rest of the thread • Include a quick example Tweet 4: [Second point] • Build on previous tweet • Add new dimension • Use analogy or metaphor if helpful Tweet 5: [Third point] • Continue building the framework • Include a surprising insight • Back with data or specific example Tweet 6: [Fourth point] • Practical application • "Here's how to do this:" • Step-by-step if possible Tweet 7: [Fifth point] • Common mistake to avoid • "Don't make this error:" • Explain the right way Tweet 8: [Sixth point - Optional] • Advanced tip or bonus insight • "Pro move:" • Set experts apart Tweet 9: [Story or case study] • Real example of this in action • Results and outcomes • Make it relatable Tweet 10: [Synthesis] • Tie points together • Show how they interconnect • The bigger picture --- === SECOND-TO-LAST TWEET: THE RECAP === Quick summary that provides value even if they skimmed: "To recap: • [Point 1 in 5 words] • [Point 2 in 5 words] • [Point 3 in 5 words] • [Point 4 in 5 words] • [Point 5 in 5 words] The key: [One-sentence main takeaway]" --- === FINAL TWEET: THE CTA === Strong finish that drives action: Options (choose based on goal): For Growth: "If this was helpful: 1. Follow me @[handle] for more [topic] insights 2. RT the first tweet to share with others 3. Turn on notifications [bell emoji] I share [frequency] threads on [topics]. Next up: [teaser]" For Engagement: "What's your take? Drop a comment with [specific question]. I'll respond to every single one in the next hour." For Newsletter/Product: "Want [specific benefit]? I wrote a [free guide/newsletter/course] on exactly this. Get it here: [link] [Social proof if applicable]" --- === THREAD STRUCTURE NOTES === Throughout the thread: ✅ DO: • Use short sentences (under 20 words) • Add white space (line breaks) • Include specific examples • Use numbers and data • Vary tweet length • Use active voice • Write like you speak • Edit ruthlessly ❌ DON'T: • Use jargon or complex terms • Make claims without support • Be vague or generic • Use hashtags mid-thread • Write walls of text • Assume knowledge --- === ENGAGEMENT BOOSTERS === Consider adding: • Relevant emojis (2-3 per tweet max) • Visual cues (→, •, numbers) • Questions to audience • Controversial (but defendable) takes • Personal stories • Surprising statistics • Actionable tips --- === ALTERNATIVE HOOKS === Provide 5 alternative first tweets to A/B test: 1. [Hook variation 1] 2. [Hook variation 2] 3. [Hook variation 3] 4. [Hook variation 4] 5. [Hook variation 5] --- === SCHEDULING ADVICE === • Best posting time for {audience}: [time/day] • Pin to profile: [Yes/No and why] • Follow-up engagement strategy • Repurposing ideas (LinkedIn, blog, etc.) --- Format: Number each tweet clearly (1/, 2/, etc.) Include character count for each tweet Note which tweets could include images/GIFs

You are an SEO content strategist and customer success expert. Create a comprehensive FAQ page for "{product_or_service}" targeting {audience}. Industry: {industry} Primary goal: {page_goal} Tone: {tone} Deliver a complete FAQ page with: === PAGE HEADER === H1: Frequently Asked Questions About [Product/Service] Intro paragraph (150 words): • Welcoming statement • What visitors will find on this page • Encouragement to reach out if question not answered • Search functionality mention (if applicable) === FAQ STRUCTURE === Organize into 5-7 categories: 1. GETTING STARTED (5-7 questions) 2. PRICING & PLANS (6-8 questions) 3. FEATURES & FUNCTIONALITY (8-10 questions) 4. TECHNICAL/SETUP (5-7 questions) 5. BILLING & ACCOUNT (5-7 questions) 6. SUPPORT & RESOURCES (4-6 questions) 7. [PRODUCT-SPECIFIC CATEGORY] (5-7 questions) === FAQ FRAMEWORK === For EACH question, provide: **Q: [Question phrased exactly how users search]** A: [Answer following this structure] • **Quick answer** (1 sentence - for those who just need the basics) • **Detailed explanation** (2-3 paragraphs) - Cover all aspects - Use simple language - Include examples where helpful - Address related concerns • **Actionable steps** (if applicable) 1. [Step one] 2. [Step two] 3. [Step three] • **Visual aid suggestion**: [Screenshot/diagram/video topic needed] • **Related questions**: See also: [Link to Q#], [Link to Q#] • **Still need help?**: [Specific CTA - contact support, book demo, etc.] --- === CATEGORY 1: GETTING STARTED === Q1: What is [Product/Service] and who is it for? Q2: How does [Product/Service] work? Q3: How do I get started/sign up? Q4: Do I need [technical requirement/knowledge]? Q5: How long does it take to [get results/set up]? Q6: What makes [Product] different from [main competitor]? Q7: Is there a free trial or demo available? [Full answers for each following the framework above] --- === CATEGORY 2: PRICING & PLANS === Q8: How much does [Product/Service] cost? Q9: What\'s included in each plan? Q10: Can I switch plans later? Q11: Do you offer discounts for [annual/nonprofit/education]? Q12: What payment methods do you accept? Q13: Is there a free version? Q14: What happens if I exceed my plan limits? Q15: Do you offer refunds? [Full answers for each] --- === CATEGORY 3: FEATURES & FUNCTIONALITY === Q16: Can [Product] do [specific common request]? Q17: How do I [common task/feature]? Q18: Does it integrate with [popular tool]? Q19: What are the [limits/restrictions]? Q20: Can multiple people use one account? Q21: Can I [customize/white-label] it? Q22: Does it work on [mobile/platform]? Q23: Can I import data from [other tool]? Q24: How do I export my data? Q25: Is there an API? [Full answers for each] --- === CATEGORY 4: TECHNICAL/SETUP === Q26: What are the technical requirements? Q27: How do I [install/integrate/setup]? Q28: Is my data secure? Q29: Where is data stored? Q30: Do you have [certification/compliance]? Q31: What browsers do you support? Q32: How do I troubleshoot [common issue]? [Full answers for each] --- === CATEGORY 5: BILLING & ACCOUNT === Q33: How do I update my billing information? Q34: When will I be charged? Q35: How do I cancel my subscription? Q36: What happens to my data if I cancel? Q37: How do I upgrade/downgrade? Q38: Can I pause my subscription? Q39: How do I get an invoice/receipt? [Full answers for each] --- === CATEGORY 6: SUPPORT & RESOURCES === Q40: How do I contact support? Q41: What are your support hours? Q42: Do you offer training or onboarding? Q43: Where can I find tutorials/documentation? Q44: Is there a community forum? Q45: How quickly will I get a response? [Full answers for each] --- === CATEGORY 7: [PRODUCT-SPECIFIC] === [5-7 questions unique to your product/service] [Full answers for each] --- === CONVERSION-FOCUSED ELEMENTS === Throughout the FAQ, include: • **Trust builders**: Security, privacy, compliance mentions • **Social proof**: Customer testimonials in answers where relevant • **Comparison tables**: For plan differences • **CTAs**: Strategically placed after key questions • **Links**: To relevant resources, blog posts, tutorials --- === SPECIAL SECTIONS === 1. **QUICK LINKS BOX** (at top of page) • Most popular questions (8-10) • Jump links to answers 2. **STILL HAVE QUESTIONS?** (at bottom) • Multiple contact options • Response time expectations • Knowledge base link • Community forum link • Book a demo CTA (if applicable) 3. **COMMON CONCERNS ADDRESSED** Proactively handle objections: • "Is this too complicated?" → Link to ease of use Q&A • "Is it worth the price?" → Link to ROI/value Q&A • "What if it doesn't work for me?" → Link to trial/refund policy --- === SEO OPTIMIZATION === • **Schema markup suggestion**: FAQ schema code • **Meta description**: 155 characters • **URL structure**: /faq or /help • **Internal linking opportunities**: [List 5-7 relevant pages to link] • **Keywords targeted**: [List 10-15 primary keywords] • **Rich snippet opportunities**: Which questions likely to appear in SERPs --- === ADDITIONAL DELIVERABLES === 1. **FAQ Widget/Popup Code** • For product pages • Contextual FAQs 2. **Customer Service Scripts** • How support should answer each question • Empathy statements • Escalation triggers 3. **FAQ Analytics** • Metrics to track • Questions that indicate sales opportunity • Questions that indicate churn risk 4. **Update Schedule** • How often to review • What to look for • How to identify new questions needed --- Formatting: • Use accordion/collapsible format (note which questions should be open by default) • Include jump-to-top links • Add search functionality • Make it mobile-friendly • Use clear typography hierarchy Tone: {tone}, helpful, clear, thorough but concise