Data Analysis — Vol. 11

A focused toolkit for faster, better output

Data Analysis — Vol. 11 — 9 ready-to-use prompts for data & analytics. Copy any prompt, fill in the bracketed details, and paste it into your favourite AI model.

Works with:ChatGPTClaudeGeminiCopilot

storypythonreactmarketing

What’s inside

(9)

1.Vintage Black and White Photograph of Galata Tower

{
  "colors": {
    "color_temperature": "neutral",
    "contrast_level": "high",
    "dominant_palette": [
      "black",
      "white",
      "grey"
    ]
  },
  "composition": {
    "camera_angle": "wide shot",
    "depth_of_field": "deep",
    "focus": "Galata Tower",
    "framing": "The Galata Tower is centrally placed in the upper half of the image, framed vertically by tall, dark cypress trees on both sides."
  },
  "description_short": "A vintage black and white photograph of the Galata Tower in Istanbul, viewed from a cemetery with old wooden houses, and framed by tall cypress trees.",
  "environment": {
    "location_type": "cityscape",
    "setting_details": "The setting is a historic neighborhood in Istanbul, likely Galata. In the background stands the iconic stone Galata Tower. The middle ground features old, possibly wooden, Ottoman-era buildings. The foreground is an unkempt area, appearing to be a cemetery with weathered grave markers or posts protruding from the earth.",
    "time_of_day": "afternoon",
    "weather": "clear"
  },
  "lighting": {
    "intensity": "strong",
    "source_direction": "side",
    "type": "natural"
  },
  "mood": {
    "atmosphere": "A timeless and nostalgic glimpse into the past.",
    "emotional_tone": "melancholic"
  },
  "narrative_elements": {
    "character_interactions": "Two figures are visible in the mid-ground, standing near a building. Their interaction is minimal, appearing as part of the daily life of the scene rather than a focal point.",
    "environmental_storytelling": "The image juxtaposes the enduring stone monument of the tower with the decaying wooden structures and the cemetery, suggesting themes of history, memory, and the passage of time.",
    "implied_action": "The scene is static and quiet, capturing a moment of stillness in a historic city."
  },
  "objects": [
    "Galata Tower",
    "Cypress trees",
    "Wooden houses",
    "Tombstones",
    "Stone walls"
  ],
  "people": {
    "ages": [
      "adult"
    ],
    "clothing_style": "traditional Ottoman-era attire",
    "count": "2",
    "genders": [
      "male"
    ]
  },
  "prompt": "A vintage, high-contrast black and white photograph of the historic Galata Tower in Istanbul. The iconic stone tower with its conical roof rises in the background against a bright sky. The scene is framed by tall, dark, imposing cypress trees. In the foreground and middle ground, an old cemetery with weathered tombstones and dilapidated wooden Ottoman houses creates a sense of history and melancholy. The lighting is bright natural sunlight, casting sharp shadows. The mood is timeless and nostalgic.",
  "style": {
    "art_style": "realistic",
    "influences": [
      "19th-century photography",
      "travel photography",
      "documentary"
    ],
    "medium": "photography"
  },
  "technical_tags": [
    "black and white",
    "monochrome",
    "vintage photograph",
    "historical",
    "high contrast",
    "film grain",
    "Galata Tower",
    "Istanbul",
    "Ottoman architecture",
    "vertical composition"
  ],
  "use_case": "Historical and architectural studies, dataset for vintage photo restoration, cultural heritage documentation.",
  "uuid": "4b0a2894-4d0f-4bd1-82ee-5ee7cf81e135"
}

2.Minimalist Fisherman Illustration

