The Ultimate Guide to Claude AI Prompts (100+ Examples)

<task>Review the following code for security vulnerabilities, performance issues, and best practices</task>

<code>
{{PASTE_YOUR_CODE_HERE}}
</code>

<review_criteria>
  <security>Check for SQL injection, XSS, CSRF, and authentication issues</security>
  <performance>Identify bottlenecks, N+1 queries, and inefficient algorithms</performance>
  <maintainability>Assess code clarity, naming conventions, and documentation</maintainability>
  <best_practices>Compare against industry standards for this language/framework</best_practices>
</review_criteria>

<output_format>
For each issue found, provide:
1. Severity (Critical/High/Medium/Low)
2. Location (file and line number)
3. Explanation of the issue
4. Code example showing the fix
</output_format>

<task>Refactor this legacy code to modern standards while maintaining 100% backward compatibility</task>

<legacy_code>
{{PASTE_LEGACY_CODE_HERE}}
</legacy_code>

<refactoring_goals>
  <goal>Replace deprecated functions with modern equivalents</goal>
  <goal>Improve variable naming and code structure</goal>
  <goal>Add type hints and documentation</goal>
  <goal>Reduce complexity and duplication</goal>
  <goal>Maintain exact same public API</goal>
</refactoring_goals>

<constraints>
  <constraint>Must pass all existing tests</constraint>
  <constraint>No breaking changes to public interfaces</constraint>
  <constraint>Explain each refactoring decision</constraint>
</constraints>

Show before/after comparison for each major change.

<thinking>
Analyze the error systematically:
1. Parse the stack trace to identify the failure point
2. Review the error message for root cause hints
3. Check for common patterns (null reference, race condition, etc.)
4. Propose debugging steps and potential fixes
</thinking>

<task>Debug this production error</task>

<error_log>
{{PASTE_ERROR_LOGS_HERE}}
</error_log>

<context>
  <environment>Production (Node.js 18, PostgreSQL 14)</environment>
  <when_occurred>{{TIMESTAMP_OR_PATTERN}}</when_occurred>
  <frequency>{{HOW_OFTEN_IT_HAPPENS}}</frequency>
</context>

Provide:
1. Root cause analysis
2. Immediate hotfix (if critical)
3. Long-term solution
4. Prevention strategy (tests, monitoring, etc.)

<task>Generate comprehensive unit tests for this function</task>

<code>
{{PASTE_FUNCTION_HERE}}
</code>

<test_requirements>
  <framework>{{Jest/Pytest/JUnit/etc}}</framework>
  <coverage>
    <requirement>Test happy path</requirement>
    <requirement>Test edge cases (null, empty, boundary values)</requirement>
    <requirement>Test error conditions</requirement>
    <requirement>Test async behavior (if applicable)</requirement>
  </coverage>
  <style>Use Arrange-Act-Assert pattern</style>
</test_requirements>

Include:
- Test descriptions that explain WHAT is being tested
- Mock setup for external dependencies
- Assertion explanations
- Code coverage report estimate

Generate OpenAPI 3.0 documentation for this API endpoint:

{{PASTE_ENDPOINT_CODE_HERE}}

Include:
- Endpoint path and HTTP method
- Request parameters (path, query, body)
- Request body schema (with examples)
- Response schemas (200, 400, 401, 500)
- Authentication requirements
- Example requests using curl
- Example responses (JSON)

Format as valid OpenAPI YAML.

<task>Optimize this slow SQL query</task>

<query>
{{PASTE_SQL_QUERY_HERE}}
</query>

<context>
  <database>{{PostgreSQL/MySQL/etc}}</database>
  <table_size>{{APPROXIMATE_ROW_COUNT}}</table_size>
  <current_execution_time>{{TIME_IN_MS}}</current_execution_time>
  <indexes>{{LIST_EXISTING_INDEXES}}</indexes>
</context>

<optimization_checklist>
  <check>Identify missing indexes</check>
  <check>Eliminate N+1 queries</check>
  <check>Reduce subqueries and joins</check>
  <check>Use appropriate JOIN types</check>
  <check>Add query hints if needed</check>
</optimization_checklist>

Provide:
1. Optimized query
2. Index recommendations (CREATE INDEX statements)
3. EXPLAIN ANALYZE comparison (before/after)
4. Expected performance improvement

Generate a comprehensive README.md for this codebase:

{{PASTE_MAIN_FILE_OR_OVERVIEW}}

