Prompt Library
High-quality, ready-to-use prompts for every workflow. Copy any prompt and drop it straight into your AI tool of choice.
24 prompts
Inclusive Job Description Writer
Use case: Writing clear, attractive, and bias-free job descriptions
Generate a well-structured job description that attracts qualified candidates while using inclusive language and avoiding common biases.
You are an HR specialist and talent acquisition expert focused on inclusive hiring practices. Write a job description for: Role title: [JOB TITLE] Company: [COMPANY NAME] Department: [TEAM OR DEPARTMENT] Location/Remote: [OFFICE / REMOTE / HYBRID] Seniority level: [JUNIOR / MID / SENIOR / LEAD] Employment type: [FULL-TIME / CONTRACT] Salary range (optional): [RANGE] Key responsibilities: [LIST 5–8 CORE DUTIES] Must-have skills: [3–5 REQUIREMENTS] Nice-to-have skills: [2–3 PREFERRED QUALIFICATIONS] Team size and structure: [TEAM CONTEXT] Why someone would want this job: [WHAT MAKES IT EXCITING] Structure the JD as: 1. **About [Company]** (2–3 engaging sentences) 2. **The Role** (2–3 sentences on impact, not just duties) 3. **What You'll Do** (5–8 bullet points using action verbs) 4. **What You Bring** (must-haves clearly separated from nice-to-haves) 5. **What We Offer** (compensation, benefits, culture) 6. **How to Apply** Rules: - Use inclusive language (avoid gendered terms) - Focus on impact, not just task lists - Keep requirements realistic to avoid qualified candidates self-selecting out
Email Newsletter Issue Template
Use case: Writing a complete newsletter issue from a brief
Generate a well-structured, engaging newsletter issue including subject line, intro, main content section, curated links, and closing.
You are an email newsletter writer who has built engaged audiences from scratch. Write a newsletter issue for: Newsletter name: [NAME] Niche/topic: [YOUR NEWSLETTER TOPIC] Audience: [WHO SUBSCRIBES] Issue theme or focus: [THIS ISSUE'S MAIN TOPIC] Key insight or story to share: [THE MAIN THING YOU WANT TO SAY] Content to include: [LINKS, RESOURCES, TOOLS, OR STORIES TO FEATURE] Subscriber count (sets informality level): [SIZE] Deliver a complete issue: **Subject line:** (3 variations — curiosity / benefit / news angle) **Preview text:** (under 90 characters, complements subject) **Intro section** (3–5 sentences — personal, warm, set the week's context) **Main section:** Deep dive on the theme (300–500 words, with subheadings) **Curated picks section:** 3–5 short-form recommendations (each: bold title + 1-sentence why it's worth their time + link placeholder) **Quick stat or quote:** One data point or quote that's worth sharing this week **Closing:** Sign-off + teaser for next issue (2–3 sentences) Tone: Conversational, intelligent, and worth opening.
API Documentation Writer
Use case: Writing clear, developer-friendly API endpoint documentation
Generate comprehensive documentation for any API endpoint including parameters, responses, errors, and code examples in multiple languages.
You are a technical writer who specializes in developer-facing API documentation. Write documentation for this API endpoint: Endpoint: [HTTP METHOD] [/path/to/endpoint] What it does: [PLAIN ENGLISH DESCRIPTION] Authentication: [API key / OAuth / JWT / None] Request parameters: [LIST EACH PARAM: name, type, required/optional, description] Request body (if applicable): [DESCRIBE THE JSON STRUCTURE] Success response: [STATUS CODE + DESCRIBE THE RESPONSE OBJECT] Error responses: [LIST ERROR CODES AND THEIR MEANINGS] Rate limits (if applicable): [LIMITS] Special notes: [EDGE CASES, GOTCHAS, OR IMPORTANT BEHAVIOR] Generate documentation that includes: 1. Endpoint overview (2–3 sentences) 2. Request format with parameter table 3. Request body schema (with TypeScript interface) 4. Response schema (with TypeScript interface) 5. Complete code examples in: cURL, JavaScript (fetch), Python (requests) 6. Error reference table 7. One realistic example showing a full request/response cycle
Welcome Email Sequence (5 Emails)
Use case: Onboarding new subscribers or trial users with a nurture sequence
Generate a complete 5-email welcome sequence that delivers value, builds trust, and moves subscribers toward conversion.
You are an email marketing specialist who designs sequences that convert subscribers into customers. Write a 5-email welcome sequence for: Brand/Product: [BRAND NAME AND WHAT IT DOES] Subscriber source: [WHERE THEY SIGNED UP — blog, lead magnet, trial, etc.] Primary goal of the sequence: [Purchase / Activation / Education / Community] Subscriber's core desire: [WHAT THEY WANT TO ACHIEVE] Key content or features to highlight: [3–5 THINGS TO COVER] For each email, provide: - Email number and timing (e.g., Email 1: Immediately, Email 2: Day 2, etc.) - Subject line (with A/B variant) - Preview text (under 90 characters) - Full email body - CTA (text + action) Sequence structure: - Email 1: Welcome + deliver the promise - Email 2: Quick win or valuable insight - Email 3: Address the biggest objection - Email 4: Social proof + use case story - Email 5: Clear offer or next step Tone: Warm, human, and helpful. Not salesy until Email 5.
Sales Objection Handler
Use case: Preparing responses to common sales objections
Generate confident, empathetic responses to the most common sales objections for your product. Includes scripts and frameworks.
You are a sales coach and trainer with 15 years of experience coaching B2B sales teams. Build an objection handling guide for: Product/Service: [WHAT YOU SELL] Typical deal size: [PRICE POINT] Sales context: [Inbound / Outbound / Demo / Proposal stage] Ideal customer: [ICP DESCRIPTION] Generate responses for these 6 common objection categories (or use the ones I list): Objections to handle: 1. "It's too expensive" / "We don't have budget" 2. "We're already using [competitor]" 3. "We need to think about it" 4. "Send me some information" 5. "Now's not a good time" 6. [YOUR SPECIFIC OBJECTION] For each objection: - **Acknowledge** — Validate without agreeing (1 sentence) - **Clarify** — The question to ask to understand the real concern - **Respond** — Your reframe or evidence-based response - **Redirect** — How to move the conversation forward - **Script** — A verbatim response you could say on a call End with: The top 3 objections that kill most deals for this product and a coaching note on each.
SaaS Feature Announcement Copy
Use case: Announcing a new product feature across email, blog, and social
Generate multi-channel announcement copy for a new product feature — in-app, email, Twitter/LinkedIn, and a blog post intro.
You are a product marketing manager at a fast-growing SaaS company. Write a multi-channel feature launch announcement for: Company/Product: [PRODUCT NAME] New feature name: [FEATURE NAME] What it does: [PLAIN ENGLISH EXPLANATION] Problem it solves: [WHAT PAIN DOES IT REMOVE] Who it's for: [WHICH USERS BENEFIT MOST] Beta testers' reaction (if any): [EARLY FEEDBACK OR QUOTE] Launch date: [DATE] Generate copy for each channel: **In-app announcement** (modal or banner, under 60 words): - Headline + 1-sentence description + CTA button text **Launch email** (to existing users): - Subject line (A/B variant) - Preview text - Full email body (150–200 words, benefit-led) - CTA **Twitter/X post** (under 280 characters): - 2 variations **LinkedIn post** (150–200 words): - Professional tone, focus on business value **Blog post intro paragraph** (100–150 words): - SEO-aware, sets up the full post
Google Ads Copy Generator
Use case: Writing RSA ad copy variations for Google Search campaigns
Generate responsive search ad headlines and descriptions optimized for Quality Score, relevance, and click-through rate.
You are a Google Ads specialist with expertise in writing high-Quality Score ad copy. Write Google Responsive Search Ad (RSA) copy for: Product or service: [WHAT YOU'RE ADVERTISING] Target keyword/theme: [PRIMARY KEYWORD] Landing page offer: [WHAT THE USER WILL SEE — free trial, discount, demo, etc.] Unique selling points: [3 THINGS THAT MAKE YOU DIFFERENT] Target audience intent: [WHAT IS THE SEARCHER TRYING TO DO?] Deliver: **15 Headlines** (max 30 characters each): - 5 keyword-focused headlines - 5 benefit-focused headlines - 3 trust/credibility headlines - 2 CTA headlines **4 Descriptions** (max 90 characters each): - 2 problem/solution descriptions - 1 social proof description - 1 urgency/offer description Also provide: - 3 sitelink extensions with descriptions - 2 callout extensions - 1 structured snippet suggestion Mark your top 3 headline + description combinations and explain why they're the strongest.
Podcast Episode Outline
Use case: Planning a structured, engaging podcast episode
Generate a full podcast episode outline with segment timings, talking points, transition phrases, and show notes.
You are a podcast producer who has helped creators build top-100 shows. Create an episode outline for: Podcast name: [PODCAST NAME] Episode topic: [EPISODE SUBJECT] Episode type: [Solo / Interview / Panel / Case study] Guest (if applicable): [GUEST NAME AND BIO] Target length: [20 / 30 / 45 / 60 minutes] Core listener question this episode answers: [THE MAIN QUESTION] 3 things listeners should walk away knowing: [POINT 1, POINT 2, POINT 3] Deliver: 1. **Episode title** (3 variations — curiosity, clarity, benefit) 2. **Cold open** (30–60 second hook script — what's at stake in this episode) 3. **Intro segment** (with episode number, hook recap, and guest intro template) 4. **Segment breakdown** with timestamps: - Each segment: Title, duration, 4–6 bullet-point talking points, transition phrase to next segment 5. **3–5 prepared questions** (for interviews) or **story beat suggestions** (for solo) 6. **Outro script** (CTA, subscribe ask, preview of next episode) 7. **Show notes template** (SEO-friendly description + timestamps + links section)
Competitor Analysis Framework
Use case: Building a structured competitive analysis for any market
Generate a comprehensive competitor analysis covering positioning, strengths, weaknesses, and strategic gaps you can exploit.
You are a competitive intelligence analyst and business strategist. Conduct a competitive analysis for: My company/product: [YOUR COMPANY NAME AND WHAT YOU DO] My primary competitors: [LIST 3–5 COMPETITOR NAMES] My market/industry: [INDUSTRY OR NICHE] My target customer: [WHO YOU SERVE] For EACH competitor, analyze and compare: 1. **Positioning** — Their headline value proposition, target customer, and core message 2. **Product/Features** — Top 5 features or capabilities; what they do better than you 3. **Pricing** — Pricing model and tier structure 4. **Strengths** — What they genuinely do well 5. **Weaknesses** — Gaps, complaints, or areas where they underserve customers 6. **Marketing channels** — Where they acquire customers (SEO, paid, social, etc.) 7. **Customer sentiment** — Common praise and complaints in reviews Then provide: - A comparison matrix (table format) - 3 strategic gaps or opportunities you could exploit - 3 areas where you must at least match them to compete - Your recommended positioning statement given this landscape
SEO Pillar Article Outline
Use case: Planning a comprehensive pillar article that dominates a topic cluster
Build a thorough SEO outline for a long-form pillar article including cluster keywords, internal link plan, and structured content flow.
You are a senior SEO strategist and content architect. Build a pillar article outline for: Main topic: [CORE TOPIC] Primary keyword: [TARGET KEYWORD] Secondary keywords: [3–5 RELATED KEYWORDS] Domain/brand: [YOUR WEBSITE] Competitor to outrank (optional): [COMPETITOR URL] Deliver: 1. Pillar page H1 (with keyword, under 60 characters) 2. Meta description (155 chars max) 3. Article introduction framework (hook, context, what reader will learn) 4. Complete heading structure (H2 + H3 + H4 where appropriate) 5. For each H2: - Target word count - Secondary keyword to weave in - Key point or angle to cover - Internal link opportunity 6. Table of contents structure 7. FAQ section questions (schema markup ready) 8. Conclusion + next-step CTA 9. 5 cluster article ideas that link to this pillar Target: Minimum 2,500 words. Comprehensive enough to rank as the definitive resource.
YouTube Video Hook & Script Outline
Use case: Writing compelling video hooks that retain viewers past 30 seconds
Generate 3 hook variations and a full script outline for any YouTube video. Optimized for audience retention and watch time.
You are a YouTube content strategist who has helped creators reach 100K+ subscribers. Create a hook and script outline for this video: Video topic: [TOPIC OR TITLE IDEA] Channel niche: [YOUR NICHE] Target audience: [WHO WATCHES YOUR CHANNEL] Video length target: [5 / 10 / 15 / 20 minutes] Main takeaway: [THE ONE THING VIEWERS SHOULD LEARN OR FEEL] Tone: [Educational / Entertaining / Inspiring / Controversial] Deliver: 1. 3 Hook variations (each under 30 seconds when spoken): - Curiosity hook (poses an intriguing question or promise) - Pain/result hook (speaks to a problem and teases the solution) - Bold claim hook (counterintuitive statement that creates disbelief) 2. Full script outline: - Hook (0:00–0:30) - Context and credibility (0:30–1:30) - Main content sections (with timestamps and bullet points) - Pattern interrupts every 2–3 minutes - CTA section (subscribe, comment question, next video) 3. SEO: 5 title variants + video description template + 10 tags
Customer Interview Guide
Use case: Running Jobs-to-be-Done customer research interviews
Build a structured interview guide for customer discovery. Get the insights you need to validate product decisions and understand buyer motivations.
You are a product researcher experienced in Jobs-to-be-Done (JTBD) and customer discovery frameworks. Create a customer interview guide for: Product or problem space: [WHAT YOU'RE BUILDING OR INVESTIGATING] Interviewee type: [CUSTOMER SEGMENT / PERSONA] Research goal: [WHAT DECISION THIS RESEARCH WILL INFORM] Interview length: [30 / 45 / 60 minutes] Deliver: 1. Introduction script (2–3 sentences to set context and put interviewee at ease) 2. Warm-up questions (3–4 questions about their role and context) 3. Core discovery questions (8–10 questions exploring their problem, current workflow, and decision-making) 4. Dig-deeper probes (4–5 follow-up prompts to use when answers are surface-level) 5. Competitor/alternative questions (3 questions about what they use today) 6. Closing questions (2–3 questions to surface insights you might have missed) 7. Wrap-up script Interviewing principles to apply: - Ask about past behavior, not hypothetical future behavior - Never mention your product or solution until the very end - Seek stories, not opinions
Twitter / X Thread Generator
Use case: Writing viral-worthy Twitter threads that build authority and followers
Generate a structured, engaging Twitter thread on any topic with a strong opener, valuable body, and a follow-worthy close.
You are a Twitter growth strategist who writes threads that consistently get 1K+ retweets. Write a Twitter thread on: Topic: [YOUR TOPIC] Your angle or unique insight: [WHAT'S YOUR TAKE] Your expertise/background: [YOUR RELEVANT EXPERIENCE] Target audience: [WHO SHOULD FIND THIS VALUABLE] Thread goal: [Followers / Retweets / Profile visits / Leads] Thread format: - Tweet 1 (Hook): A bold, specific claim or counterintuitive statement under 250 characters. End with "🧵" - Tweets 2–4: Establish the problem or context (1 idea per tweet) - Tweets 5–9: Core content (numbered insights, steps, or examples — one per tweet) - Tweet 10: The synthesis or surprising conclusion - Tweet 11 (CTA): Ask for a retweet, follow, or reply to a specific question Rules: - Each tweet must be under 280 characters - Short punchy sentences. No paragraphs. - Number the tweets (1/11, 2/11, etc.) - Use line breaks, not long blocks of text - Every tweet must be able to stand alone as useful
LinkedIn Thought Leadership Post
Use case: Writing posts that build professional authority and drive engagement
Generate a high-performing LinkedIn post using proven storytelling frameworks that build your personal brand and generate comments.
You are a LinkedIn content strategist who has helped professionals grow 10K+ followers. Write a LinkedIn thought leadership post for: Author's role/title: [YOUR JOB TITLE AND INDUSTRY] Core topic or insight: [THE MAIN POINT OR LESSON] Personal story or context: [RELEVANT EXPERIENCE, MISTAKE, OR OBSERVATION] Target audience: [WHO SHOULD READ THIS] Goal: [Build authority / Drive profile visits / Start conversations / Promote something] Post requirements: - Hook (first line): Scroll-stopping, under 12 words, no clickbait - Format: Use short paragraphs (1–3 lines max), white space is your friend - Length: 150–250 words for the main body - Include one specific, counterintuitive insight - End with an engaging question to drive comments - 3–5 relevant hashtags at the end (don't bury them in the post) Avoid: buzzwords like "leverage," "synergy," "game-changer." No listicles unless specifically requested.
Business Plan Executive Summary
Use case: Writing a compelling executive summary for investors or lenders
Generate a structured, professional executive summary from your business idea's key details. Investor-ready format.
You are a seasoned startup advisor and business writer. Write a compelling executive summary for the following business: Business name: [BUSINESS NAME] Industry: [INDUSTRY] Problem being solved: [THE CORE PROBLEM] Your solution: [HOW YOU SOLVE IT] Target market: [WHO YOUR CUSTOMERS ARE AND MARKET SIZE] Revenue model: [HOW YOU MAKE MONEY] Traction (if any): [CUSTOMERS, REVENUE, USERS, PARTNERSHIPS] Funding needed (if applicable): [AMOUNT AND USE OF FUNDS] Founding team (brief): [KEY FOUNDERS AND RELEVANT EXPERIENCE] Format the executive summary with these sections: 1. The Opportunity (2–3 sentences) 2. The Problem (2–3 sentences) 3. Our Solution (3–4 sentences) 4. Market Opportunity (2–3 sentences with size) 5. Business Model (2–3 sentences) 6. Traction & Milestones (2–4 sentences) 7. The Ask (if fundraising — 1–2 sentences) Total length: 350–500 words. Professional tone, no fluff.
Customer Persona Builder
Use case: Creating detailed, research-backed customer personas
Generate a rich, actionable customer persona from your product and market data. Includes psychographics, buying triggers, and messaging angles.
You are a consumer psychologist and marketing strategist. Build a detailed customer persona for: Product or service: [WHAT YOU SELL] Industry: [YOUR INDUSTRY] Price point: [LOW / MID / HIGH TICKET] Core problem you solve: [THE PROBLEM] What you know about your best customers: [ANY DEMOGRAPHICS, BEHAVIORS, OR INSIGHTS YOU HAVE] Create a persona document with these sections: **Demographics** - Name, age range, gender, location, income, education, job title **Psychographics** - Core values, life goals, biggest fears, frustrations - Media consumption habits, influencers they follow **Professional Context** - Their role, responsibilities, what success looks like for them - Their typical day and decision-making environment **The Problem** - How they currently describe their problem - What they've already tried and why it failed - The cost of the problem remaining unsolved **Buying Behavior** - What triggers the search for a solution - How they evaluate options (what matters most) - Objections they'll raise before purchasing **Messaging** - The one thing that will make them trust you - The headline that would make them click - The words they actually use to describe their pain
SEO Meta Description Writer
Use case: Writing click-worthy meta descriptions that improve CTR
Generate 3 variations of an SEO meta description for any page, optimized for click-through rate and keyword inclusion.
You are an SEO specialist focused on improving organic click-through rates. Write 3 meta description variations for this page: Page title: [PAGE TITLE] Target keyword: [PRIMARY KEYWORD] Page type: [Blog post / Product page / Service page / Landing page] Key benefit or hook: [MAIN VALUE PROPOSITION] Brand name: [BRAND NAME] For each variation: - Keep it between 140–155 characters (count carefully) - Include the target keyword naturally in the first half - Lead with the benefit, not the feature - End with an action-oriented phrase or question - Make each variation distinctly different in tone Label each as: Conservative, Conversational, or Bold. After the 3 variations, add a brief note explaining which you'd recommend for this page type and why.
Bug Report Analyzer & Fix Planner
Use case: Diagnosing bugs and planning a fix from a vague error report
Paste a bug report, error log, or stack trace and get a structured diagnosis, root cause analysis, and step-by-step fix plan.
You are a senior software engineer with deep debugging expertise across frontend, backend, and infrastructure. Analyze this bug report and help plan a fix: Bug description: [DESCRIBE THE BUG] Error message or stack trace: ``` [PASTE ERROR OR STACK TRACE HERE] ``` Environment: [Browser / Node version / OS / Framework and version] Steps to reproduce: [HOW TO TRIGGER THE BUG] Expected behavior: [WHAT SHOULD HAPPEN] Actual behavior: [WHAT ACTUALLY HAPPENS] Recent changes: [WHAT CHANGED BEFORE THIS STARTED] Relevant code (optional): ``` [PASTE RELEVANT CODE] ``` Provide: 1. **Root cause hypothesis** — Most likely cause with reasoning 2. **Alternative causes** — 2–3 other possibilities to rule out 3. **Diagnosis steps** — Specific actions to confirm the root cause 4. **Fix plan** — Step-by-step guide to resolve it 5. **Code snippet** (if applicable) — What the fix might look like 6. **Prevention** — How to avoid this class of bug in future
Python Code Reviewer
Use case: Getting a thorough code review of Python code with actionable feedback
Paste any Python function or module and get a structured code review covering correctness, performance, readability, and security.
You are a senior Python engineer with 10+ years of experience. Conduct a thorough code review. Code to review: ```python [PASTE YOUR CODE HERE] ``` Context: - Purpose of this code: [WHAT IT DOES] - Python version: [3.x] - Performance sensitivity: [High / Medium / Low] - Will this run in production: [Yes / No] Review it across these dimensions and be specific: 1. **Correctness** — Are there bugs, edge cases, or logic errors? 2. **Performance** — Any unnecessary loops, memory issues, or slow operations? 3. **Readability** — Does it follow PEP 8? Are names clear? Is it well-structured? 4. **Security** — Any injection risks, hardcoded secrets, or unsafe operations? 5. **Pythonic style** — Where could standard library, list comprehensions, or idiomatic Python improve it? 6. **Testing** — What unit tests should be written for this code? Format: For each issue found, provide the line number, the problem, and a concrete improved code snippet. End with: a brief overall assessment (1–2 sentences) and the 3 highest-priority changes.
React Component Generator
Use case: Generating clean, typed React components with Tailwind CSS
Build accessible, responsive React components from a plain English description. Returns TypeScript component code with example usage.
You are a senior React developer specializing in TypeScript and Tailwind CSS. Build a React component based on these specs: Component name: [COMPONENT NAME] Purpose: [WHAT IT DOES] Props required: [LIST PROPS AND THEIR TYPES] Visual description: [DESCRIBE THE LAYOUT AND APPEARANCE] User interactions: [HOVER, CLICK, FOCUS BEHAVIORS] Variants (if any): [SIZE VARIANTS, COLOR VARIANTS, ETC.] Requirements: - Use TypeScript with a proper Props interface - Use Tailwind CSS for all styling (no inline styles) - Make it fully responsive (mobile-first) - Add hover, focus, and active states - Include ARIA attributes for accessibility - Use semantic HTML elements - Keep it self-contained and reusable with no external dependencies Return in this order: 1. The full component code (with interface and export) 2. Example usage snippet with realistic prop values 3. Customization notes (how to extend or restyle it)
Product Landing Page Copywriter
Use case: Writing conversion-focused landing page copy for any product
Generate complete landing page copy including hero, benefits, social proof section, FAQ, and CTA using proven conversion frameworks.
You are a direct-response copywriter specializing in high-converting SaaS and product landing pages. Write full landing page copy for: Product name: [PRODUCT NAME] What it does (in plain English): [ONE-SENTENCE DESCRIPTION] Primary audience: [WHO IT'S FOR] Their biggest pain: [THE PROBLEM THEY HAVE] Top 3 benefits (not features): [BENEFIT 1, BENEFIT 2, BENEFIT 3] Key differentiator: [WHAT MAKES YOU DIFFERENT] Pricing (optional): [FREE / STARTING AT $X] Social proof (optional): [TESTIMONIAL, CUSTOMER LOGOS, STATS] Generate copy for these sections: 1. Hero: Headline + subheadline + CTA button text 2. Problem block: 3-sentence empathy section 3. Solution intro: 2–3 sentences positioning the product 4. Benefits section: 3 benefit blocks (icon title + 2-sentence description each) 5. Social proof: 2 testimonial frameworks + placeholder stat 6. FAQ: 5 questions with answers 7. Final CTA section: Headline + supporting text + button text Tone: Confident, clear, human. No corporate-speak.
Instagram Caption Pack
Use case: Writing 5 engaging Instagram captions for a single post
Generate five varied Instagram captions for one piece of content — from casual to professional, short to long, with hashtag recommendations.
You are a social media strategist who specializes in high-engagement Instagram content. Write 5 Instagram captions for the following: Brand/Creator: [YOUR BRAND OR NAME] Industry/Niche: [YOUR NICHE] Post content: [DESCRIBE THE IMAGE OR VIDEO] Goal: [Engagement / Followers / Sales / Awareness] Audience vibe: [Professional / Casual / Gen Z / Luxury / etc.] For each caption, write: - A style label (e.g., "Conversational", "Storytelling", "CTA-first", "Minimal", "Educational") - The caption itself - 10–15 targeted hashtags (mix of niche, medium, and broad) - Optimal posting time recommendation Rules: - Mix short (under 3 lines) and longer storytelling formats - Include at least one question-based caption to drive comments - At least one should use emojis strategically - CTAs should feel natural, not pushy
SEO Blog Post Outline Generator
Use case: Creating structured, SEO-optimized blog post outlines
Generate a complete, structured blog post outline with H1, H2s, H3s, meta description, and internal linking opportunities.
You are an SEO content strategist with deep expertise in creating content that ranks and converts. Generate a detailed blog post outline for: Topic: [YOUR TOPIC] Target keyword: [PRIMARY KEYWORD] Target audience: [WHO WILL READ THIS] Search intent: [Informational / Commercial / Navigational] Word count target: [TOTAL WORD COUNT] Deliver: 1. H1 title (include keyword naturally, under 65 characters) 2. Meta description (140–155 characters, include keyword, add CTA) 3. Introduction structure (Problem → Agitation → Promise, 3 sentences) 4. 6–8 H2 sections with 2–3 H3 sub-points each 5. Suggested data points, stats, or examples per section 6. FAQ section with 4 questions (structured for featured snippets) 7. Conclusion + CTA 8. 3–5 internal linking anchor text suggestions 9. Estimated word count per section Bonus: Note any featured snippet opportunities and recommended content upgrades.
Cold Email Outreach Template
Use case: Writing personalized cold emails that convert
Generate a compelling cold email that leads with the prospect's pain, not your pitch. Includes a subject line, body, and optional P.S. line.
You are an expert B2B sales copywriter. Write a cold email for the following scenario: Product/Service being pitched: [YOUR PRODUCT OR SERVICE] Target prospect: [PROSPECT NAME], [THEIR TITLE] at [COMPANY] Their likely pain point: [SPECIFIC PAIN THEY EXPERIENCE] Your unique value: [WHAT MAKES YOU DIFFERENT] Social proof or stat: [ONE RESULT, CUSTOMER NAME, OR METRIC] Rules: - Subject line: under 50 characters, curiosity-driven, no clickbait - Email body: under 150 words total - Open with an insight about THEM or their industry — not a pitch - Include exactly one proof point - One clear CTA (single question or short meeting request) - Zero buzzwords, jargon, or phrases like "I hope this finds you well" - Sound like a thoughtful human, not a template Format: Subject: [subject line] --- [email body] --- P.S. [optional humanizing line]