Skip to main content

AI Prompt Library by Use Case

Well-crafted prompts are the difference between generic AI output and genuinely useful results. A vague request like "help me with my business" produces vague advice. A structured prompt with clear context, specific goals, and defined output formats produces work you can actually use. This library provides tested, ready-to-use prompt templates organized by use case. Each includes variables you can customize for your specific situation and tips for getting the best results.

info

This content was developed with AI assistance and is regularly reviewed for accuracy.

tip

New to prompting? Start with our Prompt Engineering Guide to learn the fundamentals before diving into these templates.

How to Use This Library​

Every template in this library follows a consistent format designed to get you productive fast. Here is what to expect and how to get the most out of each one.

Bracketed variables like [industry] or [time period] are placeholders. Replace them with your specific details before sending the prompt to any AI platform. The more specific you are with these variables, the more useful the output will be. For example, [industry] becomes "mid-market B2B SaaS" rather than just "technology."

Platform compatibility means these templates work with ChatGPT, Claude, Gemini, Copilot, and other major AI platforms. Minor phrasing adjustments may improve results on specific platforms, but the core structure is universal.

Iteration is expected. Treat the first response as a draft. Follow up with refinements like "make the tone more formal," "add specific metrics," or "focus on the second quarter." The best results come from a back-and-forth conversation, not a single prompt.

Combine templates for complex work. Use the Business Review prompt to generate insights, then feed those insights into the Email Communication prompt to share findings with stakeholders. Chaining prompts together creates workflows that handle multi-step projects.

Business & Strategy Prompts​

These prompts help you analyze competitive landscapes, structure strategic thinking, and turn meetings into actionable outputs. They are designed to produce results you can share with colleagues and stakeholders without heavy editing.

SWOT Analysis Generator​

Use case: Generate a structured strengths, weaknesses, opportunities, and threats analysis for a product, business unit, or strategic initiative.

"Conduct a SWOT analysis for [company/product name] in the [industry] sector. Context: [brief description of current situation, such as 'launching a new product line' or 'entering a new market']. Consider these competitive factors: [list 2-3 key competitors or market dynamics]. Format the output as a table with 2-3 bullet points per quadrant, and conclude with the top strategic recommendation based on the analysis."

When to use: Strategic planning sessions, quarterly reviews, new market evaluations, or when preparing board-level presentations that require structured competitive analysis.

Customization tips: Add financial constraints ("with a budget under $500K"), timeline context ("over the next 18 months"), or ask for industry-specific factors ("considering current regulatory trends in [region]").

Competitive Analysis Brief​

Use case: Produce a concise comparison of your organization against key competitors, highlighting differentiators and market positioning.

"Create a competitive analysis comparing [your company/product] against [competitor 1], [competitor 2], and [competitor 3] in the [specific market segment]. Evaluate each on: pricing model, key features, target audience, market share (if known), and primary differentiator. Present the results in a comparison table, then write a 200-word summary of our competitive advantages and the biggest threat we should address."

When to use: Before product launches, during investor preparation, or when sales teams need updated competitive positioning materials.

Customization tips: Specify the audience ("for a sales team battlecard" vs. "for an executive summary") to adjust the level of detail and tone. Add dimensions that matter to your industry, such as compliance certifications, integration ecosystem, or customer support reputation.

Meeting Summary & Action Items​

Use case: Transform raw meeting notes into a structured summary with clear ownership and deadlines.

"Summarize the following meeting notes into a structured format. Include: (1) a 3-sentence executive summary, (2) key decisions made, (3) action items with owner and deadline in a table, and (4) open questions that need follow-up. Meeting notes: [paste your notes here]. Participants: [list of attendees and their roles]."

When to use: After any meeting where accountability matters. Especially valuable for cross-functional meetings, client calls, and project standups.

Customization tips: Add "flag any action items without a clear owner" to catch gaps. For recurring meetings, include "compare these action items against last meeting's open items: [paste previous items]" to track progress.