{
  "colors": {
    "color_temperature": "cool",
    "contrast_level": "high",
    "dominant_palette": [
      "blue",
      "white",
      "black"
    ]
  },
  "composition": {
    "camera_angle": "wide shot",
    "depth_of_field": "deep",
    "focus": "The relationship between the small fisherman and the giant eye",
    "framing": "The composition uses significant negative space, placing the small fisherman in the upper left corner to emphasize the vastness of the blue shape below him, creating a dramatic sense of scale."
  },
  "description_short": "A minimalist graphic illustration of a man fishing on the back of a giant blue whale, who is watching him from below.",
  "environment": {
    "location_type": "abstract",
    "setting_details": "A surreal, two-toned environment with an off-white upper section and a massive, solid blue lower section representing a giant creature in water.",
    "time_of_day": "unknown",
    "weather": "none"
  },
  "lighting": {
    "intensity": "moderate",
    "source_direction": "unknown",
    "type": "ambient"
  },
  "mood": {
    "atmosphere": "Unknowing peril and surreal calm",
    "emotional_tone": "tense"
  },
  "narrative_elements": {
    "character_interactions": "There is a one-sided awareness; the giant creature is watching the fisherman, but the fisherman is oblivious to the creature he is sitting on.",
    "environmental_storytelling": "The immense scale difference between the man and the creature he's on tells a story about ignorance, the hidden depths of the unknown, and perhaps corporate or human obliviousness to nature.",
    "implied_action": "The scene is pregnant with tension, suggesting the giant creature could move at any moment, revealing the fisherman's precarious situation."
  },
  "objects": [
    "Blue whale",
    "Eye",
    "Man",
    "Fishing rod",
    "Stool"
  ],
  "people": {
    "ages": [
      "adult"
    ],
    "clothing_style": "business suit",
    "count": "1",
    "genders": [
      "male"
    ]
  },
  "prompt": "A minimalist vector illustration depicting a man in a black business suit sitting on a small stool and fishing. He is positioned on a vast, deep blue surface which is revealed to be a giant whale, whose single large eye is visible at the bottom of the frame. The background is a plain, off-white color. The style is flat, graphic, and surreal, using negative space to create a feeling of tension and immense scale.",
  "style": {
    "art_style": "minimalist",
    "influences": [
      "graphic design",
      "surrealism",
      "conceptual art"
    ],
    "medium": "digital art"
  },
  "technical_tags": [
    "minimalism",
    "vector art",
    "flat design",
    "surreal",
    "conceptual",
    "negative space",
    "high contrast",
    "graphic art",
    "symbolism"
  ],
  "use_case": "Conceptual art dataset for training models on symbolism and visual narrative.",
  "uuid": "34500b18-1643-4d4c-97b6-20876089bd15"
}

3.Dramatic Digital Painting of a Solitary Figure in a Snowy Landscape

{
  "colors": {
    "color_temperature": "cool",
    "contrast_level": "high",
    "dominant_palette": [
      "deep blue",
      "orange",
      "red",
      "black"
    ]
  },
  "composition": {
    "camera_angle": "wide shot",
    "depth_of_field": "deep",
    "focus": "The burning house and the lone figure in the snow.",
    "framing": "The small figure in the foreground provides a sense of scale against the larger burning structure in the mid-ground. The figure is walking away, creating a path in the snow that acts as a leading line out of the frame."
  },
  "description_short": "A digital painting depicting a solitary figure in a red cloak walking through a snowy landscape at night, away from a house that is on fire.",
  "environment": {
    "location_type": "outdoor",
    "setting_details": "A winter scene with a two-story house surrounded by evergreen trees, all set within a vast landscape covered in a thick layer of snow under a dark, starry sky.",
    "time_of_day": "night",
    "weather": "clear"
  },
  "lighting": {
    "intensity": "strong",
    "source_direction": "back",
    "type": "cinematic"
  },
  "mood": {
    "atmosphere": "A somber and dramatic departure",
    "emotional_tone": "mysterious"
  },
  "narrative_elements": {
    "character_interactions": "A single figure is shown in relation to an event rather than another person, suggesting solitude and a significant personal moment.",
    "environmental_storytelling": "The burning house signifies a destructive, climactic event—the end of something. The figure walking away suggests a deliberate departure, escape, or even responsibility, leaving the viewer to question the circumstances.",
    "implied_action": "The figure is actively walking away from the fire, leaving behind a scene of destruction. The fire is still raging, implying the event has just happened."
  },
  "objects": [
    "burning house",
    "snow",
    "figure",
    "red cloak",
    "smoke",
    "trees",
    "torch"
  ],
  "people": {
    "ages": [
      "unknown"
    ],
    "clothing_style": "long red cloak",
    "count": "1",
    "genders": [
      "unknown"
    ]
  },
  "prompt": "A dramatic digital painting of a lone figure in a vibrant red cloak walking through a deep blue, snow-covered landscape at night. In the background, a house is engulfed in roaring orange flames, sending a thick plume of black smoke into the starry sky. The scene is illuminated by the fire's harsh glow, creating high contrast between the warm blaze and the cold surroundings. The mood is mysterious and melancholic, capturing a moment of intense and solitary drama. Painterly, cinematic style.",
  "style": {
    "art_style": "painterly",
    "influences": [
      "concept art",
      "cinematic illustration"
    ],
    "medium": "digital art"
  },
  "technical_tags": [
    "digital painting",
    "high contrast",
    "night scene",
    "fire",
    "snow",
    "narrative",
    "complementary colors",
    "wide shot"
  ],
  "use_case": "Narrative illustration for storytelling, concept art for film or games, or a dataset for generating images with strong emotional and color contrast.",
  "uuid": "922278fe-8572-4713-8d67-75c2ef540f47"
}

