You are a [Required: your role, e.g., "B2B SaaS account manager"] writing to [Required: recipient role, e.g., "enterprise decision-makers"].

Create a follow-up email with this structure:
- Subject line (under 50 characters)
- Opening: Reference [Required: previous interaction, e.g., "demo last Tuesday"]
- Body: Address [Required: specific pain point or interest mentioned, e.g., "reporting automation concerns"]
- Value: [Required: specific benefit, e.g., "reduces reporting time from 3 days to 2 hours"]
- CTA: [Required: specific action, e.g., "15-minute walkthrough this week"]
- Close: Offer to answer questions

Context: [Required: relationship stage, e.g., "attended demo but haven't signed up yet, evaluating 3 competitors, Q1 budget deadline in 6 weeks"]

Tone: [Required: select one - "professional but friendly" / "direct and concise" / "consultative and helpful"]

Constraints:
- [Required: word count, e.g., "200 words maximum"]
- Single CTA only
- Avoid: [Required: what to avoid, e.g., "sales jargon, multiple requests, assumptive closing"]

You are a [Required: analyst/consultant role, e.g., "business analyst preparing executive briefings"].

Create executive summary analyzing [Required: topic, e.g., "Q3 performance vs targets"].

Structure:
1. Key Insight (50 words): The one thing leadership needs to know
2. Supporting Data (100 words): [Required: 2-3 critical metrics with context]
3. Strategic Implications (100 words): What this means for [Required: business goal]
4. Recommended Actions (3 bullet points): Specific next steps

Audience: [Required: who reads this, e.g., "C-level executives who prioritize speed over detail"]

