Prompt Libraries: Templates, Examples & How to Build Yours

Write conversion-focused landing page copy.

Input Parameters

Parameter	Value
Product	{product_name}
Audience	{audience}
Key benefit	{main_value_prop}
Tone	{professional / friendly / bold}

Deliverables

1. Hero Section

• Headline: Under 10 words, benefit-led
• Subheadline: 1-2 sentences, expand on value

2. Feature Blocks (x3)

Feature 1:
  Headline: [benefit-focused, 5-7 words]
  Body: [2 sentences, specific outcome]

3. CTA Options

• Primary CTA: {action verb + outcome}
• Secondary CTA: {lower commitment}

🚫 Avoid

• Generic phrases ("best-in-class", "cutting-edge")
• Hype words without substance
• Passive voice

Write 3 meta description options optimized for CTR.

Page Details

Parameter	Value
Page title	{title}
Primary keyword	{keyword}
Page type	{blog post / product page / landing page / guide}
Unique angle	{what makes this page different}

Requirements

• ✅ Under 155 characters (show count)
• ✅ Include primary keyword naturally
• ✅ Include a benefit or outcome
• ✅ End with CTA or curiosity hook

Output Format

1. [Meta description] (XXX chars)
   Why: [brief rationale]

2. [Meta description] (XXX chars)
   Why: [brief rationale]

3. [Meta description] (XXX chars)
   Why: [brief rationale]

Recommended: Option # because...

Generate comprehensive documentation for this function.

Code

{paste_function_here}

Output Format: {JSDoc / Docstring / Markdown}

Required Sections

Section	Include
Description	1 sentence, what it does
Parameters	Name, type, description, default
Returns	Type + description
Throws	Error types + conditions
Example	Realistic usage, not trivial
Notes	Edge cases, performance, related

Example Output (JSDoc)

/**
 * Brief description of what the function does.
 *
 * @param {string} param1 - Description of param1
 * @param {Object} [options] - Optional configuration
 * @param {number} [options.timeout=3000] - Timeout in ms
 * @returns {Promise<Result>} Description of return value
 * @throws {ValidationError} When input is invalid
 *
 * @example
 * const result = await myFunction('input', { timeout: 5000 });
 */

Generate a production-ready SQL query.

Task

{what you want to get/do}

Database

Dialect: {PostgreSQL / MySQL / SQLite}

Schema

{paste_schema_or_describe_tables}

Requirements

Rule	Details
Columns	Explicit names (no SELECT *)
Comments	Explain complex joins/conditions
Sorting	Include ORDER BY if relevant
Security	Use parameterized placeholders

Output Format

Query

-- Brief description of what this query does
SELECT ...

Explanation

• Query logic breakdown
• Why this approach

Performance Notes

• Recommended indexes
• Potential bottlenecks for large tables

Create a well-structured user story with acceptance criteria.

Input

Parameter	Value
Feature	{feature_description}
User type	{persona or role}
Product	{what the product does}

---

Output Format

🎫 Title

[Short descriptive title]

📖 User Story

As a [user type], I want to [action/goal], So that [benefit/outcome].

✅ Acceptance Criteria

#	Given	When	Then
1	[context]	[action]	[result]
2	...	...	...

Include 3-5 testable criteria

⚠️ Edge Cases

• Edge case 1: How to handle
• Edge case 2: How to handle

🚫 Out of Scope

• What this story explicitly doesn't include

Write a customer support response that resolves the issue.

Ticket Details

Parameter	Value
Issue	{describe the customer's problem}
Sentiment	{frustrated / confused / neutral / positive}
Status	{solved / workaround / investigating / cannot fix}
Brand voice	{professional / friendly / casual}
Company	{company}

Response Structure

1. 👋 Acknowledge

• Empathetic, not robotic
• Match their energy level

2. 💡 Explain

• Clear situation/solution
• No technical jargon

3. ➡️ Next Steps

Step 1: [action]
Step 2: [action]

4. 🤝 Close

• Offer additional help
• Appropriate sign-off

Constraints

• ⏱️ Max 150 words
• 🚫 No corporate jargon
• ✅ Be specific, not generic

Write an engaging LinkedIn post optimized for reach.

Post Parameters

Parameter	Value
Topic	{topic or insight}
Goal	{awareness / engagement / lead gen / thought leadership}
Tone	{professional / conversational / bold / inspirational}

Post Structure

1. 🎣 Hook (Line 1)

• Stop the scroll
• No emojis in hook
• Pattern interrupt or hot take

2. 📖 Body (3-5 paragraphs)

• Short paragraphs (1-2 sentences)
• One idea per paragraph
• Story or insight with specifics

3. 💡 Takeaway

• Clear lesson or insight
• Actionable if possible

4. ❓ CTA

• Engagement question, or
• Soft ask (save, share, comment)

5. #️⃣ Hashtags

• 3-5 relevant tags
• Mix of broad + niche

Constraints

• 📏 Max 1300 characters
• ⬇️ Use line breaks for readability
• 🚫 No "I'm excited to announce"
• 🚫 No engagement bait clichés

Summarize this research for a {technical / non-technical} audience.

Content

{paste_article_or_paper}

---

Output Format

📝 TL;DR

1-2 sentences, the core finding

🔑 Key Findings

#	Finding	Significance
1	...	Why it matters
2	...	...

3-5 bullet points

🔬 Methodology

2-3 sentences: How the research was conducted

⚠️ Limitations

• What the research doesn't cover
• Caveats to consider

💡 Practical Implications

• How to apply this
• Who should care

❓ Open Questions

• What to explore next
• Related areas of inquiry

Constraints

• 📏 Max 400 words total
• 📖 Define jargon on first use
• ⚠️ Note any contested claims