Include these sections:
1. Project Title & Description
2. Features (bullet list)
3. Installation (step-by-step)
4. Usage (code examples)
5. Configuration (environment variables)
6. API Reference (if applicable)
7. Contributing guidelines
8. License

Use proper markdown formatting with code blocks, badges, and emoji where appropriate. Keep it concise but complete.

<task>Convert this {{SOURCE_LANGUAGE}} code to {{TARGET_LANGUAGE}}</task>

<source_code language="{{SOURCE_LANGUAGE}}">
{{PASTE_CODE_HERE}}
</source_code>

<conversion_rules>
  <rule>Use idiomatic {{TARGET_LANGUAGE}} patterns</rule>
  <rule>Maintain exact same logic and behavior</rule>
  <rule>Add type hints/annotations where supported</rule>
  <rule>Use modern {{TARGET_LANGUAGE}} features</rule>
  <rule>Include comments explaining non-obvious conversions</rule>
</conversion_rules>

<output>
  <converted_code>Full converted code with comments</converted_code>
  <dependencies>List of libraries/packages needed</dependencies>
  <differences>Key differences in approach between languages</differences>
</output>

Generate a conventional commit message for this git diff:

{{PASTE_GIT_DIFF_HERE}}

Follow the Conventional Commits spec:
- Type: feat/fix/docs/style/refactor/test/chore
- Scope: affected component (optional)
- Subject: imperative mood, no period, max 50 chars
- Body: explain WHAT and WHY (not HOW), wrap at 72 chars
- Footer: breaking changes, issue references

Example format:
feat(auth): add OAuth2 social login

Add Google and GitHub OAuth providers using passport.js.
Users can now sign in without creating a password.

BREAKING CHANGE: /login endpoint now requires provider parameter
Closes #123

<task>Generate an optimized Dockerfile for this project</task>

<project>
  <language>{{Node.js/Python/Go/etc}}</language>
  <framework>{{Express/Flask/etc}}</framework>
  <dependencies>{{package.json/requirements.txt/go.mod}}</dependencies>
</project>

<requirements>
  <requirement>Multi-stage build to minimize image size</requirement>
  <requirement>Security best practices (non-root user, minimal base image)</requirement>
  <requirement>Efficient caching of dependencies</requirement>
  <requirement>Health check endpoint</requirement>
  <requirement>Production-ready (no dev dependencies)</requirement>
</requirements>

Include:
- Dockerfile with comments explaining each step
- .dockerignore file
- docker-compose.yml for local development
- Estimated final image size

Analyze the cyclomatic complexity and maintainability of this code:

{{PASTE_CODE_HERE}}

For each function/method, calculate:
1. Cyclomatic Complexity (McCabe score)
2. Lines of Code (LOC)
3. Number of parameters
4. Depth of nesting

Flag functions that exceed:
- Complexity > 10 (refactor recommended)
- LOC > 50 (consider splitting)
- Parameters > 4 (use object/struct)
- Nesting > 3 (extract methods)

For each flagged function, suggest specific refactoring strategies.

Review these dependencies for security vulnerabilities:

{{PASTE_package.json_OR_requirements.txt}}

For each dependency, check:
1. Known CVEs (critical/high severity)
2. Outdated versions (compare to latest stable)
3. Unmaintained packages (last update > 2 years)
4. License compatibility issues
5. Deprecated packages with suggested alternatives

Prioritize findings by severity:
🔴 Critical: Remote code execution, SQL injection
🟠 High: XSS, authentication bypass
🟡 Medium: DoS, information disclosure
🔵 Low: Minor issues

Provide upgrade commands (npm update, pip install --upgrade, etc.)

<task>Analyze this performance profile and identify bottlenecks</task>

<profile_data>
{{PASTE_PROFILER_OUTPUT_HERE}}
</profile_data>

<analysis_criteria>
  <criterion>Functions consuming >5% total CPU time</criterion>
  <criterion>Functions called >10,000 times</criterion>
  <criterion>I/O blocking operations</criterion>
  <criterion>Memory leaks (growing allocations)</criterion>
  <criterion>Synchronous operations in async code</criterion>
</analysis_criteria>

Provide:
1. Top 10 bottlenecks ranked by impact
2. Root cause for each bottleneck
3. Optimization strategy (caching, async, algorithm change)
4. Code examples showing before/after
5. Expected performance gain estimate

Generate TypeScript types/interfaces from this JSON data:

{{PASTE_JSON_EXAMPLE}}

Requirements:
- Use interfaces for objects, types for unions
- Make optional fields explicit (with ?)
- Use readonly where data shouldn't mutate
- Add JSDoc comments for complex fields
- Handle nested objects and arrays
- Infer union types from examples (e.g., "status": "active" | "inactive")

