Prompt Library

Write complete landing page copy for {product_name}. Target customer: {target_customer} Main pain point they have: {pain_point} Key benefit of the product: {key_benefit} Social proof available: {social_proof} Structure the copy as follows: 1. Hero headline (benefit-led, under 10 words) 2. Subheadline (expands on the headline, 1-2 sentences) 3. Three benefit sections (each with a bold heading + 2-sentence explanation) 4. Social proof block (use the provided testimonials/stats) 5. FAQ section (3 most common objections answered) 6. Final CTA section (urgency-based, clear next step) Tone: {tone} Avoid: jargon, passive voice, generic phrases like 'world-class' or 'cutting-edge'

Write a 5-email welcome sequence for {business_type}. Goal of the sequence: {conversion_goal} Target audience: {audience} Product/service being promoted: {product} Brand voice: {brand_voice} Email structure: - Email 1 (Day 0): Welcome + deliver the promised value. Subject line + full body. - Email 2 (Day 2): Teach one key insight related to the product. No pitch. - Email 3 (Day 4): Share a customer success story or case study. Soft pitch at end. - Email 4 (Day 6): Address the #1 objection your audience has. Direct pitch. - Email 5 (Day 9): Final follow-up with urgency or scarcity. Strong CTA. For each email include: subject line, preview text, full body copy, and CTA button text. Keep each email under 250 words. No fluff.

Write 3 ad copy variations for {product_or_service} targeting {target_audience} on {platform}. Each variation must use a different psychological angle: - Variation 1: Pain point / problem-led (open with the frustration they feel) - Variation 2: Aspiration / outcome-led (open with the result they want) - Variation 3: Social proof / credibility-led (open with a stat, testimonial, or authority signal) For each variation provide: - Primary headline (under 40 characters) - Secondary headline (under 40 characters) - Body copy (under 125 characters) - CTA button text (under 20 characters) Product USP: {usp} Key offer: {offer} Tone: {tone} Do not use exclamation marks. Avoid superlatives like 'best' or 'amazing'.

Write a production-ready {language} function that {description}. Requirements: - Input parameters: {inputs} - Expected output: {output} - Edge cases to handle: {edge_cases} The function must include: 1. Full type annotations / type hints 2. Comprehensive docstring with parameters, return value, raises, and usage example 3. Input validation with descriptive error messages 4. Error handling for all edge cases listed above 5. At least 4 unit tests covering: happy path, edge cases, and error conditions Coding standards: {coding_standard} Optimize for: {optimize_for} Do not use external libraries unless absolutely necessary. Explain any non-obvious logic with inline comments.

Perform a thorough code review of the following {language} code and provide a refactored version. Code to review: {code} Review it across these dimensions: 1. Correctness — are there any bugs or logic errors? 2. Performance — any inefficiencies, unnecessary loops, or memory issues? 3. Security — any injection risks, unvalidated inputs, or exposed secrets? 4. Readability — naming conventions, function length, complexity 5. Best practices — does it follow {coding_standard} standards? 6. Test coverage — what's missing from a testing perspective? For each issue found: - Describe the problem clearly - Explain why it matters - Show the fix with a code snippet Then provide the fully refactored version of the code. Rate the original code quality 1-10 and explain the rating.

Design a {system_type} system for {use_case}. Scale requirements: - Expected users: {users} - Data volume: {data_volume} - Latency requirement: {latency} Provide a complete system design covering: 1. High-level architecture diagram (described in text with components and connections) 2. Database design — schema, choice of SQL vs NoSQL and why 3. API design — key endpoints with request/response structure 4. Caching strategy — what to cache, where, and for how long 5. Scalability approach — how the system handles 10x traffic growth 6. Failure points and how to handle them (redundancy, fallbacks) 7. Security considerations Tech stack preference: {tech_stack} Budget constraint: {budget} Highlight trade-offs for each major decision.

Write a complete {word_count}-word blog post titled "{title}". Target keyword: {primary_keyword} Secondary keywords to include naturally: {secondary_keywords} Target audience: {audience} Content goal: {goal} Structure: 1. Introduction (hook + problem statement + what the reader will learn) 2. {number_of_sections} main sections, each with: - H2 heading (keyword-rich where natural) - 2-3 H3 subheadings - Specific examples, data points, or actionable steps 3. Conclusion with key takeaways and CTA Requirements: - Include at least 2 statistics with context - Use short paragraphs (3 sentences max) - Add a TL;DR summary box after the introduction - Suggest 3 internal link opportunities with anchor text - Tone: {tone} - Avoid: passive voice, filler phrases like 'in today's world', generic advice