Quarterly Business Review Draft​

Use case: Generate a first draft of a quarterly business review from raw performance data and notes.

"Draft a quarterly business review for [department/team name] covering [quarter and year]. Key metrics: [list 3-5 KPIs with values, e.g., 'revenue: $2.1M, up 12% QoQ']. Major accomplishments: [list 2-3 highlights]. Challenges faced: [list 2-3 obstacles]. Structure the review with these sections: Executive Summary, Performance Highlights, Challenges & Lessons Learned, Next Quarter Priorities, and Resource Needs. Keep the tone [professional/conversational] and the total length under 800 words."

When to use: End-of-quarter reporting cycles when you need a solid first draft to refine rather than starting from a blank page.

Customization tips: Include audience context like "this will be presented to the VP of Sales" to tailor emphasis. Add "include a comparison against targets" if you have benchmark data available.

Writing & Content Prompts​

Content creation is one of the most common AI use cases, and for good reason. These prompts help you move past the blank page and produce drafts that need polishing rather than wholesale rewriting.

Blog Post Outline​

Use case: Generate a detailed blog post outline with section headers, key points, and a logical narrative arc.

"Create a detailed blog post outline about [topic]. Target audience: [describe reader, e.g., 'small business owners new to AI']. Goal: [what should the reader be able to do after reading?]. Tone: [professional/casual/educational]. Include: a compelling hook for the introduction, 4-6 main sections with 2-3 sub-points each, suggested examples or data points to include, and a clear call-to-action for the conclusion. Target word count for the final post: [number] words."

When to use: When starting any long-form content. An outline keeps your writing focused and ensures you cover all necessary points before investing time in full drafts.

Customization tips: Add SEO context with "target keyword: [keyword], secondary keywords: [list]" to get SEO-aware structure. Specify "include a section addressing the common objection that [objection]" to preemptively handle reader skepticism.

Email Communication​

Use case: Draft professional emails with the right tone, structure, and call-to-action for any business context.

"Write a [formal/informal] email to [recipient role, e.g., 'a prospective client'] regarding [subject]. Key points to cover: [list 2-4 main messages]. Desired outcome: [what action do you want the recipient to take?]. Context: [any background the recipient needs]. Keep the email under [number] words. Sign off as [your name/title]."

When to use: Whenever you need to communicate something important and want to get the tone right on the first try. Particularly useful for sensitive communications, client outreach, and executive updates.

Customization tips: For difficult conversations, add "maintain a positive tone while being direct about [issue]." For follow-ups, include "reference our previous conversation about [topic] on [date]."

Social Media Content Calendar​

Use case: Generate a week or month of social media posts across multiple platforms with consistent messaging.

"Create a [1-week/1-month] social media content calendar for [brand/company] on [platforms: LinkedIn, Twitter/X, Instagram]. Theme for this period: [campaign theme or focus area]. Brand voice: [describe tone, e.g., 'authoritative but approachable']. Include for each post: platform, suggested date/time, post copy (platform-appropriate length), content type (text/image/video/poll), and relevant hashtags. Mix content types: [educational/promotional/engagement/behind-the-scenes]. Include [number] posts per platform per week."

When to use: Monthly content planning sessions, campaign launches, or when you need to maintain consistent social presence without daily brainstorming.

Customization tips: Add "align with these upcoming events: [list dates and events]" for timely content. Include brand guidelines like "never use emojis" or "always include our tagline" for on-brand results.

Press Release Draft​

Use case: Create a structured press release following standard journalistic format for company announcements.

"Write a press release announcing [news/event]. Company: [company name and brief description]. Key details: [who, what, when, where, why]. Include a quote from [executive name, title] that emphasizes [key message]. Target media: [industry trade publications/local news/national business press]. Include boilerplate company description at the end. Follow standard AP style press release format with a compelling headline and subheadline."

When to use: Product launches, partnership announcements, funding rounds, executive hires, or any company news worth public distribution.

