Strategic Prompt Patterns & Templates

"Create a comprehensive blog post about [TOPIC] with the following structure:

1. An engaging introduction that highlights the importance of [TOPIC] and establishes your credibility
2. [NUMBER] main sections, each covering a key aspect of [TOPIC]
3. For each section, include:
- A clear subheading
- Practical examples or case studies
- Actionable tips or insights
- Data points or statistics where relevant
4. A conclusion that summarizes key takeaways and includes a call to action

Additional guidelines:
- Target audience: [AUDIENCE DESCRIPTION]
- Tone: [TONE - e.g., professional, conversational, educational]
- Word count: Approximately [NUMBER] words
- Include [NUMBER] suggested meta tags for SEO"

"Write a compelling product description for [PRODUCT NAME], a [PRODUCT CATEGORY].

Key details:
- Main features: [LIST KEY FEATURES]
- Target user: [IDEAL CUSTOMER]
- Key benefit: [PRIMARY VALUE PROPOSITION]
- Price point: [PRICE RANGE]
- Differentiators: [WHAT MAKES THIS PRODUCT UNIQUE]

Structure the description as follows:
1. An attention-grabbing headline
2. An opening paragraph that creates emotional connection
3. Feature-benefit pairs (for each feature, explain the customer benefit)
4. Social proof element (suggested testimonial or use case)
5. Strong closing with call to action

The tone should be [BRAND VOICE] and the total length approximately [NUMBER] words."

"Create comprehensive documentation for the following API endpoint:

Endpoint: [ENDPOINT PATH]
Method: [HTTP METHOD]
Description: [BRIEF ENDPOINT DESCRIPTION]

Include the following sections:
1. Overview
2. Authentication requirements
3. Request parameters in table format (name, type, required, description)
4. Request body schema with example JSON
5. Response codes and their meanings
6. Response body schema with example JSON
7. Error handling information
8. Rate limiting details
9. At least 2 complete request-response examples
10. Common troubleshooting tips"

"Create a step-by-step tutorial about [TECHNICAL TOPIC] for [SKILL LEVEL] developers.

Include the following components:
1. Introduction explaining what the reader will learn and why it's valuable
2. Prerequisites (required knowledge, tools, dependencies)
3. Project setup instructions
4. Core content broken into sequential steps, each with:
- Clear instruction
- Code snippet (with syntax highlighting)
- Explanation of how the code works
- Expected outcome
5. Troubleshooting section addressing common issues
6. Summary of what was learned
7. Next steps or advanced topics to explore

Focus on best practices and explain the 'why' behind approaches taken."

"Conduct a comprehensive SWOT analysis for [COMPANY/PRODUCT], a [BRIEF DESCRIPTION].

For each quadrant, provide 4-6 bullet points with brief explanations:

STRENGTHS:
• Internal capabilities and resources that provide advantages
• Consider: brand reputation, proprietary technology, team expertise, financial resources

WEAKNESSES:
• Internal limitations that create disadvantages
• Consider: resource gaps, operational inefficiencies, product limitations, market positioning

OPPORTUNITIES:
• External factors that could be leveraged for growth
• Consider: market trends, competitor gaps, new technologies, regulatory changes

THREATS:
• External challenges that could negatively impact performance
• Consider: new competitors, changing customer preferences, economic factors, supply chain risks

After the quadrant analysis, provide:
1. A strategic assessment of the most critical 2-3 factors in each quadrant
2. Three actionable recommendations based on the SWOT insights"

"Create an executive summary for [PROJECT/REPORT NAME] that addresses [PRIMARY PURPOSE].

Structure the summary with these sections:

1. OVERVIEW (2-3 sentences):
• Core purpose and scope

2. KEY FINDINGS (3-5 bullet points):
• Most significant insights or results
• Include relevant metrics and their business impact

3. RECOMMENDATIONS (3-4 bullet points):
• Specific, actionable next steps
• Clear ownership and timeframes where relevant

4. BUSINESS IMPACT (2-3 sentences):
• Expected outcomes if recommendations are implemented
• Quantifiable benefits where possible

5. ADDITIONAL CONSIDERATIONS:
• Risks, dependencies, or resource requirements

The tone should be concise, data-driven, and focused on strategic implications. Total length should be approximately 350-500 words."

"Explain the concept of [COMPLEX TOPIC] at these three levels of understanding:

1. BEGINNER LEVEL:
• Explain it as if to a 12-year-old with no background knowledge
• Use simple analogies and everyday examples
• Avoid jargon and technical terms

2. INTERMEDIATE LEVEL:
• Explain to someone with basic field knowledge
• Introduce key terminology with clear definitions
• Connect with related concepts they might already understand
• Include practical applications

3. ADVANCED LEVEL:
• Explain to a professional in the field
• Deep dive into mechanics, theories, and nuances
• Reference latest research or developments
• Discuss complexities and edge cases
• Address common misconceptions at this level

For each level, end with 1-2 questions that would help the learner test their understanding."

"Create a detailed course outline for teaching [SUBJECT] to [TARGET AUDIENCE].

Course Parameters:
• Duration: [TOTAL LENGTH] (e.g., 8 weeks, 4 hours)
• Delivery format: [FORMAT] (e.g., video, workshop, text)
• Prerequisite knowledge: [PREREQUISITES]
• Learning objectives: [PRIMARY OUTCOMES]

Structure the outline as follows:

COURSE INTRODUCTION:
• Overview and relevance
• Learning path and expectations

For each module/unit (create [NUMBER] modules):
• Module title
• Duration
• Learning objectives for this module
• Topics covered (bullet points)
• Main activities or exercises
• Assessment method
• Resources needed

FINAL PROJECT/ASSESSMENT:
• Description
• Success criteria
• How it demonstrates mastery

Suggest 3-5 methods to accommodate different learning styles throughout the course."

"Create a structured data analysis report based on the following information about [DATASET/TOPIC]:

Data Sources:
• [LIST DATA SOURCES, SAMPLE SIZES, TIME PERIODS]

Metrics Analyzed:
• [LIST KEY METRICS AND WHY THEY MATTER]

Structure the report with these sections:

1. EXECUTIVE SUMMARY:
• Key findings and business implications in bullet form

2. METHODOLOGY:
• Data collection approach
• Analysis techniques used
• Limitations or caveats

3. FINDINGS (for each metric/area):
• Visual representation description (chart/graph type)
• Key observations
• Statistical significance notes
• Comparative analysis (benchmarks, previous periods)

4. INSIGHTS:
• Patterns and trends identified
• Correlations and potential causations
• Anomalies and their possible explanations

5. RECOMMENDATIONS:
• Data-driven suggestions
• Prioritized by impact and feasibility
• Metrics to track for each recommendation

6. NEXT STEPS:
• Follow-up analyses
• Implementation timeline
• Areas for further research"