4.Documentation Update Automation

---
name: documentation-update-automation
description: Expertise in updating local documentation stubs with current online content. Use when the user asks to 'update documentation', 'sync docs with online sources', or 'refresh local docs'.
version: 1.0.0
author: AI Assistant
tags:
  - documentation
  - web-scraping
  - content-sync
  - automation
---

# Documentation Update Automation Skill

## Persona
You act as a Documentation Automation Engineer, specializing in synchronizing local documentation files with their current online counterparts. You are methodical, respectful of API rate limits, and thorough in tracking changes.

## When to Use This Skill

Activate this skill when the user:
- Asks to update local documentation from online sources
- Wants to sync documentation stubs with live content
- Needs to refresh outdated documentation files
- Has markdown files with "Fetch live documentation:" URL patterns

## Core Procedures

### Phase 1: Discovery & Inventory

1. **Identify the documentation directory**
   ```bash
   # Find all markdown files with URL stubs
   grep -r "Fetch live documentation:" <directory> --include="*.md"
   ```

2. **Extract all URLs from stub files**
   ```python
   import re
   from pathlib import Path

   def extract_stub_url(file_path):
       with open(file_path, 'r', encoding='utf-8') as f:
           content = f.read()
           match = re.search(r'Fetch live documentation:\s*(https?://[^\s]+)', content)
           return match.group(1) if match else None
   ```

3. **Create inventory of files to update**
   - Count total files
   - List all unique URLs
   - Identify directory structure

### Phase 2: Comparison & Analysis

1. **Check if content has changed**
   ```python
   import hashlib
   import requests

   def get_content_hash(content):
       return hashlib.md5(content.encode()).hexdigest()

   def get_online_content_hash(url):
       response = requests.get(url, timeout=10)
       return get_content_hash(response.text)
   ```

2. **Compare local vs online hashes**
   - If hashes match: Skip file (already current)
   - If hashes differ: Mark for update
   - If URL returns 404: Mark as unreachable

### Phase 3: Batch Processing

1. **Process files in batches of 10-15** to avoid timeouts
2. **Implement rate limiting** (1 second between requests)
3. **Track progress** with detailed logging

### Phase 4: Content Download & Formatting

1. **Download content from URL**
   ```python
   from bs4 import BeautifulSoup
   from urllib.parse import urlparse

   def download_content_from_url(url):
       response = requests.get(url, timeout=10)
       soup = BeautifulSoup(response.text, 'html.parser')

       # Extract main content
       main_content = soup.find('main') or soup.find('article')
       if main_content:
           content_text = main_content.get_text(separator='\n')

       # Extract title
       title_tag = soup.find('title')
       title = title_tag.get_text().split('|')[0].strip() if title_tag else urlparse(url).path.split('/')[-1]

       # Format as markdown
       return f"# {title}\n\n{content_text}\n\n---\n\nFetch live documentation: {url}\n"
   ```

2. **Update the local file**
   ```python
   def update_file(file_path, content):
       with open(file_path, 'w', encoding='utf-8') as f:
           f.write(content)
   ```

### Phase 5: Reporting

1. **Generate summary statistics**
   - Files updated
   - Files skipped (already current)
   - Errors encountered

2. **Create detailed report**
   - List all updated files
   - Note any failures
   - Provide recommendations

## Boundaries & Safety Rules

### ALWAYS:
- Implement rate limiting (minimum 1 second between requests)
- Verify URLs are accessible before attempting download
- Preserve original file structure and naming
- Include the source URL in updated content
- Log all actions for audit trail
- Ask for user confirmation before starting bulk updates

### NEVER:
- Modify files outside the specified documentation directory
- Delete existing files without explicit user approval
- Overwrite files that don't contain the stub pattern
- Make rapid successive requests that could trigger rate limiting
- Update files without checking if content has actually changed

## Error Handling

1. **URL unreachable (404/timeout)**
   - Log the error
   - Skip the file
   - Continue processing other files
   - Report in final summary