Customization tips: Specify "include a data point or statistic in the opening paragraph" to make the release more newsworthy. Add "write an alternative headline option" to give your PR team choices.

Data Analysis Prompts​

AI excels at finding patterns in data and translating numbers into narrative insights. These prompts help you move from raw data to actionable intelligence, whether you are working with spreadsheets, survey results, or performance dashboards.

Data Interpretation & Insights​

Use case: Transform raw data or a dataset summary into meaningful business insights with recommended actions.

"Analyze the following data and provide insights: [paste data or describe the dataset]. Context: this data represents [what the data measures] for [time period]. I need you to: (1) identify the 3 most significant trends or patterns, (2) flag any anomalies or unexpected results, (3) provide possible explanations for each finding, and (4) recommend 2-3 specific actions based on the analysis. Present the findings in order of business impact."

When to use: After pulling reports, receiving new datasets, or when you need to quickly understand what numbers are telling you before a meeting or decision point.

Customization tips: Add "compare against industry benchmarks for [industry]" for external context. Specify "assume the audience has [no/some/deep] statistical background" to control the technical depth of the explanation.

Survey Results Analysis​

Use case: Synthesize survey responses into a structured report with themes, sentiment, and recommendations.

"Analyze these survey results from [survey name/purpose]. Total respondents: [number]. Key questions and response summaries: [paste aggregated results]. Please: (1) identify the top 3 positive themes and top 3 areas of concern, (2) calculate or note any significant differences between [demographic groups or segments], (3) pull out 3-5 representative verbatim quotes that illustrate key themes, and (4) recommend 3 priority actions based on the findings. Format as a report I can share with [stakeholder group]."

When to use: After closing employee engagement surveys, customer satisfaction surveys, market research surveys, or any structured feedback collection.

Customization tips: For NPS surveys specifically, add "segment analysis by promoters, passives, and detractors." For longitudinal data, include "compare against our previous survey results: [summary]."

Trend Analysis Report​

Use case: Identify and explain trends in time-series data with forward-looking projections.

"Analyze the following time-series data for [metric name] over [time period]: [paste data or describe trends]. Identify: (1) overall trend direction and magnitude, (2) seasonal or cyclical patterns, (3) inflection points where the trend changed and possible causes, and (4) a projected range for the next [time period] with assumptions stated. Present the analysis with a narrative summary followed by a structured breakdown of each finding."

When to use: Revenue forecasting, website traffic analysis, customer growth tracking, or any scenario where understanding trajectory matters for planning.

Customization tips: Add "consider these external factors that may have influenced the data: [list events]" for more accurate cause analysis. Include "express projections as best-case, likely, and worst-case scenarios" for risk-aware planning.

KPI Dashboard Narrative​

Use case: Turn a set of KPI values into a written narrative suitable for executive reporting.

"Write a dashboard narrative for [team/department] covering [time period]. KPIs and current values: [list each KPI with current value, target, and previous period value]. For each KPI: (1) state whether it is on track, at risk, or off track, (2) explain the primary driver behind the result in one sentence, and (3) note any required action. Conclude with an overall health assessment and the single most important thing leadership should know. Keep the total narrative under 500 words."

When to use: Weekly or monthly executive reporting, board updates, or any situation where stakeholders need a quick understanding of performance without digging into raw data.

Customization tips: Specify "use red/yellow/green status indicators" for visual clarity. Add "highlight any KPI that changed status from last period" to surface what is new and important.

Development & Technical Prompts​

Whether you write code daily or manage technical teams, these prompts help you work with AI on code review, documentation, and technical decision-making. They produce outputs that follow industry conventions and can slot into existing workflows.

Code Review Assistant​

Use case: Get a thorough code review with actionable feedback organized by severity.

"Review the following [programming language] code for quality, correctness, and maintainability. Code: [paste code]. Context: this code [describe what it does and where it fits in the system]. Review for: (1) bugs or logic errors, (2) security vulnerabilities, (3) performance concerns, (4) readability and naming conventions, and (5) missing edge case handling. Categorize each finding as Critical, Warning, or Suggestion. For each finding, explain why it matters and provide a corrected code example."

