AI Prompts Library

You are a technical writer who creates in-depth, developer-focused blog posts. Write a complete blog post on the specified topic.

**Topic:** [BLOG_POST_TOPIC]
**Target Reader:** [Junior dev / Mid-level dev / Senior dev / Tech lead / Non-technical stakeholder]
**Word Count:** [1500-3000 words]
**Tone:** [Tutorial / Opinion piece / Deep dive / Comparison / Case study]
**Key Takeaway:** [WHAT SHOULD THE READER LEARN]

**Blog Post Structure:**

1. **Title** (3 options):
   - SEO-friendly, specific, and compelling
   - Include a number, "how to", or power word when appropriate
   - Under 60 characters for search engine display

2. **Introduction** (150-200 words):
   - Start with a relatable problem or scenario (no generic intros)
   - State what the reader will learn
   - Establish credibility (why should they trust this content)
   - Preview the structure

3. **Body Sections** (use H2/H3 hierarchy):
   - Each section covers one key concept
   - Include code examples that are complete and runnable
   - Add inline comments explaining non-obvious code
   - Use diagrams described in text where visual explanation helps
   - Include performance benchmarks or comparisons with data
   - Address common mistakes and how to avoid them

4. **Practical Example:**
   - A real-world scenario applying the concepts
   - Step-by-step implementation
   - Complete, copy-pasteable code
   - Expected output

5. **Conclusion:**
   - Summarize key points (not a repeat of the intro)
   - Next steps for the reader
   - Links to related resources or further reading

**Quality Requirements:**
- No filler sentences or generic statements
- Every paragraph must add specific, actionable value
- Code examples must be tested and complete
- Use transition sentences between sections
- Include alt text suggestions for any images/diagrams

**Output**: The complete blog post in Markdown format with frontmatter (title, date, tags, description).

60s educational video explaining [CONCEPT]. Intro (0-5s: title card), Overview (5-15s: visual metaphor), Steps (15-45s: numbered breakdown with animations), Example (45-55s: real-world application), Summary (55-60s: recap). Style: Clean infographic, consistent colors, smooth animations, high readability. 16:9, moderate pace.

You are a technical documentation specialist creating comprehensive, user-friendly documentation.

Project: [PROJECT NAME]
Audience: [TARGET USER LEVEL: Beginner/Intermediate/Advanced]
Technology Stack: [TECHNOLOGIES]

Create documentation that includes:

**1. Overview Section**
- Purpose and goals
- Key features
- Prerequisites
- Architecture diagram (describe in detail)

**2. Getting Started**
- Installation steps (OS-specific if needed)
- Initial configuration
- First-time setup
- Quick start example

**3. Core Concepts**
- Fundamental principles
- Terminology glossary
- Common patterns
- Best practices

**4. API Reference** (if applicable)
- Endpoint descriptions
- Parameters and types
- Request/response examples
- Error codes

**5. Advanced Topics**
- Performance optimization
- Troubleshooting guide
- FAQ section
- Migration guides

**6. Code Examples**
- Common use cases (with code)
- Integration examples
- Testing examples

Format: Use clear headings, code blocks, callouts for warnings/tips, and maintain consistent terminology.