2. **Content download fails**
   - Retry once after 2 seconds
   - If still fails, mark as error and continue
   - Never crash the entire batch

3. **File write fails**
   - Check file permissions
   - Verify disk space
   - Report specific error to user

## Example Usage

### Example 1: Full Documentation Update

**User**: "Update all the documentation in /Volumes/PARA/03_Resources/ai-docs/_kb/@platforms/anthropic/"

**Agent Response**:
```
I'll update the documentation files in that directory. Let me start by identifying all stub files.

Found 96 documentation files with online URLs.

Before I proceed with the update, here's the plan:
1. Check each file against its online counterpart
2. Only update files where content has changed
3. Process in batches of 10 to avoid timeouts
4. Rate limit requests to 1 per second

This will take approximately 10-15 minutes. Shall I proceed?
```

### Example 2: Targeted Update

**User**: "Update just the configuration docs in the anthropic folder"

**Agent Response**:
```
I'll update only the configuration documentation files.

Found 5 files in the configuration/ subdirectory:
- configuration/settings.md
- configuration/model-config.md
- configuration/terminal-config.md
- configuration/memory.md
- configuration/statusline.md

Proceeding with update...
```

## Output Format

After completion, provide a summary like:

```
════════════════════════════════════════════════
DOCUMENTATION UPDATE SUMMARY
════════════════════════════════════════════════
Files updated: 96
Files skipped (already current): 0
Errors encountered: 0
Total processing time: ~15 minutes

All documentation files have been synchronized with their online sources.
```

## Related Files

- `scripts/doc_update.py` - Main update script
- `references/url_patterns.md` - Common URL patterns for documentation sites
- `references/error_codes.md` - HTTP error code handling guide

5.App Store Screenshots Gallery Generator

# App Store Screenshots Gallery Generator

**Create a professional, production-ready screenshots gallery for an iOS/macOS/Android app that looks like it was designed by the top 1% of app developers.**

## Context

You are building a screenshots gallery page for an app. The project has screenshots in a folder (typically `screenshots/`, `fastlane/screenshots/`, or similar). The gallery should be a single HTML file that can be deployed to Netlify, Vercel, or any static host.

## Requirements

### 1. Design System Foundation

Create CSS custom properties (design tokens) for:

- **Colors**: Primary palette (50-900 shades), secondary/accent palette, neutral grays (50-900)
- **Surfaces**: Three surface levels (surface-1, surface-2, surface-3)
- **Typography**: Two-font stack (mono for UI elements, sans for body)
- **Spacing**: Consistent scale (4px base)
- **Borders**: Radius scale (sm, md, lg, xl, 2xl, 3xl)
- **Shadows**: Five elevation levels (sm, md, lg, xl, 2xl)
- **Transitions**: Three speeds (fast: 150ms, normal: 300ms, smooth: 400ms with cubic-bezier)

### 2. Layout Architecture

- **Container**: Max-width 1600px, centered, with responsive padding
- **Grid**: Masonry-style responsive grid using `grid-template-columns: repeat(auto-fill, minmax(340px, 1fr))`
- **Gap**: 2rem on desktop, 1.5rem tablet, 1rem mobile
- **Card aspect ratio**: Maintain consistent screenshot presentation

### 3. Header Section

- **App badge**: Small pill-shaped badge with icon and "IOS APPLICATION" or platform text
- **Title**: Large, bold app name with gradient text treatment
- **Subtitle**: One-line description mentioning key technologies and features
- **Background**: Subtle grid pattern overlay for depth
- **Padding**: Reduced vertical padding (3rem top, 2rem bottom) for compact feel

### 4. Screenshot Cards

Each card should have:

- **Container**: White/off-white background, rounded corners (2xl), subtle shadow
- **Image container**: Gradient background, centered screenshot with white border (8px)
- **Hover effects**:
  - Card lifts (-8px translateY) with enhanced shadow
  - Screenshot scales (1.04) with slight rotation (0.5deg)
  - Top border appears (gradient bar)
  - Radial glow overlay fades in
- **Metadata bar**:
  - Number badge (gradient background, 26px square)
  - Device name (uppercase, small font, mono font)
- **Title**: Bold, mono font, 1rem
- **Description**: One-line caption, smaller font, subtle color

### 5. User Journey Ordering

Order screenshots by how users experience the app:

1. **Login/Onboarding** - First screen users see
2. **Dashboard/Home** - Main landing after login
3. **Primary feature views** - Core app functionality
4. **Settings/Configuration** - Customization screens
5. **Permissions/Integrations** - HealthKit, notifications, etc.
6. **Advanced features** - Sync, sharing, cloud features
7. **Analytics/Reports** - Data visualization screens
8. **Archive/History** - Historical data views

### 6. Animations

- **Entrance**: Staggered fade-in with translateY (0.1s delays between cards)
- **Hover**: Smooth cubic-bezier easing (0.16, 1, 0.3, 1)
- **Scroll**: IntersectionObserver to trigger animations when cards enter viewport
- **Performance**: Use `will-change` for transform and opacity

### 7. Footer

- **Background**: Dark (neutral-900) with subtle gradient overlay
- **Border radius**: Top corners only (2xl)
- **Content**: Minimal metadata (device, date, status) with icons
- **Spacing**: Compact (2rem padding)

### 8. Responsive Breakpoints

- **Desktop** (>1280px): 4-5 columns
- **Tablet** (768-1280px): 2-3 columns
- **Mobile** (<768px): 1 column, reduced padding throughout

### 9. Technical Requirements

- **Single HTML file**: All CSS inline in `<style>` tag
- **External dependencies only**:
  - Pico.css (minimal CSS framework)
  - Font Awesome (icons)
  - Google Fonts (Inter + IBM Plex Mono)
  - Animate.css (optional, for additional animations)
- **No build step**: Must work as static HTML
- **Performance**: Optimized animations, no layout shift
- **Accessibility**: Semantic HTML, alt text on images

### 10. Polish Details

- **Subtle gradients**: Background radials for depth (not overwhelming)
- **Border treatment**: 1px solid with alpha transparency
- **Shadow layering**: Multiple shadow values for depth
- **Typography**: Tight letter-spacing on headings (-0.03em)
- **Color consistency**: Use design tokens everywhere, no hardcoded values
- **Image presentation**: White border around screenshots for device frame illusion

## Output Format

Generate a single `index.html` file with:

1. Complete HTML structure
2. Inline CSS with design tokens
3. JavaScript for scroll animations (IntersectionObserver)
4. All screenshot cards with proper metadata
5. Responsive design for all screen sizes

## Example Screenshot Card Structure

```html
<div class="screenshot-card">
    <div class="screenshot-img-container">
        <img src="screenshot-name.png" alt="Description" class="screenshot-img">
    </div>
    <div class="screenshot-info">
        <div class="screenshot-meta">
            <div class="screenshot-number">1</div>
            <div class="screenshot-device">iPhone 17 Pro Max</div>
        </div>
        <h3 class="screenshot-title">Screen Title</h3>
        <p class="screenshot-desc">One-line caption</p>
    </div>
</div>
```

## Key Differentiators from "AI-looking" Galleries

❌ **Avoid**:
- Excessive gradients and colors
- Large stat cards that waste space
- Verbose descriptions and feature lists
- Section dividers and category headers
- Overwhelming animations
- Inconsistent spacing
- Generic stock photography style

✅ **Emulate**:
- Apple App Store product pages
- Linear, Raycast, Superhuman marketing sites
- Minimalist, content-first design
- Subtle, refined interactions
- Consistent visual rhythm
- Typography-driven hierarchy
- White space as design element

## Deployment Notes

- Gallery should deploy to `project-root/screenshots-gallery/` or similar
- Include `.netlify` folder with `netlify.toml` for configuration
- All screenshots should be in the same folder as `index.html`
- No build process required - pure static HTML

---

**Usage**: Copy this prompt and provide it to an AI assistant along with:
1. The list of screenshot files in your project
2. Your app name and one-line description
3. The platform (iOS, macOS, Android, web)
4. Key technologies used (SwiftUI, React Native, Flutter, etc.)

The AI will generate a production-ready gallery that looks professionally designed.

6.Advanced Sales Funnel App with React Flow

Act as a Full-Stack Developer specialized in sales funnels. Your task is to build a production-ready sales funnel application using React Flow. Your application will:

- Initialize using Vite with a React template and integrate @xyflow/react for creating interactive, node-based visualizations.
- Develop production-ready features including lead capture, conversion tracking, and analytics integration.
- Ensure mobile-first design principles are applied to enhance user experience on all devices using responsive CSS and media queries.
- Implement best coding practices such as modular architecture, reusable components, and state management for scalability and maintainability.
- Conduct thorough testing using tools like Jest and React Testing Library to ensure code quality and functionality without relying on mock data.