When to use: Before merging pull requests, when working without a second reviewer, or when onboarding to an unfamiliar codebase and wanting to validate your understanding.

Customization tips: Add "follow [style guide name] conventions" for team-specific standards. Specify "this code handles [financial transactions/user data/authentication]" to trigger domain-specific security checks.

Technical Documentation Generator​

Use case: Create clear technical documentation from code, APIs, or system descriptions.

"Generate technical documentation for [component/API/system]. Source: [paste code, API spec, or system description]. Documentation should include: (1) overview and purpose, (2) architecture or data flow description, (3) setup/installation instructions, (4) API reference with parameters, return values, and examples, (5) common use cases with code samples, and (6) troubleshooting section. Target audience: [junior developers/senior engineers/external API consumers]. Use [Markdown/reStructuredText] format."

When to use: When shipping new features, onboarding team members, publishing public APIs, or catching up on documentation debt.

Customization tips: Add "include a sequence diagram description for the main workflow" for complex integrations. Specify "follow the documentation structure used in [framework/tool]" for consistency with ecosystem norms.

Bug Report Analysis​

Use case: Analyze a bug report and generate a structured investigation plan with potential root causes.

"Analyze this bug report and help me investigate: [paste bug report or describe the issue]. System context: [technology stack, relevant architecture details]. Symptoms: [what is happening vs. what should happen]. Steps to reproduce: [list steps if known]. Please: (1) list the 3 most likely root causes ranked by probability, (2) suggest specific diagnostic steps for each hypothesis, (3) identify what logs or data to collect, and (4) recommend a temporary workaround if applicable."

When to use: When triaging production issues, investigating intermittent bugs, or when you need a systematic approach to debugging rather than trial-and-error.

Customization tips: Include "this bug affects [number] users and was first reported [date]" to help prioritize. Add "similar issues we have seen before: [list]" to leverage historical context.

Architecture Decision Record​

Use case: Document an architectural decision with context, alternatives considered, and rationale.

"Create an Architecture Decision Record (ADR) for the following decision: [describe the decision, e.g., 'choosing PostgreSQL over MongoDB for our user data store']. Context: [describe the problem or need driving the decision]. Constraints: [list technical, budget, timeline, or team constraints]. Alternatives considered: [list 2-4 options]. Include for each alternative: description, pros, cons, and estimated effort. State the final decision and provide a clear rationale. Follow the standard ADR format with Status, Context, Decision, and Consequences sections."

When to use: When making significant technical decisions that affect system architecture, technology choices, or development workflows. ADRs create a historical record that helps future team members understand why decisions were made.

Customization tips: Add "consider our existing tech stack: [list current technologies]" for integration-aware analysis. Include "this decision must be revisitable in [timeframe]" to build in review triggers.

Education & Training Prompts​

These prompts help educators, trainers, and subject matter experts create learning materials efficiently. They follow pedagogical best practices and produce content that is ready for classroom or self-paced use.

Lesson Plan Creator​

Use case: Generate a complete lesson plan with learning objectives, activities, and assessments.

"Create a lesson plan for teaching [topic] to [audience description, e.g., 'college freshmen with no prior experience']. Duration: [class length]. Learning objectives: by the end of this lesson, students should be able to [list 2-4 specific, measurable objectives]. Include: (1) an opening hook or warm-up activity (5 minutes), (2) main instruction with a mix of lecture and interactive elements, (3) a hands-on practice activity, (4) assessment or check-for-understanding activity, and (5) summary and preview of next lesson. List required materials and preparation steps."

When to use: Preparing new courses, adapting existing material for a different audience, or when you need structured lesson plans quickly for substitute coverage or guest instruction.

Customization tips: Add "incorporate [specific teaching methodology, e.g., 'think-pair-share' or 'flipped classroom']" for pedagogical preferences. Specify "students have access to [list available tools/technology]" to ensure activities are feasible.