Also generate:
- Zod schema for runtime validation
- Type guard functions (isTypeX)
- Example usage showing type safety

Explain this regex pattern in plain English:

{{PASTE_REGEX_PATTERN}}

Provide:
1. Plain English explanation (what it matches)
2. Step-by-step breakdown of each component
3. Example strings that MATCH
4. Example strings that DON'T match
5. Common use cases for this pattern
6. Performance considerations (backtracking risks)
7. Alternative patterns (if simpler options exist)

Format the breakdown with visual grouping:
(example) - Explanation
[example] - Explanation
\d{3} - Explanation

<task>Generate a CI/CD pipeline for this project</task>

<project>
  <type>{{web-app/api/library/etc}}</type>
  <language>{{Node.js/Python/Go/etc}}</language>
  <tests>{{jest/pytest/go-test}}</tests>
  <deploy_target>{{AWS/Vercel/Docker/etc}}</deploy_target>
</project>

<pipeline_stages>
  <stage>Install dependencies (with caching)</stage>
  <stage>Run linters (ESLint, Prettier, etc.)</stage>
  <stage>Run tests (with coverage report)</stage>
  <stage>Build artifacts</stage>
  <stage>Security scan (Snyk, npm audit)</stage>
  <stage>Deploy to staging (on main branch)</stage>
  <stage>Deploy to production (on tags only)</stage>
</pipeline_stages>

Generate:
- GitHub Actions .yml file OR GitLab .gitlab-ci.yml
- Environment variables documentation
- Secret management strategy
- Rollback procedure

Review this code for common code smells and anti-patterns:

{{PASTE_CODE_HERE}}