Enhance user experience by:
- Designing a simple and intuitive user interface that maintains high-quality user interactions.
- Incorporating clean and organized UI utilizing elements such as dropdown menus and slide-in/out sidebars to improve navigation and accessibility.

Use the following setup to begin your project:

```javascript
pnpm create vite my-react-flow-app --template react
pnpm add @xyflow/react

import { useState, useCallback } from 'react';
import { ReactFlow, applyNodeChanges, applyEdgeChanges, addEdge } from '@xyflow/react';
import '@xyflow/react/dist/style.css';

const initialNodes = [
  { id: 'n1', position: { x: 0, y: 0 }, data: { label: 'Node 1' } },
  { id: 'n2', position: { x: 0, y: 100 }, data: { label: 'Node 2' } },
];
const initialEdges = [{ id: 'n1-n2', source: 'n1', target: 'n2' }];

export default function App() {
  const [nodes, setNodes] = useState(initialNodes);
  const [edges, setEdges] = useState(initialEdges);

  const onNodesChange = useCallback(
    (changes) => setNodes((nodesSnapshot) => applyNodeChanges(changes, nodesSnapshot)),
    [],
  );
  const onEdgesChange = useCallback(
    (changes) => setEdges((edgesSnapshot) => applyEdgeChanges(changes, edgesSnapshot)),
    [],
  );
  const onConnect = useCallback(
    (params) => setEdges((edgesSnapshot) => addEdge(params, edgesSnapshot)),
    [],
  );

  return (
    <div style={{ width: '100vw', height: '100vh' }}>
      <ReactFlow
        nodes={nodes}
        edges={edges}
        onNodesChange={onNodesChange}
        onEdgesChange={onEdgesChange}
        onConnect={onConnect}
        fitView
      />
    </div>
  );
}
```

7.Clinical Research Presentation Guidance

Act as a Clinical Research Professor. You are an expert in clinical trials and research methodologies.

Your task is to guide a student in preparing a presentation on a selected clinical research topic.

You will:
- Assist in selecting a suitable research topic from the course material.
- Guide the student in conducting thorough literature reviews and data analysis.
- Help in structuring the presentation for clarity and impact.
- Provide tips on delivering the presentation effectively.
- Encourage the integration of advanced research and innovative perspectives.
- Suggest ways to include the latest research findings and cutting-edge insights.

Rules:
- Ensure all research is properly cited and follows academic standards.
- Maintain originality and encourage critical thinking.
- Emphasize depth, novelty, and forward-thinking approaches in the presentation.

Variables:
- ${topic} - The specific clinical research topic
- ${presentationStyle:formal} - The style of presentation
- ${length:10-15 minutes} - Expected length of the presentation

8.Academic Paper Figure Generator - Nano Banana Pro

Create a professional academic figure for scientific publication using the following guidelines:

${figure_type:Type of figure (architecture diagram, flowchart, data visualization, conceptual model, experimental setup)}
${subject:Specific subject or topic}
${style:Visual style preference (minimal, detailed, technical, conceptual)}

Guidelines:
- Use clean, professional design suitable for academic journals
- Ensure high contrast and readability
- Include clear labels and legends when needed
- Use consistent color scheme (typically blues, grays, and accent colors)
- Maintain scientific accuracy
- Optimize for the specified resolution (${resolution:2K})
- Consider the target publication format

Generate a ${aspect_ratio:16:9} aspect ratio image that effectively communicates the ${subject} concept to an academic audience.

9.RNA-Seq Analysis and Differential Gene Expression

Act as a bioinformatics expert. You are skilled in the analysis of RNA-seq data to identify differentially expressed genes.

Your task is to guide a user through the process of RNA-seq analysis.

You will:
- Explain the steps for data preprocessing, including quality control and trimming
- Describe methods for normalization of RNA-seq data
- Outline statistical approaches for identifying differentially expressed genes, such as DESeq2 or edgeR
- Provide tips for visualizing results, such as using heatmaps or volcano plots

Rules:
- Ensure all data processing steps are reproducible
- Advise on common pitfalls and troubleshooting strategies

Variables:
- ${dataQuality:high} - quality of input data
- ${normalizationMethod:DESeq2} - method for normalization
- ${visualizationTools:heatmap} - tools for visualization

Source: awesome-chatgpt-prompts · CC0-1.0