Quiz & Assessment Generator​

Use case: Create varied assessment questions aligned to specific learning objectives.

"Generate a [quiz/exam/assessment] on [topic] for [audience level]. Include: [number] multiple choice questions with 4 options each (mark correct answer), [number] short-answer questions, and [number] application-based or scenario questions. Align all questions to these learning objectives: [list objectives]. Provide an answer key with brief explanations for each correct answer. Difficulty distribution: 40% recall, 40% application, 20% analysis. Avoid trick questions."

When to use: Mid-unit checks, final assessments, certification preparation, or when building question banks for adaptive learning systems.

Customization tips: Add "include common misconceptions as distractor options" for more diagnostic multiple choice questions. Specify "format for import into [LMS name]" if you need a specific technical format.

Concept Explainer​

Use case: Explain a concept at an adjustable complexity level, from beginner to expert.

"Explain [concept] at a [beginner/intermediate/advanced] level. Audience: [describe who needs to understand this]. Include: (1) a one-sentence plain-language definition, (2) an analogy or real-world comparison that makes the concept intuitive, (3) a detailed explanation with [1-2/3-4/5+] key subtopics, (4) a concrete example showing the concept in action, and (5) common misunderstandings to avoid. If explaining at the advanced level, include technical nuances and edge cases."

When to use: Creating educational content, preparing to teach a new topic, building glossaries, or when you need to communicate a complex idea to a non-technical audience.

Customization tips: Chain complexity levels together: "First explain at beginner level, then provide an advanced-level addendum" to create layered content. Add "relate this concept to [concept they already know]" to build on existing knowledge.

Training Material Outline​

Use case: Design a complete training program structure with modules, activities, and progression.

"Design a training program outline for [topic/skill]. Audience: [who will be trained, their current skill level]. Training goal: participants will be able to [describe desired competency]. Duration: [total time available, e.g., '3 half-day sessions']. Include: (1) module breakdown with titles and time allocations, (2) learning objectives for each module, (3) suggested activities and exercises, (4) prerequisite knowledge and pre-work, and (5) post-training reinforcement activities. Ensure progressive difficulty and include at least one hands-on practice per module."

When to use: Designing onboarding programs, upskilling initiatives, workshop series, or any structured learning experience.

Customization tips: Specify "include knowledge checks between modules" to build in assessment points. Add "participants will be in [in-person/virtual/hybrid] format" to get format-appropriate activity suggestions.

Customer Service Prompts​

Customer service teams handle high volumes of communication where tone, accuracy, and consistency matter. These prompts help craft responses that are empathetic, professional, and solution-oriented.

Customer Response Template​

Use case: Draft a customer-facing response that addresses concerns while maintaining brand voice.

"Write a customer service response to the following situation: [describe the customer's issue or complaint]. Customer sentiment: [frustrated/confused/neutral/upset]. Resolution available: [describe what you can offer]. Company policy relevant to this case: [state any applicable policy]. The response should: (1) acknowledge the customer's experience, (2) explain what happened (if applicable), (3) state the resolution clearly, (4) provide next steps, and (5) close warmly. Tone: [empathetic and professional/casual and friendly]. Keep under 200 words."

When to use: Responding to complaints, handling refund requests, addressing service failures, or any situation where the right tone is as important as the right answer.

Customization tips: Add "the customer has been with us for [duration] and has [history context]" to personalize the response. Include "offer [specific goodwill gesture]" when you want to go above policy.

FAQ Generator​

Use case: Create a comprehensive FAQ section from product information, support tickets, or common inquiries.

"Generate a FAQ document for [product/service/topic]. Based on these common customer questions and themes: [list 5-10 topics or paste sample support tickets]. For each FAQ entry: (1) write the question in natural customer language, (2) provide a clear, concise answer (3-5 sentences), and (3) include a link placeholder for related resources where applicable. Organize the FAQs into logical categories. Add 3-5 additional questions that customers commonly ask but may not be on this list."

