AI Prompts Library

You are a presentation design consultant who creates compelling, structured presentation outlines. Design a presentation for the described topic and audience.

**Presentation Details:**
- Topic: [TOPIC]
- Audience: [WHO WILL ATTEND]
- Duration: [X minutes]
- Purpose: [Inform / Persuade / Train / Inspire / Sell]
- Format: [Keynote / Board meeting / Workshop / Webinar / Sales pitch]
- Key Message: [WHAT IS THE ONE THING THE AUDIENCE SHOULD REMEMBER]

**Generate a presentation outline with:**

1. **Slide-by-Slide Breakdown:**
   For each slide, provide:
   - Slide title
   - Key message (one sentence the slide communicates)
   - Bullet points or content elements
   - Visual suggestion (chart type, image description, diagram)
   - Speaker notes (what to say, not what is on the slide)
   - Time allocation

2. **Narrative Arc:**
   - Hook: Open with a surprising fact, question, or story
   - Problem: Establish the challenge or opportunity
   - Journey: Walk through insights, data, and analysis
   - Solution: Present the recommendation or key findings
   - Call to Action: What should the audience do next

3. **Slide Count Budget:**
   - Rule of thumb: 1 slide per 2 minutes
   - Title slide, agenda, Q&A, and closing do not count toward content
   - No more than 5 bullet points per slide
   - Data slides: one insight per chart

4. **Design Recommendations:**
   - Color scheme suggestion
   - Font pairing
   - Layout templates for different slide types
   - When to use animation (sparingly)

5. **Audience Engagement:**
   - Questions to ask the audience
   - Interactive moments (polls, show of hands)
   - Transition phrases between sections

**Output**: Complete slide-by-slide outline with speaker notes, visual descriptions, and timing for the entire presentation.

You are a newsletter strategist who builds engaged subscriber communities. Create a comprehensive newsletter content plan.

**Newsletter Details:**
- Newsletter Name: [NAME]
- Niche/Topic: [TOPIC_AREA]
- Target Subscriber: [WHO READS THIS]
- Frequency: [Weekly / Bi-weekly / Monthly]
- Monetization: [Sponsorship / Premium tier / Affiliate / Product promotion / None]
- Current Subscribers: [NUMBER]
- Growth Goal: [TARGET_SUBSCRIBERS in X_MONTHS]

**Generate:**

1. **Newsletter Format Template:**
   - Recurring sections (e.g., Main Story, Quick Takes, Tool of the Week, Quote, CTA)
   - Section descriptions and word count targets
   - Visual layout description
   - From name, subject line, and preview text strategy

2. **12-Issue Content Calendar:**
   For each issue:
   - Main topic/theme
   - Subject line (with A/B variant)
   - Key sections with brief descriptions
   - Guest feature or interview suggestion
   - Sponsor integration point (if applicable)

3. **Subject Line Formulas** (10 templates):
   - Curiosity-driven
   - Number-based
   - How-to
   - Contrarian
   - Personal story

4. **Growth Strategy:**
   - Cross-promotion tactics with other newsletters
   - Social media preview content strategy
   - Referral program design
   - Lead magnet ideas to attract subscribers
   - SEO-optimized archive strategy

5. **Engagement Optimization:**
   - Optimal send time and day analysis
   - Re-engagement sequence for inactive subscribers
   - Feedback collection methods
   - Community building tactics (Discord, Slack, or comments)

6. **Metrics to Track:**
   - Open rate, click rate, unsubscribe rate benchmarks
   - Subscriber growth rate
   - Revenue per subscriber
   - Engagement score calculation

**Output**: A complete content plan with the template, 12 issues mapped out, and growth strategy.

You are a senior engineer who writes clear, persuasive technical RFCs (Request for Comments). Create an RFC document for the described technical proposal.

**RFC Details:**
- Title: [PROPOSAL_TITLE]
- Author: [YOUR_NAME]
- Status: Draft
- Problem: [WHAT PROBLEM ARE WE SOLVING]
- Proposed Solution: [HIGH-LEVEL SOLUTION]
- Impact: [WHAT SYSTEMS/TEAMS ARE AFFECTED]

**RFC Document Structure:**

1. **Summary** (1 paragraph):
   - What is being proposed and why
   - Expected outcome

2. **Motivation:**
   - Current state and its problems
   - Business impact of the problem (cost, velocity, reliability)
   - Why we need to solve this now (urgency justification)
   - What happens if we do nothing

3. **Detailed Design:**
   - Architecture overview with component descriptions
   - Data flow and sequence descriptions
   - API changes or new APIs
   - Database schema changes
   - Configuration changes
   - Migration strategy

4. **Alternatives Considered:**
   - For each alternative:
     - Description of the approach
     - Pros and cons
     - Why it was not chosen
   - Include at minimum: the proposed solution, a simpler approach, a more complex approach, and "do nothing"

5. **Implementation Plan:**
   - Phases with milestones
   - Estimated effort (person-weeks)
   - Dependencies on other teams
   - Feature flag strategy
   - Rollout plan (percentage-based, canary, blue-green)

6. **Risks and Mitigations:**
   - Technical risks
   - Operational risks
   - Business risks
   - For each risk: likelihood, impact, and mitigation strategy

7. **Observability and Testing:**
   - Metrics to track success
   - Alerting conditions
   - Test plan (unit, integration, load, chaos)
   - Rollback plan

8. **Open Questions:**
   - Decisions that need input from reviewers
   - Areas of uncertainty

**Output**: Complete RFC document in Markdown format, ready for review.

Write press release:

**HEADLINE** - Benefit-focused, includes key news
**SUBHEAD** - Expand on headline
**DATELINE** - [CITY, STATE] – [DATE]
**LEAD** - Who, what, when, where, why in 2-3 sentences
**BODY** - Context, details, impact (3-4 paragraphs)
**QUOTE** - "[Compelling quote]" – [Name, Title]
**BOILERPLATE** - About [Company] (2-3 sentences)
**CONTACT** - [Media contact info]

AP Style, 400-500 words, newsworthy angle.

Grant proposal for [PROJECT]:

**Executive Summary** (1 page) - Mission, project overview, impact
**Statement of Need** - Problem + data + target population
**Project Description** - SMART goals, methodology, timeline
**Evaluation Plan** - Metrics, data collection, reporting
**Budget** - Itemized with justifications
**Organizational Capacity** - Track record, key personnel

Data-driven, mission-focused, funder-aligned.

[00:00] **COLD OPEN** - Hook/teaser
[00:30] **INTRO** - Theme, host intro, episode preview
[02:00] **MAIN CONTENT** - Segments with transitions
[XX:XX] **MID-ROLL AD** (if applicable)
[XX:XX] **CONCLUSION** - Recap, CTA, next episode tease
[XX:XX] **OUTRO** - Socials, music

**Production Notes**: [PAUSE], [EMPHASIZE], tone indicators
**Timing Marks**: Track length
**B-Roll**: Sound effects, music cues

Conversational, authentic, engaging.

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.