Context:
- Previous quarter: [Required: benchmark, e.g., "$2.3M revenue, 15% growth"]
- Current results: [Required: actual numbers]
- Key changes: [Required: what's different, e.g., "new enterprise sales focus, 2 major churns"]
- Stakes: [Required: why this matters, e.g., "board meeting next week"]

You are a [Required: role, e.g., "project manager"] creating agenda for [Required: meeting type, e.g., "quarterly planning meeting"].

Create structured agenda:
- Meeting goal: [Required: specific outcome, e.g., "finalize Q1 roadmap priorities"]
- Attendees: [Required: who's there and why, e.g., "product, engineering leads, CEO for final approval"]
- Duration: [Required: total time, e.g., "90 minutes"]

Agenda sections:
1. Context setting ([X] minutes): [Required: what background to cover]
2. Main discussion ([X] minutes): [Required: key decision or topic]
3. Decision points ([X] minutes): [Required: what needs approval]
4. Next steps ([X] minutes): Action items and ownership

Context:
- Previous meeting outcome: [Required: what happened last time]
- Open issues: [Required: what's unresolved]
- Constraints: [Required: deadlines, budget limits, dependencies]

Format: Time-boxed with clear decision points, action items assigned with owners

Constraints: Fit within [Required: duration]

You are a [Required: writer type, e.g., "B2B SaaS content strategist"] creating outline for [Required: topic].

Target audience: [Required: who reads this, e.g., "technical product managers evaluating AI tools"]

Create outline with:
1. Hook (why this matters now): [Required: timely angle or problem]
2. Core sections (3-5 main points):
   - Section 1: [Required: first key point]
   - Section 2: [Required: second key point]
   - Section 3: [Required: third key point]
   [Add sections as needed]
3. Actionable takeaway: What reader should do with this information

For each section include:
- Main argument
- Supporting evidence needed (data, examples, case studies)
- Potential reader objections to address

Context:
- Reader's expertise level: [Required: beginner/intermediate/expert]
- Reader's goal: [Required: what they're trying to accomplish]
- Competitive content: [Required: what already exists on this topic]

Style: [Required: publication reference, e.g., "Harvard Business Review: data-driven, executive focus"]

Constraints:
- Target length: [Required: word count]
- SEO keywords: [Required: 2-3 primary terms to include naturally]
- Avoid: [Required: topics or angles to exclude]

You are a [Required: role, e.g., "social media manager for B2B tech company"].

Create [Required: number]-post series about [Required: topic] for [Required: platform, e.g., "LinkedIn"].

For each post:
- Hook (first line that stops scroll)
- Core value (insight, tip, or framework)
- Supporting detail (example, data point, or story)
- CTA (engagement prompt or link)

Series theme: [Required: overarching message, e.g., "AI prompt mistakes costing teams time"]

Post topics:
1. [Required: first post angle]
2. [Required: second post angle]
3. [Required: third post angle]
[Add more as needed]

Audience: [Required: who follows you, e.g., "product managers and founders interested in AI productivity"]

Tone: [Required: voice, e.g., "helpful expert sharing practical insights, not salesperson"]

Constraints per post:
- [Required: character/word limit for platform]
- Include [Required: hashtag strategy, e.g., "3-5 relevant hashtags"]
- Avoid: [Required: what doesn't work, e.g., "corporate speak, excessive emoji, hard sells"]

You are a [Required: role, e.g., "technical writer documenting APIs for developers"].

Document [Required: API endpoint/feature name] for [Required: developer audience level, e.g., "backend engineers familiar with REST APIs but new to our platform"].

Structure:
1. Overview: What this endpoint does and why developers would use it
2. Authentication: [Required: auth method]
3. Endpoint: [Required: method and URL]
4. Parameters:
   - [Required: parameter name]: [Required: type, required/optional, description]
   [List all parameters]
5. Request example: [Required: working code sample in preferred language]
6. Response format: [Required: JSON structure with field descriptions]
7. Error codes: Common errors and how to handle them
8. Rate limits: [Required: if applicable]

Context:
- Use case: [Required: typical scenario where this is used]
- Prerequisites: [Required: what developers need set up first]
- Related endpoints: [Required: what else they might need]

Style: Technical precision, assume intelligent audience, include working examples

Constraints:
- Code examples in [Required: language, e.g., "Python and JavaScript"]

[Required: portrait type, e.g., "Corporate headshot" / "Dating profile photo" / "LinkedIn professional portrait"]

Subject: [Required: description, e.g., "confident professional in mid-30s, approachable expression"]

Style reference: [Required: photographer or aesthetic, e.g., "Peter Hurley corporate portrait style: warm approachable professional"]

Composition:
- Framing: [Required: e.g., "shoulders up, head and shoulders composition"]
- Subject position: [Required: e.g., "centered, direct eye contact with camera"]
- Background: [Required: e.g., "neutral grey slightly out of focus, subject sharp"]

Lighting:
- Direction: [Required: e.g., "soft beauty lighting from front-left"]
- Quality: [Required: e.g., "diffused, reduces harsh shadows"]
- Mood: [Required: e.g., "natural warm skin tones, professional but friendly"]

Context: [Required: use case, e.g., "LinkedIn profile for executive coach targeting corporate clients"]

Technical specs:
- Aspect ratio: [Required: e.g., "4:5 for Instagram/LinkedIn" or "1:1 for profile photos"]
- Style: [Required: for Midjourney, e.g., "--style raw --v 6"]

Avoid: [Required: what not to include, e.g., "harsh shadows, busy backgrounds, overly formal corporate stiffness"]

Product photography: [Required: item, e.g., "wireless earbuds in charging case"]

Style reference: [Required: e.g., "Apple product photography aesthetic: clean minimalist premium"]

Composition:
- Layout: [Required: e.g., "product centered occupying 60% of frame"]
- Angle: [Required: e.g., "45-degree angle showing case open with earbuds visible inside"]
- Background: [Required: e.g., "pure white seamless background RGB 255,255,255"]
- Negative space: [Required: e.g., "40% empty space right side for text overlay"]

Lighting:
- Setup: [Required: e.g., "soft directional from upper left"]
- Shadows: [Required: e.g., "gentle shadow beneath product for depth, not harsh"]
- Highlights: [Required: e.g., "subtle reflection on glossy surfaces"]

Context: [Required: platform/use, e.g., "e-commerce listing on Amazon, needs white background"]

Technical specs:
- Aspect ratio: [Required: e.g., "1:1 square for product listings"]
- Resolution: [Required: e.g., "2000x2000px minimum"]
- Focus: [Required: e.g., "sharp focus throughout, no blur"]
- [For Midjourney: "--ar 1:1 --style raw"]

Avoid: [Required: e.g., "colored backgrounds, multiple products, decorative elements, text overlays"]

[Required: duration, e.g., "15-second"] product demonstration video

Product: [Required: what you're showing]

Shot sequence:
1. ([X] sec): [Required: opening shot, e.g., "Close-up hands unboxing product, smooth reveal"]
2. ([X] sec): [Required: feature demo, e.g., "Hands demonstrating key feature in clear deliberate motion"]
3. ([X] sec): [Required: result/benefit, e.g., "Product in use, showing successful outcome"]

Camera/motion:
- Camera position: [Required: e.g., "overhead locked angle throughout"]
- Camera movement: [Required: e.g., "static camera, no pans or zooms"]
- Subject motion: [Required: e.g., "hands move deliberately, each action given time to register"]

Cinematic style: [Required: reference, e.g., "Apple product video aesthetic: clean minimal, smooth controlled"]

Lighting: [Required: e.g., "soft natural window light, warm color grade"]

Context: [Required: platform/audience, e.g., "landing page for skeptical enterprise buyers who need to see working product"]

Technical specs:
- Aspect ratio: [Required: e.g., "16:9 for web" or "9:16 for social stories"]
- Pacing: [Required: e.g., "slow deliberate, not rushed"]
- Frame rate: [Required: e.g., "24fps cinematic"]

Avoid: [Required: e.g., "voice-over, background music, text overlays during demo, rapid cuts"]

You are a [Required: analyst type, e.g., "market research analyst"] researching [Required: topic/market].

Research focus: [Required: specific question, e.g., "current state of AI coding assistants market"]

Information needed:
1. Market landscape: Key players, market share estimates, recent entrants
2. Product comparison: Features, pricing, target customers for top 3-5 products
3. Trends: Adoption patterns, growth indicators, emerging capabilities
4. Customer sentiment: Common complaints, praised features, switching patterns

Sources to prioritize:
- [Required: source types, e.g., "Recent industry reports (last 6 months), company blogs, user reviews, funding announcements"]
- Cite sources for significant claims

Context:
- Purpose: [Required: why you need this, e.g., "Evaluating whether to enter this market with $5M seed funding"]
- Decision timeline: [Required: when you need to decide]
- Specific concerns: [Required: what you're worried about, e.g., "market saturation, customer acquisition costs"]

Focus on: [Required: what matters most, e.g., "real-world production use cases, not marketing materials"]

Constraints:
- Time period: [Required: how recent, e.g., "last 6 months for trends, all available for fundamentals"]
- Depth: [Required: overview vs deep-dive, e.g., "high-level landscape not exhaustive analysis"]

You are a [Required: expert role with relevant experience].

Problem: [Required: specific problem to solve]

Think through this systematically:

Step 1: Define the problem precisely
- What exactly is wrong?
- What would success look like?
- What constraints exist?

Step 2: Identify root causes
- Why is this happening?
- What assumptions might be wrong?
- What's the evidence for each potential cause?

Step 3: Generate solution options
- What are 3-5 possible approaches?
- What are the tradeoffs of each?
- What resources would each require?

Step 4: Recommend approach
- Which option do you recommend and why?
- What are the key risks?
- What would you need to know to be more confident?

Context:
- Background: [Required: situation details]
- Constraints: [Required: what you cannot do]
- Previous attempts: [Required: what's been tried before]
- Stakeholders: [Required: who cares about this and what they prioritize]