When to use: Launching new products, redesigning help centers, reducing support ticket volume, or onboarding new support team members.

Customization tips: Specify "write questions in the voice of [customer persona]" for authenticity. Add "include questions that address common misconceptions about [topic]" to preemptively reduce confusion.

Escalation Summary​

Use case: Create a concise escalation document that gives the next-tier support agent everything they need.

"Create an escalation summary for the following customer case. Customer: [name/ID]. Issue: [describe the problem]. Timeline: [list key interactions and dates]. Steps already taken: [list troubleshooting or resolution attempts]. Customer sentiment: [describe current emotional state]. What the customer is requesting: [state desired outcome]. Recommended next action: [your suggestion]. Format this as a structured handoff document that a Tier 2 agent can act on immediately without re-contacting the customer for basic information."

When to use: When a case needs to move to a specialist, manager, or technical team. Good escalation summaries prevent customers from repeating themselves and speed up resolution.

Customization tips: Add "include relevant account details: [subscription tier, contract value, renewal date]" for context that affects prioritization. Specify "flag if this customer is at churn risk" for retention-sensitive handling.

Customer Feedback Analysis​

Use case: Analyze a batch of customer feedback to identify themes, sentiment, and priorities.

"Analyze the following customer feedback collected from [source, e.g., 'post-purchase surveys' or 'app store reviews']. Feedback: [paste feedback entries or summarize themes]. Provide: (1) overall sentiment breakdown (positive/neutral/negative with approximate percentages), (2) top 5 themes ranked by frequency, (3) most critical issue requiring immediate attention, (4) a positive highlight worth celebrating or amplifying, and (5) 3 recommended actions prioritized by impact and feasibility. Include representative quotes for each major theme."

When to use: Monthly or quarterly feedback reviews, product roadmap planning, customer experience audits, or when building a business case for improvements.

Customization tips: Add "segment analysis by [customer tier/product line/region]" for more granular insights. Include "compare sentiment against our target NPS of [score]" to benchmark results.

Customizing Prompts for Better Results​

These templates are starting points. The real skill lies in adapting them to your specific context and iterating on the results. Here are techniques that consistently improve output quality across all use cases.

Add context generously. The more relevant background you provide, the better the output. Instead of saying "my company," say "a 50-person B2B SaaS company selling HR software to mid-market companies." Context eliminates guesswork and produces more targeted results.

Specify your output format. If you need a table, say "format as a table." If you need bullet points under 20 words each, say so. If you need something you can paste into a slide deck, mention that. AI platforms are remarkably good at following format instructions when you state them explicitly.

Iterate and refine. Your first prompt is rarely your last. After the initial response, follow up with specifics: "expand on point 3," "make the tone more direct," "add a section about risks," or "rewrite this for a non-technical audience." Treat AI like a collaborator, not a vending machine.

Chain prompts for complex tasks. Break big projects into steps. Use one prompt to research, another to outline, a third to draft, and a fourth to refine. Each step benefits from the accumulated context of the conversation. For advanced techniques on building effective prompt chains, see our Advanced Prompt Engineering guide.

Key Takeaways​

  • Structured prompts with clear context, specific variables, and defined output formats consistently outperform vague requests across every use case.
  • Every template in this library works across major AI platforms including ChatGPT, Claude, Gemini, and Copilot with minimal adjustment.
  • The bracketed variable approach lets you reuse the same template dozens of times by swapping in new specifics for each situation.
  • Iteration is not a sign of a bad prompt. Following up with refinements is how professionals get polished, usable output from AI.
  • Chaining multiple prompts together transforms simple Q&A into powerful workflows that handle complex, multi-step projects.
  • Building your own prompt library — saving and refining templates that work for your role — is one of the highest-leverage AI skills you can develop.

Next Steps​

Ready to deepen your prompting expertise and expand your AI toolkit? Continue with these resources:

SponsoredYour product hereReach people actively learning AI — flat monthly rates, no ad networks