Write a professional case study for {client_company} who used {product_or_service} to solve {problem}. Background: - Client industry: {industry} - Company size: {company_size} - Timeframe: {timeframe} - Results achieved: {results} Structure the case study as: 1. Executive Summary (3 sentences — problem, solution, result) 2. The Challenge (what was broken, what they tried before, why it wasn't working) 3. Why They Chose {product_or_service} (decision criteria, alternatives considered) 4. The Implementation (what was done, how long it took, any obstacles) 5. The Results (specific metrics, before vs after comparison) 6. Client Quote (write a realistic, specific quote from {client_name}, {client_title}) 7. Key Takeaways (3 bullet points) Length: 600-800 words. Tone: professional but human. Use specific numbers throughout.

Write a LinkedIn thought leadership post about {topic} from the perspective of {role}. Core insight or lesson to share: {insight} Personal experience or story to draw from: {story_context} Target audience: {audience} Post structure: - Line 1: Bold hook that stops the scroll (under 12 words, no question marks, no 'I') - Lines 2-4: Set up the story or context - Lines 5-10: The main insight broken into short punchy lines (1-2 sentences each) - Lines 11-13: Practical takeaway — what the reader should do differently - Final line: Conversation-starting question for comments Formatting rules: - Max 3 words per line in the hook section - Use line breaks generously — no walls of text - No hashtag spam (max 3 hashtags at the end) - No emojis in the first 3 lines - Length: 150-250 words total

Create a complete on-page SEO content brief for an article targeting the keyword "{target_keyword}". Website: {website} Industry: {industry} Target audience: {audience} Search intent: {search_intent} The brief must include: 1. Recommended title tag (under 60 characters, keyword near the front) 2. Meta description (under 155 characters, includes keyword, has CTA) 3. H1 heading (different from title tag) 4. Recommended URL slug 5. Content outline with H2s and H3s (at least 6 H2 sections) 6. Primary keyword + 8 semantically related keywords to include naturally 7. 3 questions from 'People Also Ask' to answer in the content 8. Word count recommendation based on search intent 9. Internal linking opportunities (suggest 3 existing page topics to link to) 10. Schema markup recommendation (FAQ, HowTo, Article, etc.) Competitor gap: what topics should this article cover that competitors typically miss?

Write a programmatic SEO page for the keyword "{page_keyword}". Page type: {page_type} Website niche: {niche} Target audience: {audience} Page structure: 1. H1: Best {page_keyword} — [Year] Guide 2. Introduction paragraph (120 words, includes keyword in first sentence, explains what the page covers) 3. Quick answer box (50 words — direct answer to the implied question in the keyword) 4. Main content section with 5-8 items, each containing: - H3 heading - 2-3 sentence description - One specific, actionable tip 5. Comparison table (if applicable) 6. FAQ section (5 questions with concise answers) 7. Conclusion with internal CTA linking to {cta_destination} SEO requirements: - Keyword density: 1-2% (natural, not forced) - Include keyword in H1, first paragraph, one H2, and meta description - Total length: 800-1200 words - Tone: helpful and direct, not salesy

Write a complete job description for a {job_title} role at {company_type}. Department: {department} Reports to: {reports_to} Location: {location} Employment type: {employment_type} Salary range: {salary_range} Key responsibilities (provide 6-8 bullet points based on these focus areas): {responsibilities} Required qualifications: - Years of experience: {experience} - Must-have technical skills: {technical_skills} - Must-have soft skills: {soft_skills} Nice to have: {nice_to_have} Structure: 1. About the company (2-3 sentences, culture-focused) 2. Role overview (what success looks like in 90 days) 3. What you'll do (responsibilities) 4. What we're looking for (requirements) 5. What we offer (benefits, growth, culture) 6. How to apply Tone: {tone} Avoid: gendered language, age references, unnecessary degree requirements

Write a formal performance review for {employee_name}, {job_title}, covering the period {review_period}. Performance context: - Key achievements this period: {achievements} - Areas where performance fell short: {gaps} - Feedback from peers/stakeholders: {peer_feedback} - Overall rating: {rating} out of 5 Write the review with these sections: 1. Overall Performance Summary (3-4 sentences, balanced, specific) 2. Key Achievements (3-4 bullet points with specific impact and metrics where possible) 3. Areas for Development (2-3 bullet points — constructive, not punitive, with context) 4. Goals for Next Review Period (3 SMART goals with measurable success criteria) 5. Manager's Closing Statement (motivating, forward-looking) Tone: professional, fair, and constructive. Use specific examples throughout. Avoid: vague language like 'good attitude' or 'needs improvement' without specifics. Do not use: 'always', 'never', 'everyone thinks'.

Write a complete YouTube video script for a {duration}-minute video titled "{video_title}". Channel niche: {niche} Target audience: {audience} Video goal: {goal} Tone: {tone} Script structure: 1. HOOK (0:00-0:30) — Pattern interrupt opening. Do NOT start with 'Hey guys' or 'Welcome back'. Open mid-action or with a bold statement. Include a curiosity gap that makes viewers stay. 2. INTRO (0:30-1:00) — Who this is for, what they'll learn, why it matters now. 3. MAIN CONTENT — {number_of_sections} sections, each with: - Section title (for chapters) - Full scripted dialogue - [B-ROLL: description of suggested footage] - Transition to next section 4. MID-ROLL ENGAGEMENT (halfway point) — Natural subscribe ask tied to the video's value, not generic. 5. OUTRO (last 45 seconds) — Recap of 3 key takeaways, next video recommendation, comment question. Add [PAUSE] markers where the presenter should pause for emphasis. Add [GRAPHIC: description] where on-screen graphics would help. Estimate word count per section based on speaking pace of 130 words/minute.

Create a complete YouTube SEO package for a video about {video_topic}. Channel: {channel_name} Target audience: {audience} Primary keyword: {primary_keyword} Video length: {video_length} Deliver: 1. TITLE OPTIONS (5 variations) - Each under 60 characters - Primary keyword in first 3 words where possible - Mix of formats: how-to, listicle, curiosity gap, bold claim - Mark which is recommended and why 2. VIDEO DESCRIPTION (full) - First 2 lines (visible before 'show more'): hook with keyword, under 100 chars total - Full description: 250-300 words, keyword-rich but natural - Timestamps section (create {number_of_chapters} chapter markers) - Links section placeholder - Subscribe CTA - Hashtags (5, placed at very end) 3. TAGS LIST - 15 tags: mix of exact match, broad, long-tail, and related - Formatted as comma-separated list 4. THUMBNAIL TEXT - 3 options, max 4 words each, high contrast, curiosity-driven

Write the narrative and slide content for a {funding_stage} pitch deck for {company_name}. Company details: - What it does: {description} - Problem being solved: {problem} - Solution: {solution} - Target market: {market} - Business model: {business_model} - Traction so far: {traction} - Team: {team} - Funding ask: {ask} - Use of funds: {use_of_funds} Write content for these slides: 1. Cover — tagline (under 10 words, benefit-led) 2. Problem — make the pain visceral and quantified 3. Solution — clear, visual, no jargon 4. Market Size — TAM/SAM/SOM with sources 5. Product — key features tied to customer outcomes 6. Business Model — how you make money, unit economics 7. Traction — metrics that prove demand 8. Competition — honest positioning, your defensible advantage 9. Team — why you specifically will win this 10. The Ask — what you need and exactly what it buys Tone: confident, specific, investor-ready. No buzzwords. Every claim needs a number.

Write 5 customer support response templates for {company_name} in the {industry} industry. Brand voice: {brand_voice} Support channel: {channel} Write templates for these scenarios: 1. Product/service not working as expected (customer is frustrated) 2. Refund request (within policy) 3. Refund request (outside policy — decline with empathy) 4. Feature request acknowledgment (no commitment to build) 5. Escalation to senior support (handing off the conversation) For each template: - Subject line (for email) or opening line (for chat) - Full response body - Closing line - Internal note (what the agent should check before sending) Requirements: - Acknowledge the specific issue in the first sentence - Never use: 'Unfortunately', 'I apologize for any inconvenience', 'As per' - Always offer a clear next step - Keep each response under 150 words - Tone: {tone}

Write a 3-email cold outreach sequence targeting {target_role} at {target_company_type}. Sender context: - Your name/company: {sender} - What you offer: {offer} - The specific value for this prospect: {value_prop} - Social proof: {social_proof} Email 1 — Initial outreach: - Subject line: personalized, under 6 words, no 'quick question' - Opening: reference something specific about their company/role (use {personalization_hook}) - Body: problem you solve → proof → single CTA - Length: under 100 words Email 2 — Follow-up (3 days later): - Different angle from Email 1 - Add one new piece of value (insight, stat, or relevant example) - Even shorter: under 75 words Email 3 — Final follow-up (5 days later): - Breakup email format - Light humor or directness - Leave the door open - Under 50 words Do not use: 'I hope this email finds you well', 'touching base', 'circling back'

Conduct a detailed competitive analysis for {company_name} in the {industry} space. Our company: - Product/service: {our_product} - Target customer: {our_target} - Current positioning: {our_positioning} - Key strengths: {our_strengths} - Known weaknesses: {our_weaknesses} Competitors to analyze: {competitors} For each competitor provide: 1. Overview (what they do, who they target, estimated market share) 2. Pricing model and price points 3. Top 3 strengths 4. Top 3 weaknesses 5. Their messaging and positioning angle 6. Customer sentiment (common praise and complaints) Then provide: - Competitive positioning map (described in text — 2x2 matrix with axes {axis_1} vs {axis_2}) - Our biggest opportunity gaps - 3 strategic recommendations based on the analysis - One 'blue ocean' opportunity none of the competitors are addressing Be specific and honest. Do not sugarcoat weaknesses.

Create a complete user research interview script for {company_name} to understand {research_goal}. Product/service being researched: {product} Target interviewee: {participant_profile} Interview duration: {duration} minutes Research questions we need answered: {research_questions} Script structure: 1. Introduction (5 min) - Interviewer introduction - Purpose of the interview (without biasing answers) - Permission to record - Ground rules 2. Warm-up questions (5 min) — 3 easy questions to build rapport 3. Core questions ({core_duration} min) - 8-10 open-ended questions targeting {research_questions} - For each question: the main question + 2 follow-up probes - Include at least 2 scenario-based questions ('Tell me about a time when...') 4. Concept/product reaction (if applicable) — how to present and what to observe 5. Closing (5 min) - Final open question - Thank you + next steps Include interviewer notes on: what to listen for, red flags, and how to handle off-topic responses.