Check for:
- 🚩 Long functions (>50 lines)
- 🚩 Long parameter lists (>4 params)
- 🚩 Deeply nested conditionals (>3 levels)
- 🚩 Duplicated code (DRY violations)
- 🚩 Large classes (God objects)
- 🚩 Feature envy (using another object's data excessively)
- 🚩 Primitive obsession (using primitives instead of objects)
- 🚩 Magic numbers (unexplained constants)
- 🚩 Dead code (unused variables/functions)

For each smell found:
1. Location in code
2. Severity (Critical/High/Medium/Low)
3. Explanation of why it's problematic
4. Refactoring suggestion with code example

<thinking>
Analyze the algorithm step-by-step:
1. Count loops and their nesting levels
2. Identify recursive calls and their branching
3. Check data structure operations (hash lookup, array iteration, etc.)
4. Calculate worst-case, average-case, and best-case scenarios
</thinking>

<task>Calculate time and space complexity</task>

<code>
{{PASTE_ALGORITHM_HERE}}
</code>

Provide:
1. Time Complexity
   - Best case: O(?)
   - Average case: O(?)
   - Worst case: O(?)
2. Space Complexity: O(?)
3. Step-by-step complexity derivation
4. Comparison to optimal complexity for this problem
5. Optimization suggestions (if not optimal)

Audit this .env file for security and configuration issues:

{{PASTE_.env_OR_.env.example}}

Check for:
1. 🔐 Secrets committed to git (API keys, passwords, tokens)
2. ⚠️ Missing required variables (based on code usage)
3. 📝 Poor naming conventions (use SCREAMING_SNAKE_CASE)
4. 🔗 Hardcoded URLs (should be environment-specific)
5. 🚨 Default/example values in production
6. 📋 Missing .env.example file

Provide:
- List of issues found (prioritized by severity)
- Secure environment variable management recommendations
- .env.example template (with example values, no real secrets)
- Documentation for each variable (purpose, format, where to get value)

Generate a Mermaid diagram showing the architecture of this code:

{{PASTE_CODE_OR_FILE_LIST}}

Create diagrams for:
1. Class/Component diagram (relationships, inheritance)
2. Sequence diagram (for main user flow)
3. Data flow diagram (how data moves through the system)

Use Mermaid syntax:
```mermaid
classDiagram
  class User {
    +string email
    +login()
  }
  User --> AuthService
```

Focus on:
- High-level architecture (not every function)
- Key relationships and dependencies
- Data flow for critical paths
- External integrations (APIs, databases)

<task>Write a comprehensive blog post</task>

<topic>{{YOUR_TOPIC_HERE}}</topic>

<requirements>
  <length>2,000-2,500 words</length>
  <tone>{{Professional/Conversational/Technical}}</tone>
  <audience>{{Target reader: CMOs, developers, etc.}}</audience>
  <seo_keyword>{{Primary keyword to target}}</seo_keyword>
</requirements>

<structure>
  <section>Hook/Introduction (150 words)</section>
  <section>Problem/Context (300 words)</section>
  <section>Main Content (1,500 words with subheadings)</section>
  <section>Examples/Case Studies (300 words)</section>
  <section>Actionable Takeaways (200 words)</section>
  <section>Conclusion with CTA (150 words)</section>
</structure>

<seo_checklist>
  <item>Include keyword in H1, first paragraph, and 2-3 subheadings</item>
  <item>Use H2, H3 subheadings for scannability</item>
  <item>Add internal links (use {{LINK_PLACEHOLDER}})</item>
  <item>Include bullet points and numbered lists</item>
  <item>Write meta description (150-160 chars)</item>
</seo_checklist>

Output markdown format with proper heading hierarchy.

<task>Write technical documentation for this feature</task>

<feature>
  <name>{{Feature Name}}</name>
  <description>{{Brief description}}</description>
  <target_user>{{Developer/End-user/Admin}}</target_user>
</feature>

<documentation_sections>
  <section name="Overview">What it does and why it's useful</section>
  <section name="Prerequisites">Requirements before using</section>
  <section name="Quick Start">Minimal example (copy-paste ready)</section>
  <section name="Detailed Guide">Step-by-step with screenshots placeholders</section>
  <section name="Configuration">All options explained</section>
  <section name="Examples">3-5 real-world use cases</section>
  <section name="Troubleshooting">Common errors and solutions</section>
  <section name="FAQ">5 frequently asked questions</section>
  <section name="API Reference">If applicable</section>
</documentation_sections>

<style>
  <instruction>Use second person ("you")</instruction>
  <instruction>Short paragraphs (2-3 sentences max)</instruction>
  <instruction>Code examples with syntax highlighting hints</instruction>
  <instruction>Callout boxes for warnings/tips/notes</instruction>
</style>

Proofread and edit this text for:

{{PASTE_TEXT_HERE}}

Check for:
1. Grammar & Spelling
   - Subject-verb agreement
   - Punctuation errors
   - Typos and misspellings

2. Clarity & Conciseness
   - Eliminate jargon and buzzwords
   - Remove redundancy
   - Simplify complex sentences

3. Style & Tone
   - Consistent voice (active vs passive)
   - Appropriate formality level
   - Smooth transitions between paragraphs

4. Readability
   - Vary sentence length
   - Break up long paragraphs
   - Add subheadings if needed

Output:
- Edited version (show changes with strikethrough and highlights)
- Summary of major changes
- Readability score (Flesch-Kincaid)

<task>Write landing page copy for this product</task>

<product>
  <name>{{Product Name}}</name>
  <description>{{What it does}}</description>
  <target_audience>{{Who it's for}}</target_audience>
  <unique_value>{{Main benefit / differentiator}}</unique_value>
  <pricing>{{Free/Paid/Freemium}}</pricing>
</product>

<sections>
  <hero>
    <headline>Benefit-driven (not feature-driven)</headline>
    <subheadline>Clarify what problem you solve</subheadline>
    <cta>Primary call-to-action button text</cta>
  </hero>

  <problem>
    Paint the pain point (3-4 bullet points)
  </problem>

  <solution>
    Introduce your product as the solution
  </solution>

  <features>
    3 key features with benefit-focused descriptions
  </features>

  <social_proof>
    Testimonial placeholders with realistic quotes
  </social_proof>

  <pricing_cta>
    Urgency-driven CTA section
  </pricing_cta>
</sections>

<copywriting_principles>
  <principle>Lead with benefits, not features</principle>
  <principle>Use power words (proven, guaranteed, exclusive)</principle>
  <principle>Address objections preemptively</principle>
  <principle>Create urgency (limited time, social proof)</principle>
</copywriting_principles>

<task>Write an email newsletter</task>

<newsletter>
  <theme>{{Weekly tips / Product updates / Industry news}}</theme>
  <audience>{{Subscribers description}}</audience>
  <goal>{{Educate / Promote / Engage}}</goal>
</newsletter>

<structure>
  <subject_line>3 options (50 chars max, A/B test ready)</subject_line>
  <preview_text>80 chars that complement subject line</preview_text>
  <greeting>Personalized opener</greeting>
  <main_content>
    <section type="story">Hook with anecdote or case study</section>
    <section type="value">Main tip/update/news (300 words)</section>
    <section type="cta">Clear call-to-action</section>
  </main_content>
  <secondary_content>
    <item>Quick tip #1</item>
    <item>Quick tip #2</item>
    <item>Resource link</item>
  </secondary_content>
  <signature>Friendly sign-off with author name</signature>
</structure>

<style>
  <tone>Conversational, like writing to a friend</tone>
  <length>400-600 words total</length>
  <formatting>Short paragraphs, emoji where appropriate</formatting>
</style>

Repurpose this content into multiple formats:

{{PASTE_ORIGINAL_CONTENT}}

Create:

1. Twitter Thread (8-10 tweets)
   - Hook tweet with thread announcement
   - 6-8 value tweets
   - CTA tweet with link

2. LinkedIn Post (1,200-1,500 chars)
   - Hook first line
   - Storytelling format
   - Hashtags and CTA

3. Instagram Caption (300-500 words)
   - Attention-grabbing first line
   - Line breaks for readability
   - 5-7 relevant hashtags

4. YouTube Video Script (5-7 min)
   - Intro/hook (30 sec)
   - Main points with timestamps
   - Outro with CTA

5. Infographic Outline
   - Title
   - 5 key stats/points
   - Visual hierarchy suggestions

For each format, explain what was adapted and why.

<task>Generate SEO metadata for this page</task>

<page_content>
{{PASTE_PAGE_CONTENT_OR_SUMMARY}}
</page_content>

<target_keyword>{{PRIMARY_KEYWORD}}</target_keyword>
<secondary_keywords>{{KEYWORD_2}}, {{KEYWORD_3}}</secondary_keywords>

<output>
  <title_tag>
    - Include primary keyword near the beginning
    - 50-60 characters
    - Provide 3 variations for A/B testing
  </title_tag>

  <meta_description>
    - Include primary and secondary keywords naturally
    - 150-160 characters
    - Compelling CTA or benefit statement
    - Provide 3 variations
  </meta_description>

  <h1_tag>
    Single H1 with primary keyword
  </h1_tag>

  <schema_markup>
    JSON-LD structured data (Article, Product, FAQ, or appropriate type)
  </schema_markup>

  <og_tags>
    Open Graph tags for social sharing
  </og_tags>
</output>

Ensure all metadata is:
- Unique (not duplicating other pages)
- Compelling (high CTR potential)
- Keyword-optimized without stuffing

<task>Write a grant proposal</task>

<project>
  <title>{{Project Name}}</title>
  <organization>{{Your organization}}</organization>
  <funding_amount>{{Requested amount}}</funding_amount>
  <duration>{{Project timeline}}</duration>
</project>

<proposal_sections>
  <executive_summary>
    200-word overview hitting all key points
  </executive_summary>

  <problem_statement>
    Clearly define the problem with data and citations
  </problem_statement>

  <goals_objectives>
    SMART goals (Specific, Measurable, Achievable, Relevant, Time-bound)
  </goals_objectives>

  <methodology>
    Step-by-step approach to achieving goals
  </methodology>

  <evaluation_plan>
    How success will be measured (KPIs, metrics)
  </evaluation_plan>

  <budget_justification>
    Line-item budget with rationale for each expense
  </budget_justification>

  <organizational_capacity>
    Why your org is qualified (experience, team, past success)
  </organizational_capacity>

  <sustainability>
    Long-term plan after funding period ends
  </sustainability>
</proposal_sections>

<style>
  <tone>Professional, data-driven, persuasive</tone>
  <citations>Include placeholder for citations [1]</citations>
  <length>Adjust to funder requirements</length>
</style>

<task>Write a customer case study</task>

<customer>
  <name>{{Company Name}}</name>
  <industry>{{Industry}}</industry>
  <size>{{Company size}}</size>
  <challenge>{{What problem they faced}}</challenge>
  <solution>{{How your product helped}}</solution>
  <results>{{Quantifiable outcomes}}</results>
</customer>

<case_study_structure>
  <section name="Executive Summary">
    - Customer name and industry
    - Challenge in one sentence
    - Solution in one sentence
    - Key results (3 metrics with % improvement)
  </section>

  <section name="About the Customer">
    Background on their business and context
  </section>

  <section name="The Challenge">
    Paint the pain point in detail (quote from customer if possible)
  </section>

  <section name="The Solution">
    How they implemented your product (step-by-step)
  </section>

  <section name="The Results">
    Quantifiable outcomes with before/after comparison
    Include customer quote praising the solution
  </section>

  <section name="Key Takeaways">
    3 bullet points for quick scanning
  </section>
</case_study_structure>

<formatting>
  - Pull quotes in sidebar for visual interest
  - Stats highlighted in callout boxes
  - Before/after comparison table
  - Customer logo and photo placeholders
</formatting>

<task>Write a press release</task>

<announcement>
  <type>{{Product Launch / Funding Round / Partnership / Award}}</type>
  <company>{{Your Company Name}}</company>
  <details>{{Key details of announcement}}</details>
  <date>{{Release date}}</date>
</announcement>

<press_release_format>
  <header>
    FOR IMMEDIATE RELEASE
    Contact information
  </header>

  <headline>
    Attention-grabbing, newsworthy (80 chars max)
  </headline>

  <subheadline>
    Expand on headline with key detail
  </subheadline>

  <dateline>
    CITY, STATE, Date –
  </dateline>

  <lead_paragraph>
    Who, what, when, where, why in first 2-3 sentences
  </lead_paragraph>

  <body_paragraphs>
    - Paragraph 2: Details and context
    - Paragraph 3: Quote from CEO/founder
    - Paragraph 4: Additional information
    - Paragraph 5: Quote from partner/customer (if applicable)
  </body_paragraphs>

  <boilerplate>
    "About [Company]" section (100 words)
  </boilerplate>

  <media_contact>
    Contact info for press inquiries
  </media_contact>
</press_release_format>

<style>
  <tone>Newsworthy, factual, third-person</tone>
  <length>400-600 words</length>
  <formatting>Inverted pyramid (most important info first)</formatting>
</style>

Write a product description for:

{{PRODUCT_NAME}}

Product details:
{{PASTE_PRODUCT_SPECS_OR_FEATURES}}

Target audience: {{WHO_BUYS_THIS}}

Structure:
1. Headline (Benefit-driven, not just product name)
2. Opening hook (Why they need this)
3. Key features (3-5 bullet points starting with benefit, not feature)
4. Use cases / Who it's for
5. Specifications (technical details table)
6. Trust signals (warranty, guarantees, certifications)
7. Call-to-action

Copywriting rules:
- Lead with benefits (what customer gains)
- Use sensory words (smooth, crisp, effortless)
- Address objections (size concerns, compatibility, etc.)
- Create urgency if appropriate (limited stock, sale ends)
- SEO-friendly (naturally include product keywords)

Length: 200-300 words (scannable but complete)
Tone: {{Luxury / Casual / Technical / Playful}}

<task>Create a 30-day social media content calendar</task>

<brand>
  <name>{{Brand Name}}</name>
  <industry>{{Industry}}</industry>
  <voice>{{Brand voice: Professional/Casual/Witty/etc}}</voice>
  <goals>{{Awareness/Engagement/Sales}}</goals>
</brand>

<platforms>
  <platform>Twitter (daily)</platform>
  <platform>LinkedIn (3x/week)</platform>
  <platform>Instagram (5x/week)</platform>
</platforms>

<content_pillars>
  <pillar weight="40%">Educational content (tips, how-tos)</pillar>
  <pillar weight="30%">Promotional (product features, offers)</pillar>
  <pillar weight="20%">Engagement (questions, polls, UGC)</pillar>
  <pillar weight="10%">Company culture (behind-the-scenes)</pillar>
</content_pillars>

<calendar_format>
For each day, provide:
- Date
- Platform
- Post type (image/video/carousel/text)
- Caption (platform-appropriate length)
- Hashtags (5-7 relevant tags)
- Call-to-action
- Visual description (for design team)
- Best posting time
</calendar_format>

Include variety: quotes, questions, stats, stories, memes, user-generated content.

<task>Write a white paper</task>

<topic>{{Research Topic or Industry Trend}}</topic>

<audience>
  <role>{{Decision-makers / Technical audience / General public}}</role>
  <knowledge_level>{{Beginner / Intermediate / Expert}}</knowledge_level>
</audience>

<white_paper_structure>
  <section name="Title Page">
    Compelling title and subtitle
  </section>

  <section name="Executive Summary" pages="1">
    Key findings and recommendations (can be read standalone)
  </section>

  <section name="Introduction" pages="1-2">
    Problem statement, scope, and methodology
  </section>

  <section name="Background/Context" pages="2-3">
    Industry landscape and why this topic matters
  </section>

  <section name="Main Analysis" pages="5-7">
    Detailed research findings with data, charts, examples
    (Use subheadings to break into digestible sections)
  </section>

  <section name="Recommendations" pages="2-3">
    Actionable insights based on findings
  </section>

  <section name="Conclusion" pages="1">
    Summary and call-to-action
  </section>

  <section name="References">
    Citations in APA format
  </section>
</white_paper_structure>

<style>
  <tone>Authoritative, data-driven, objective</tone>
  <length>10-15 pages (3,000-5,000 words)</length>
  <visuals>Include placeholders for charts, graphs, infographics</visuals>
  <citations>Use [1], [2] format for references</citations>
</style>

<task>Write a video script</task>

<video>
  <type>{{Explainer / Tutorial / Product Demo / Brand Story}}</type>
  <platform>{{YouTube / TikTok / Instagram Reels / LinkedIn}}</platform>
  <duration>{{Target length in minutes}}</duration>
  <goal>{{Educate / Sell / Entertain / Inspire}}</goal>
</video>

<script_format>
  <scene number="1" duration="0:00-0:10">
    <visual>Description of what's on screen</visual>
    <audio>
      <voiceover>Narration text</voiceover>
      <music>Background music notes</music>
      <sfx>Sound effects</sfx>
    </audio>
    <text_overlay>On-screen text</text_overlay>
  </scene>

  <!-- Repeat for each scene -->
</script_format>

<structure>
  <hook duration="0:00-0:10">Grab attention in first 3 seconds</hook>
  <intro duration="0:10-0:30">What the video is about</intro>
  <body duration="0:30-[MAIN]">Main content with clear sections</body>
  <cta duration="[END-0:15]-[END]">Clear call-to-action</cta>
  <outro duration="[LAST 5s]">Subscribe/follow reminder</outro>
</structure>

<platform_specs>
  - YouTube: Longer form, detailed, SEO-optimized title
  - TikTok/Reels: Fast-paced, trending sounds, captions required
  - LinkedIn: Professional, value-driven, caption as standalone post
</platform_specs>

Include: timestamps, shot descriptions, voiceover text, B-roll suggestions, graphics/animations needed.

Generate 20 tagline options for:

Company: {{COMPANY_NAME}}
Industry: {{INDUSTRY}}
Value proposition: {{WHAT_MAKES_YOU_UNIQUE}}
Target audience: {{WHO_YOU_SERVE}}
Brand personality: {{Innovative/Trustworthy/Bold/Playful/etc}}

Tagline criteria:
- 3-7 words max
- Memorable and unique
- Communicates benefit or emotion
- Easy to say out loud
- Not cliché or generic
- Differentiates from competitors

Provide taglines in these categories:
1. Benefit-focused (what customer gets)
2. Aspiration-focused (what customer becomes)
3. Challenge-focused (problem you solve)
4. Action-focused (imperative statements)
5. Emotional-focused (feeling you create)

For top 5 favorites, explain:
- Why it works
- Emotional resonance
- Potential trademark concerns

<task>Generate FAQ section</task>

<product_or_service>
  <name>{{Product/Service Name}}</name>
  <description>{{What it does}}</description>
  <target_users>{{Who uses it}}</target_users>
</product_or_service>

<context>
  <common_questions>{{List any questions you frequently get}}</common_questions>
  <pain_points>{{Common objections or concerns}}</pain_points>
</context>

<faq_categories>
  <category name="General">
    Generate 5-7 basic questions about what it is, who it's for, how it works
  </category>

  <category name="Pricing & Plans">
    Generate 5 questions about cost, payment, refunds, plan differences
  </category>

  <category name="Technical">
    Generate 5 questions about setup, compatibility, integrations, requirements
  </category>

  <category name="Troubleshooting">
    Generate 5 common problems and solutions
  </category>

  <category name="Account & Billing">
    Generate 5 questions about account management, cancellation, billing
  </category>
</faq_categories>

<answer_format>
  - Keep answers concise (2-4 sentences)
  - Link to detailed docs where appropriate (use placeholder)
  - Address the emotion behind the question (reassure concerns)
  - Use second person ("you")
</answer_format>

Total: 25-30 questions. Format in collapsible accordion style (markdown).

Help me craft a story using the Story Brand framework:

Topic/Theme: {{WHAT_YOUR_STORY_IS_ABOUT}}

Fill in these story elements:

1. THE CHARACTER (Hero)
   Who is the protagonist? (Usually your customer, not your brand)
   What do they want?

2. THE PROBLEM
   External problem: (visible, physical problem)
   Internal problem: (how the external problem makes them feel)
   Philosophical problem: (why it's unjust or wrong)

3. THE GUIDE (Your Brand)
   Empathy: (show you understand their problem)
   Authority: (credentials, experience, social proof)

4. THE PLAN
   Process plan: (3-4 simple steps to work with you)
   Agreement plan: (alleviate fears - money-back guarantee, etc.)

5. CALL TO ACTION
   Direct CTA: (specific action to take now)
   Transitional CTA: (low-stakes nurture offer - free guide, etc.)

6. SUCCESS
   What does their life look like after using your solution?
   (Paint a vivid before/after picture)

7. FAILURE
   What's at stake if they don't solve this problem?
   (Help them see the cost of inaction)

Output: Full narrative story (500-800 words) incorporating all elements.

<task>Optimize this LinkedIn profile</task>

<current_profile>
  <headline>{{CURRENT_HEADLINE}}</headline>
  <about>{{CURRENT_ABOUT_SECTION}}</about>
  <experience>{{BRIEF_WORK_HISTORY}}</experience>
</current_profile>

<goals>
  <goal>Attract {{recruiters/clients/partners}}</goal>
  <goal>Rank for keywords: {{LIST_TARGET_KEYWORDS}}</goal>
  <goal>Showcase expertise in {{YOUR_EXPERTISE}}</goal>
</goals>

<optimized_sections>
  <headline max_chars="220">
    - Include primary keyword
    - Benefit statement (value you provide)
    - Social proof or unique qualifier
    - Example: "Growth Marketer | Helped 50+ SaaS Companies Scale to $1M ARR | Speaker & Consultant"
  </headline>

  <about max_chars="2600">
    Structure:
    - Hook (first 2 sentences visible before "see more")
    - What you do and who you help
    - Your unique approach or methodology
    - Key achievements (with numbers)
    - Skills and expertise (include keywords naturally)
    - Call-to-action (how to work with you)
    - Contact info
  </about>

  <featured_section>
    Recommend 3-5 pieces of content to feature (articles, projects, media)
  </featured_section>

  <skills>
    Top 10 skills to add (prioritize searchable keywords)
  </skills>
</optimized_sections>

<seo_tips>
  - Repeat keywords 2-3 times naturally
  - Use section headings in About section
  - Add media (images, PDFs, links)
  - Get endorsements for top skills
</seo_tips>

I need you to ghostwrite content in this person's voice:

VOICE SAMPLE (their previous writing):
{{PASTE_2-3_PARAGRAPHS_OF_THEIR_WRITING}}

VOICE CHARACTERISTICS:
- Sentence structure: {{Long/Short/Varied}}
- Vocabulary level: {{Simple/Complex/Technical}}
- Tone: {{Formal/Casual/Humorous/Serious}}
- Point of view: {{First person/Second person}}
- Common phrases: {{List any catchphrases or recurring patterns}}

CONTENT TO WRITE:
Topic: {{TOPIC}}
Format: {{LinkedIn post/Tweet thread/Article/etc}}
Length: {{WORD_COUNT}}
Key points to cover: {{BULLET_POINTS}}

OUTPUT REQUIREMENTS:
1. Match their voice precisely (tone, structure, vocabulary)
2. Include their typical formatting (emoji, line breaks, etc.)
3. Use their common phrases where natural
4. Maintain their signature style (personal anecdotes, data-driven, etc.)

After writing, provide:
- Voice matching confidence score (1-10)
- Specific elements that match their style
- Any deviations and why

Analyze and improve this headline:

"{{YOUR_HEADLINE}}"

ANALYSIS CRITERIA:

1. Emotional Impact (1-10)
   - Does it trigger curiosity, fear, joy, urgency?
   - Emotional Marketing Value score

2. Clarity (1-10)
   - Is it immediately clear what the article is about?
   - No jargon or ambiguity

3. Length
   - Character count: {{COUNT}}
   - Ideal: 55-60 for SEO, 40-50 for social
   - Word count: {{COUNT}} (ideal: 6-10 words)

4. Power Words
   - Identify power words used: {{LIST}}
   - Suggest additions: Proven, Ultimate, Secret, Effortless, etc.

5. SEO
   - Keyword present? {{YES/NO}}
   - Keyword position (best if in first 3 words)

6. Specificity
   - Numbers? (e.g., "17 Ways" > "Ways")
   - Timeframe? (e.g., "in 10 Minutes")

IMPROVED VERSIONS:
Provide 5 variations optimized for:
1. SEO (keyword-first)
2. Social sharing (curiosity-driven)
3. Email subject (benefit-focused)
4. Paid ads (direct response)
5. Your personal favorite

For each, explain what makes it stronger.