# Creator Studio Pack - Complete Production Workflows

> This guide contains battle-tested production workflows for different content creation scenarios. Each workflow includes timing estimates, tools used, and expected outputs.

- Skill: `tools-only/creator-studio-pack-complete-production-workflows` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add tools-only/creator-studio-pack-complete-production-workflows`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tools-only/creator-studio-pack-complete-production-workflows/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: tools-only (https://skillmd.com/u/tools-only)
- Updated: 2026-09-29
- Page: https://skillmd.com/skills/tools-only/creator-studio-pack-complete-production-workflows

---

# Creator Studio Pack - Complete Production Workflows

**Version**: 1.0.0
**Last Updated**: 2025-10-11

---

## Overview

This guide contains battle-tested production workflows for different content creation scenarios. Each workflow includes timing estimates, tools used, and expected outputs.

---

## Table of Contents

1. [Solo Builder Workflow](#solo-builder-workflow)
2. [Batch Recording Workflow](#batch-recording-workflow)
3. [Collaboration Workflow](#collaboration-workflow)
4. [Repurposing Workflow](#repurposing-workflow)
5. [Live Coding Session Workflow](#live-coding-session-workflow)
6. [Tutorial Series Workflow](#tutorial-series-workflow)
7. [Problem-Solving Workflow](#problem-solving-workflow)
8. [Product Launch Workflow](#product-launch-workflow)

---

## Solo Builder Workflow

**The daily workflow for builders who document as they work**

### Phase 1: Build (Ongoing)

**Time**: Your normal development time
**Tools**: `build-logger-agent`, git
**Output**: Automatic build documentation

**Actions:**
```bash
# Start of project
Talk to build-logger-agent: "Start tracking my [project-name] development"

# As you work (automatic)
git add .
git commit -m "feat: implement user authentication"
git push

# Build logger automatically:
# ✓ Captures git commits
# ✓ Analyzes code changes
# ✓ Identifies "hero moments" (10x improvements, breakthroughs)
# ✓ Suggests video ideas
# ✓ Tracks technical debt and learnings
```

**Build Logger Output Example:**
```markdown
BUILD LOG - Day 3 - User Auth System

Commits today: 7
Lines added: 342
Lines removed: 89

HERO MOMENT 🎬:
"Implemented JWT authentication with refresh tokens"
Why it matters: Secure, scalable auth in 2 hours
Video potential: HIGH (8/10)
Title suggestion: "Building Secure Authentication in 2 Hours"

Technical decisions:
- Chose JWT over sessions (why: stateless, scalable)
- Used httpOnly cookies (security best practice)
- Implemented token rotation (compliance)

Next steps:
- Add 2FA support
- Implement rate limiting
- Add logging/monitoring
```

---

### Phase 2: Document (5 minutes)

**Time**: 5 minutes after a breakthrough
**Tools**: `build-logger-agent`, `code-explainer-video`
**Output**: Video script outline

**Actions:**
```bash
# Review build log
Talk to build-logger-agent: "What video ideas do I have from today?"

# Generate script outline
Talk to code-explainer-video: "Create a video outline for my JWT authentication implementation"
```

**Script Outline Output:**
```markdown
VIDEO OUTLINE: "Building Secure Authentication in 2 Hours"

TARGET AUDIENCE: Web developers, indie hackers
LENGTH: 8-12 minutes
STYLE: Tutorial + time-lapse

HOOK (0:00-0:15):
"Watch me build production-ready authentication in 2 hours"

STORY ARC:
1. Problem: Most apps get auth wrong
2. Solution: JWT + refresh tokens + httpOnly cookies
3. Implementation: Code walkthrough
4. Result: Secure, scalable auth system

KEY MOMENTS:
- Token generation logic
- Refresh token rotation
- Security considerations
- Testing with Postman

CALL TO ACTION:
"Download the code, star the repo, try it yourself"
```

---

### Phase 3: Record (30 minutes)

**Time**: 30 minutes focused recording
**Tools**: `screen-recorder-command`, `script-to-teleprompter`
**Output**: Raw video footage

**Actions:**
```bash
# Start recording
/record start jwt-auth-tutorial --webcam

# Optional: Load script in teleprompter
/teleprompter ~/Videos/jwt-auth-tutorial/script.md

# Record segments:
# 0:00-0:30 - Hook (show the working result first)
/record mark "Working demo - secure authentication"

# 0:30-2:00 - Problem setup
/record mark "Why most auth is insecure"

# 2:00-8:00 - Implementation walkthrough
/record mark "JWT token generation"
/record mark "Refresh token logic"
/record mark "httpOnly cookie setup"

# 8:00-10:00 - Testing and results
/record mark "Postman tests passing"

# 10:00-10:30 - Call to action
/record mark "Try this yourself"

# Stop recording
/record stop
```

**Recording Output:**
```
✅ Recording saved: ~/Videos/jwt-auth-tutorial/raw/2025-10-11-jwt-auth.mp4
Duration: 10:47
Markers: 7
File size: 892 MB
Ready for editing
```

---

### Phase 4: Edit (20 minutes)

**Time**: 20 minutes automated editing
**Tools**: `video-editor-ai`, `subtitle-generator-pro`, `audio-mixer-assistant`
**Output**: Polished video ready for upload

**Actions:**
```bash
# Automated editing
Talk to video-editor-ai: "Edit jwt-auth-tutorial:
- Cut at my 7 markers
- Remove silence over 1.5 seconds
- Add Mr Beast style subtitles
- Mix audio levels (normalize voice, reduce keyboard noise)
- Add intro animation (3 seconds)
- Add outro with subscribe button
- Export 1080p 60fps for YouTube"

# While editing runs (takes 5-10 minutes), create thumbnail
/thumbnail "Building Secure Authentication in 2 Hours" --style code-focused

# Generate metadata
/metadata "Building Secure Authentication in 2 Hours" --include-chapters
```

**Editing Output:**
```
✅ Video processed in 8 minutes 34 seconds

Edits applied:
- Removed 1m 23s of silence
- Applied 7 cuts at markers
- Added 1,247 subtitle words
- Normalized audio (-23 LUFS)
- Reduced background noise by 15dB
- Added intro/outro animations
- Generated 4 thumbnail variations
- Created chapter markers

Final video:
Duration: 9:24 (from 10:47 raw)
File: ~/Videos/jwt-auth-tutorial/final/jwt-auth-final.mp4
Size: 487 MB
```

---

### Phase 5: Publish (10 minutes)

**Time**: 10 minutes multi-platform distribution
**Tools**: `distribution-automator`, `seo-metadata-generator`
**Output**: Video published across 6+ platforms

**Actions:**
```bash
# Distribute everywhere
Talk to distribution-automator: "Publish jwt-auth-tutorial:
- YouTube: Schedule for Tuesday 10am EST
- Twitter: 5-tweet thread with 30-second clips
- LinkedIn: Professional post with article
- Reddit: r/webdev with context
- Blog: Full transcript + code snippets
- Email: Send to subscribers
- Cross-promote with previous videos"
```

**Distribution Output:**
```
✅ YOUTUBE
Uploaded: 9m 24s video
Title: "Building Secure Authentication in 2 Hours (JWT + Refresh Tokens)"
Thumbnail: Variation 2 (code-focused with face)
Scheduled: Tuesday 10:00 AM EST
Chapters: Auto-generated from markers
Tags: 25 tags added
Predicted views: 5K-20K first week

✅ TWITTER
Thread created: 5 tweets
Tweet 1: Hook + 30-second clip
Tweet 2: Problem explanation
Tweet 3: Code snippet + screenshot
Tweet 4: Results + metrics
Tweet 5: CTA + link
Posted: Now

✅ LINKEDIN
Article: "How to Build Production-Ready Authentication"
Video embedded: First 2 minutes
Length: 850 words
Posted: Now

✅ REDDIT
Subreddit: r/webdev
Context: Included code snippets and GitHub link
Posted: Now

✅ BLOG
Published: https://yourblog.com/secure-auth-tutorial
Includes: Full transcript, code blocks, embedded video
SEO: Optimized for "JWT authentication tutorial"

✅ EMAIL
Subject: "New Tutorial: Build Secure Auth in 2 Hours"
Sent to: 1,543 subscribers
Open rate (predicted): 32-38%

Total reach (estimated): 10K-50K in first week
```

---

### Total Time Investment

**Active time**: 65 minutes
- Document: 5 minutes
- Record: 30 minutes
- Edit: 20 minutes
- Publish: 10 minutes

**Passive time**: 10 minutes (AI processing)

**Total**: 75 minutes for 1 complete video + 30+ derivative content pieces

---

## Batch Recording Workflow

**Record 7 videos in one 3.5-hour session**

### Why Batch Recording?

**Efficiency gains:**
- Setup once, record multiple times
- Context switching minimized
- Consistent energy/appearance
- Bulk editing in parallel

**Best for:**
- Weekly content sprints
- Tutorial series
- Multiple small topics
- Consistent publishing schedule

---

### Pre-Session Planning (30 minutes)

**Day before recording:**

```bash
# Review build log for video ideas
Talk to build-logger-agent: "What are my best video ideas from the past 2 weeks?"

# Plan session
Talk to batch-recording-scheduler: "I have 3.5 hours Saturday morning. Plan maximum output."
```

**Scheduler Output:**
```markdown
BATCH RECORDING SESSION - Saturday 9am-12:30pm

SETUP 1: Screen Recording (Code Tutorials) - 90 minutes
Environment: IDE + terminal + browser
Lighting: Natural (window left side)
Camera: Off

Video 1: "JWT Authentication Tutorial" (30 min)
Video 2: "Redis Caching Implementation" (30 min)
Video 3: "Database Migration Strategy" (30 min)

--- 10 MINUTE BREAK ---

SETUP 2: Face-to-Camera (Talking Head) - 60 minutes
Environment: Clean background
Lighting: Ring light + key light
Camera: On, centered

Video 4: "My Development Workflow" (20 min)
Video 5: "5 Tools That Changed My Life" (20 min)
Video 6: "Answering Your Questions" (20 min)

--- 10 MINUTE BREAK ---

SETUP 3: Hybrid (Screen + Face) - 30 minutes
Environment: Split screen
Lighting: Ring light
Camera: Picture-in-picture

Video 7: "Week 3 Build Recap" (30 min)

POST-SESSION:
Batch edit: 1.5 hours (all 7 videos)
Total production: 5 hours → 7 published videos
```

---

### Session Execution

**Setup 1: Screen Recording (9:00am - 10:30am)**

```bash
# Prepare environment
- Close all non-essential apps
- Clear desktop clutter
- Open IDE with clean project
- Test audio levels
- Hide notifications

# Record Video 1
/record start jwt-auth-tutorial --screen-only
[30 minutes of focused recording]
/record stop

# 2-minute transition (save files, switch project)

# Record Video 2
/record start redis-caching --screen-only
[30 minutes of focused recording]
/record stop

# 2-minute transition

# Record Video 3
/record start database-migrations --screen-only
[30 minutes of focused recording]
/record stop

# Break: 10 minutes (stretch, water, bathroom)
```

**Setup 2: Face-to-Camera (10:40am - 11:40am)**

```bash
# Environment change
- Switch to clean background
- Turn on ring light + key light
- Position camera at eye level
- Check framing in monitor
- Load teleprompter scripts

# Record Video 4
/record start dev-workflow --webcam-only
/teleprompter ~/scripts/dev-workflow.md
[20 minutes recording]
/record stop

# 2-minute transition (new script)

# Record Video 5
/record start tool-recommendations --webcam-only
/teleprompter ~/scripts/tools.md
[20 minutes recording]
/record stop

# 2-minute transition

# Record Video 6
/record start qa-session --webcam-only
[20 minutes recording - no teleprompter, natural]
/record stop

# Break: 10 minutes
```

**Setup 3: Hybrid (11:50am - 12:30pm)**

```bash
# Combine setups
- Screen share + picture-in-picture webcam
- Keep ring light on
- Load week's projects

# Record Video 7
/record start week-3-recap --hybrid
[30 minutes recording - tour of week's work]
/record stop

SESSION COMPLETE: 3.5 hours → 7 raw videos
```

---

### Batch Editing (1.5 hours)

**All videos edited in parallel:**

```bash
# Queue all videos for editing
Talk to video-editor-ai: "Batch edit all recordings from today:

Video 1-3 (screen recordings):
- Remove silence over 2 seconds
- Add code-focused subtitles
- Normalize audio
- Add intro/outro

Video 4-6 (face-to-camera):
- Remove filler words (um, uh, like)
- Add dynamic subtitles (Mr Beast style)
- Color grade for consistent look
- Add intro/outro

Video 7 (hybrid):
- Remove silence over 1.5 seconds
- Add subtitles
- Enhance screen clarity
- Add intro/outro

Export all as 1080p 60fps for YouTube"
```

**Editing Output:**
```
✅ Batch processing started (all 7 videos in parallel)
Estimated completion: 12-15 minutes

Video 1: jwt-auth-tutorial
- Edited: 10:47 → 9:24
- Removed: 1m 23s silence
- Status: ✅ Complete

Video 2: redis-caching
- Edited: 9:15 → 8:02
- Removed: 1m 13s silence
- Status: ✅ Complete

[... all 7 videos processed ...]

All videos ready in: 14 minutes 22 seconds
Total output: 7 final videos, 28 thumbnail variations
```

---

### Batch Publishing (30 minutes)

**Schedule entire week's content:**

```bash
Talk to distribution-automator: "Schedule my 7 videos for this week:

Video 1 (JWT Auth): Monday 10am
Video 2 (Redis): Tuesday 10am
Video 3 (Migrations): Wednesday 10am
Video 4 (Workflow): Thursday 10am
Video 5 (Tools): Friday 10am
Video 6 (Q&A): Saturday 10am
Video 7 (Recap): Sunday 10am

For each video:
- YouTube (scheduled)
- Twitter thread (day of)
- LinkedIn article (day of)
- Reddit (manual review first)
- Blog post (day of)
- Email (Tuesday + Friday only)"
```

**Distribution Output:**
```
✅ WEEKLY CONTENT CALENDAR CREATED

Mon 10am: JWT Authentication Tutorial
Tue 10am: Redis Caching + Email Newsletter
Wed 10am: Database Migrations
Thu 10am: My Dev Workflow
Fri 10am: 5 Life-Changing Tools + Email Newsletter
Sat 10am: Q&A Session
Sun 10am: Week 3 Build Recap

All videos scheduled
All thumbnails uploaded
All metadata optimized
All social posts queued

Estimated week 1 reach: 50K-200K views
```

---

### Total Batch ROI

**Time invested**: 5 hours total
- Planning: 30 minutes
- Recording: 3.5 hours
- Editing: 1.5 hours (mostly automated)
- Publishing: 30 minutes (mostly automated)

**Content output**:
- 7 YouTube videos
- 35 Twitter threads (5 tweets each)
- 7 LinkedIn articles
- 7 blog posts
- 2 email newsletters
- 70+ social media clips

**Traditional time**: 35+ hours (5 hours per video)
**Time saved**: 30 hours (6x efficiency)

---

## Collaboration Workflow

**Guest appearances, interviews, and co-creation**

### Pre-Collaboration (1 week before)

**Planning phase:**

```bash
Talk to collaboration-manager: "Plan a collaboration with [guest name]:
- Topic: Building a SaaS in 30 days
- Format: Pair programming session
- Length: 60 minutes
- My expertise: Backend architecture
- Their expertise: Frontend design"
```

**Manager Output:**
```markdown
COLLABORATION PLAN - [Guest Name] x You

DATE: Next Friday 2pm EST
FORMAT: Pair programming (split screen)
TOPIC: "Building a SaaS in 60 Minutes"

PRE-SESSION CHECKLIST:
□ Send guest equipment requirements
□ Share project repository access
□ Test video call recording quality
□ Prepare codebase (clean, commented)
□ Create shared development environment
□ Write outline with talking points
□ Test screen sharing setup

RECORDING SETUP:
- Your side: Screen + webcam (bottom right)
- Their side: Screen + webcam (bottom left)
- Audio: Both on separate tracks
- Recording: Local + cloud backup

TECHNICAL REQUIREMENTS:
□ OBS Studio for local recording
□ Zoom/Discord for communication
□ VS Code Live Share for collaboration
□ GitHub for code sharing

TALKING POINTS:
1. Introduction (2 min)
2. Problem definition (3 min)
3. Architecture planning (10 min)
4. Backend build (20 min - you lead)
5. Frontend build (20 min - guest leads)
6. Integration + testing (10 min)
7. Wrap-up + learnings (5 min)

POST-SESSION:
- Edit into 10-minute tutorial
- Create behind-the-scenes clips
- Cross-promote on both channels
```

---

### Recording Day

**Session setup (15 minutes before):**

```bash
# Technical check
- Test OBS recording (local backup)
- Test Zoom recording (cloud backup)
- Test audio levels (yours + guest)
- Test screen sharing (both sides)
- Test VS Code Live Share
- Test webcam positioning

# Start recording
/record start collab-[guest-name] --dual-webcam --separate-audio-tracks

# Also start call recording
- Zoom: Start recording (cloud)
- OBS: Start recording (local backup)
```

**During session (60 minutes):**

```bash
# Mark key moments
/record mark "Intro - explaining the challenge"
/record mark "Architecture decisions"
/record mark "[Guest] starts frontend work"
/record mark "First feature working end-to-end"
/record mark "Bug discovered and fixed together"
/record mark "Final result demonstration"
/record mark "Learnings and takeaways"

# End recording
/record stop
```

**Recording output:**
```
✅ Collaboration recorded: 63 minutes

Files saved:
- Main recording: collab-guest-2025-10-11.mp4 (1.2 GB)
- Your audio track: you-audio.wav
- Guest audio track: guest-audio.wav
- Zoom backup: zoom-recording.mp4
- Markers: 7 key moments

Ready for editing
```

---

### Post-Production (2 hours)

**Edit into multiple videos:**

```bash
Talk to video-editor-ai: "Edit collaboration recording into 3 videos:

VIDEO 1: Main Tutorial (10 minutes)
- Use all 7 markers as structure
- Focus on technical content
- Add subtitles for both speakers
- Add code annotations
- Export for both channels

VIDEO 2: Behind the Scenes (5 minutes)
- Show planning process
- Include funny moments
- Show collaboration tools
- Add blooper reel

VIDEO 3: Key Learnings (3 minutes)
- Extract best insights
- Create quote graphics
- Format for social media
- Vertical format for TikTok/Shorts"
```

**Editing output:**
```
✅ 3 videos created from 63-minute recording

VIDEO 1: "Building a SaaS in 60 Minutes (w/ [Guest])"
Duration: 10:47
Style: Tutorial
Format: 16:9 landscape
Target: YouTube (both channels)

VIDEO 2: "Behind the Scenes: Pair Programming"
Duration: 5:23
Style: Documentary
Format: 16:9 landscape
Target: YouTube, blog

VIDEO 3: "5 Lessons from Building Together"
Duration: 3:12
Style: Quick tips
Format: 9:16 vertical
Target: TikTok, Instagram, YouTube Shorts

Total output: 19 minutes of content from 63-minute recording
```

---

### Cross-Promotion Strategy

```bash
Talk to distribution-automator: "Publish collaboration with cross-promotion:

Main video (Video 1):
- Upload to BOTH channels (same day)
- Cross-link in descriptions
- Mention each other in intros
- Share each other's social posts

BTS video (Video 2):
- Upload to YOUR channel (3 days later)
- Link to guest's channel
- Tag guest in all social posts

Learnings video (Video 3):
- Post to social media (both accounts)
- Create quote graphics featuring both
- Schedule throughout next week"
```

**Distribution output:**
```
✅ CROSS-PROMOTION SCHEDULED

FRIDAY (Release Day):
Your channel: Main video at 10am
Guest channel: Same video at 10am
Twitter: Dual announcement thread
LinkedIn: Joint article post

MONDAY (BTS):
Your channel: Behind-the-scenes at 10am
Social: Tag guest in all posts

THROUGHOUT NEXT WEEK:
7 quote graphics (alternating accounts)
5 short-form clips (both accounts)
3 blog posts (your site + guest site)

Estimated combined reach: 100K-500K views
```

---

## Repurposing Workflow

**Turn 1 video into 30+ content pieces**

### Source: 10-Minute YouTube Video

**Example**: "Building Secure Authentication in 2 Hours"

---

### Repurposing Map

**From 1 video, create:**

1. **Platform Variations** (4 pieces)
   - YouTube long-form: 10 minutes
   - YouTube Shorts: 60 seconds
   - TikTok: 60 seconds
   - Instagram Reels: 60 seconds

2. **Social Media Posts** (10 pieces)
   - Twitter thread: 5 tweets with clips
   - LinkedIn article: 1,000 words + embedded video
   - LinkedIn carousel: 10 slides
   - Instagram post: 3 images + caption
   - Facebook post: Video + long caption

3. **Written Content** (5 pieces)
   - Blog post: Full transcript + code
   - Medium article: Tutorial format
   - Dev.to article: Technical deep dive
   - Email newsletter: Key takeaways
   - Reddit post: Tutorial with context

4. **Educational Resources** (5 pieces)
   - GitHub README: Code documentation
   - Code snippets: 10 shareable blocks
   - Infographic: Process visualization
   - Cheat sheet: Quick reference PDF
   - Quiz: Test your knowledge

5. **Audio Content** (2 pieces)
   - Podcast episode: Audio extracted
   - Audio clips: 10x 30-second insights

6. **Promotional Content** (4 pieces)
   - Thumbnail variations: 4 designs
   - Quote graphics: 5 shareable images
   - Testimonial graphics: User feedback
   - Progress screenshots: Before/after

**Total: 30+ pieces from 1 video**

---

### Automated Repurposing Process

```bash
Talk to repurpose-content: "Repurpose my jwt-auth-tutorial video into all formats:

Source: ~/Videos/jwt-auth-tutorial/final/jwt-auth-final.mp4
Transcript: ~/Videos/jwt-auth-tutorial/transcript.txt
Code: https://github.com/you/jwt-auth-example

Create all variations:
- Short-form clips (YouTube Shorts, TikTok, Reels)
- Social media posts (Twitter, LinkedIn, Instagram)
- Written content (blog, Medium, Dev.to, email)
- Educational resources (README, snippets, infographic)
- Audio content (podcast, clips)
- Promotional graphics (quotes, testimonials)"
```

---

### Repurposing Output

**Agent processing time: 10-15 minutes**

```markdown
✅ REPURPOSING COMPLETE - 34 pieces created

SHORT-FORM VIDEO (4 pieces)
✅ YouTube Shorts: 60s hook + key moment
   File: jwt-auth-short.mp4
   Caption: "Building secure auth in 60 seconds"

✅ TikTok: 60s tutorial snippet
   File: jwt-auth-tiktok.mp4
   Hashtags: #coding #webdev #programming

✅ Instagram Reels: 60s with trending audio
   File: jwt-auth-reel.mp4
   Caption: "JWT authentication explained"

✅ LinkedIn: 90s professional version
   File: jwt-auth-linkedin.mp4
   Caption: "How we secure our applications"

---

SOCIAL MEDIA POSTS (10 pieces)
✅ Twitter thread (5 tweets)
   Tweet 1: Hook + 30s clip
   Tweet 2: Problem explanation
   Tweet 3: Code snippet
   Tweet 4: Results
   Tweet 5: CTA + link

✅ LinkedIn article (1,200 words)
   Title: "Building Production-Ready Authentication"
   Includes: Video embed, code blocks, diagrams
   Reading time: 5 minutes

✅ LinkedIn carousel (10 slides)
   Slide 1: Title slide
   Slides 2-9: Step-by-step tutorial
   Slide 10: CTA

✅ Instagram grid post (3 images)
   Image 1: Hook text
   Image 2: Code screenshot
   Image 3: Results
   Caption: 200-word tutorial

✅ Instagram Stories (5 stories)
   Story 1: Hook
   Stories 2-4: Tutorial steps
   Story 5: Swipe-up CTA

✅ Facebook post
   Video: First 2 minutes
   Caption: 300-word tutorial
   CTA: "Learn more (link)"

---

WRITTEN CONTENT (6 pieces)
✅ Blog post (2,500 words)
   File: blog/jwt-auth-tutorial.md
   Includes: Full transcript, code, images
   SEO optimized: "JWT authentication tutorial"

✅ Medium article (2,000 words)
   File: medium/jwt-auth-tutorial.md
   Format: Tutorial style with code blocks
   Tags: JavaScript, Security, Web Development

✅ Dev.to article (1,800 words)
   File: devto/jwt-auth-tutorial.md
   Format: Technical deep dive
   Tags: node, security, authentication

✅ Email newsletter (600 words)
   File: email/jwt-auth-newsletter.html
   Subject: "New Tutorial: Secure Authentication"
   Includes: Video embed, key takeaways

✅ Reddit post (300 words + context)
   File: reddit/jwt-auth-post.md
   Subreddits: r/webdev, r/node, r/learnprogramming
   Includes: GitHub link, code snippets

✅ Hacker News post (150 words)
   Title: "Building Secure Authentication (with code)"
   Link: Blog post URL
   Context: Brief explanation

---

EDUCATIONAL RESOURCES (7 pieces)
✅ GitHub README (1,000 words)
   File: github/README.md
   Includes: Installation, usage, examples
   Code: Fully documented

✅ Code snippets (10 files)
   Token generation, validation, refresh, etc.
   All on GitHub Gists
   Easily shareable

✅ Infographic (1 image)
   File: graphics/jwt-auth-infographic.png
   Shows: Authentication flow diagram
   Size: 1080x1920px (Instagram)

✅ Cheat sheet (1 PDF)
   File: resources/jwt-cheat-sheet.pdf
   Pages: 2
   Includes: Commands, best practices, gotchas

✅ Quiz (10 questions)
   File: resources/jwt-quiz.md
   Format: Multiple choice
   Purpose: Test understanding

✅ Slides (15 slides)
   File: slides/jwt-auth-presentation.pdf
   Format: Google Slides / PowerPoint
   Purpose: Conference talks, teaching

✅ Notion template
   File: templates/jwt-auth-implementation.notion
   Purpose: Implementation checklist

---

AUDIO CONTENT (3 pieces)
✅ Podcast episode (10 minutes)
   File: audio/jwt-auth-podcast.mp3
   Format: Audio extracted from video
   Includes: Intro/outro music

✅ Audio clips (5 clips)
   Clip 1: "Why JWT tokens" (30s)
   Clip 2: "Refresh token strategy" (45s)
   Clip 3: "Security considerations" (60s)
   Clip 4: "Common mistakes" (40s)
   Clip 5: "Best practices" (50s)

✅ Audiogram (1 video)
   File: audiogram/jwt-auth-wave.mp4
   Format: Audio waveform animation
   Duration: 60 seconds
   Purpose: Social media audio preview

---

PROMOTIONAL GRAPHICS (4 pieces)
✅ Quote graphics (5 images)
   Quote 1: "Secure authentication in 2 hours"
   Quote 2: "JWT + refresh tokens = scalable auth"
   [... 3 more quotes ...]
   Size: 1080x1080px (Instagram square)

✅ Before/after screenshots (2 images)
   Before: Insecure auth code
   After: Secure JWT implementation
   Size: 1920x1080px (YouTube thumbnail size)

✅ Process diagram (1 image)
   File: graphics/jwt-flow-diagram.png
   Shows: Complete authentication flow
   Style: Professional, colorful

✅ Testimonial graphic (1 image)
   File: graphics/testimonial.png
   Includes: User feedback quote
   Style: Clean, professional

---

TOTAL OUTPUT: 34 pieces of content
Source: 1 video (10 minutes)
Processing time: 12 minutes
Formats: 9 different platforms
Estimated reach: 10x original video views
```

---

### Publishing Schedule (30 days)

**Week 1: Launch**
- Day 1: YouTube video, Twitter thread, blog post
- Day 2: LinkedIn article
- Day 3: Dev.to article
- Day 4: Medium article
- Day 5: Email newsletter
- Day 6-7: Rest (analyze performance)

**Week 2: Short-form**
- Day 8: YouTube Shorts
- Day 9: TikTok
- Day 10: Instagram Reels
- Day 11: Instagram carousel
- Day 12: LinkedIn video
- Day 13-14: Rest

**Week 3: Educational**
- Day 15: GitHub README + code
- Day 16: Cheat sheet PDF
- Day 17: Infographic
- Day 18: Quiz
- Day 19: Slides
- Day 20-21: Rest

**Week 4: Audio + Community**
- Day 22: Podcast episode
- Day 23: Reddit post (with context)
- Day 24: Hacker News post
- Day 25: Audio clips on Twitter
- Day 26: Audiogram on LinkedIn
- Day 27-30: Community engagement

---

### Repurposing ROI

**Time invested**: 15 minutes (mostly automated)
**Content output**: 34 pieces
**Publishing window**: 30 days
**Estimated reach**: 10x original video views
**Engagement**: 3-5x more comments/interactions
**SEO benefit**: 9 different platforms linking back

**Traditional approach**:
- Create 34 pieces manually: 50+ hours
- Inconsistent quality: High variation
- Delayed publishing: Takes months

**With Creator Studio Pack**:
- 15 minutes automated repurposing
- Consistent quality across all formats
- Ready to publish immediately

---

## Live Coding Session Workflow

**Stream your build process live, then edit for YouTube**

### Pre-Stream Setup (30 minutes)

```bash
# Prepare streaming environment
Talk to collaboration-manager: "Set up live coding stream:
- Platform: Twitch + YouTube simultaneously
- Topic: Building a real-time chat app
- Duration: 2 hours
- Include: Code, webcam, chat overlay"
```

**Setup checklist:**
```markdown
STREAMING SETUP

TECHNICAL:
□ OBS Studio configured
□ Stream keys added (Twitch + YouTube)
□ Bitrate: 6000 kbps
□ Resolution: 1920x1080
□ FPS: 60

SCENES:
Scene 1: Full screen code
Scene 2: Code + webcam (bottom right)
Scene 3: Code + webcam + chat (right side)
Scene 4: "Starting soon" screen
Scene 5: "Taking a break" screen
Scene 6: "Thanks for watching" screen

AUDIO:
□ Microphone: Tested and clear
□ Desktop audio: Enabled (for alerts)
□ Music: Lo-fi beats (low volume)
□ Alerts: Configured (followers, subs)

CODE ENVIRONMENT:
□ VS Code with large font (16pt)
□ Terminal with readable colors
□ Browser with extensions hidden
□ Documentation tabs prepared
□ GitHub repository created (empty)
□ .env file with dummy values (no secrets!)

STREAM INFO:
Title: "Building a Real-Time Chat App | Live Coding"
Tags: coding, javascript, tutorial, live
Category: Science & Technology
Thumbnail: "LIVE NOW" red banner
```

---

### During Stream (2 hours)

```bash
# Start streaming
Talk to video-editor-ai: "Start recording stream for YouTube edit:
- Record locally (backup)
- Mark key moments automatically
- Detect chat interactions
- Capture highlights"

# Stream structure
0:00-0:10 - Intro + plan
0:10-0:30 - Setup project structure
0:30-1:00 - Build WebSocket server
1:00-1:30 - Build frontend chat UI
1:30-1:50 - Connect everything + test
1:50-2:00 - Recap + deploy

# Use markers during stream
/record mark "Project initialized"
/record mark "WebSocket server working"
/record mark "First message sent - IT WORKS!"
/record mark "Bug discovered - debugging"
/record mark "Bug fixed - app working"
/record mark "Deployed to production"
```

---

### Post-Stream Editing (45 minutes)

**Turn 2-hour stream into 15-minute tutorial:**

```bash
Talk to video-editor-ai: "Edit stream recording into YouTube tutorial:

Source: 2-hour live stream
Target: 15-minute tutorial

Structure:
- Intro: 30 seconds (what we're building)
- Setup: 2 minutes (fast-forward through boilerplate)
- Core logic: 8 minutes (WebSocket implementation)
- Testing: 2 minutes (showing it work)
- Deployment: 1 minute (push to production)
- Outro: 1.5 minutes (recap + CTA)

Remove:
- All chat reading (unless critical)
- Setup delays and waiting
- Debugging dead ends
- Silence over 2 seconds

Keep:
- Key moments (from markers)
- Aha moments and reactions
- Final working demonstration
- Debugging wins (if instructive)

Add:
- Chapters for each section
- Code annotations
- Subtitles
- Intro/outro animations"
```

**Editing output:**
```
✅ 2-hour stream edited to 15-minute tutorial

Removed:
- 1h 20m of setup/boilerplate (fast-forwarded to 2 min)
- 18 minutes of chat reading
- 15 minutes of debugging dead ends
- 12 minutes of silence/thinking

Kept:
- 6 key moments (from markers)
- Bug discovery + fix (instructive)
- Final working demo
- Genuine reactions

Added:
- 8 chapter markers
- 32 code annotations
- Full subtitles
- Intro/outro animations

Final video:
Duration: 15:47
Quality: 1080p 60fps
File: ~/Videos/chat-app-tutorial/final/chat-app-final.mp4
Ready for upload
```

---

### Multi-Platform Strategy

**From 1 stream, create:**

1. **Full stream archive** (Twitch/YouTube)
   - Keep full 2-hour VOD
   - For fans who want everything
   - Casual viewers

2. **Edited tutorial** (YouTube main channel)
   - 15-minute highlights
   - Professional quality
   - Optimized for discovery

3. **Key moments clips** (Social media)
   - "IT WORKS!" moment: 30 seconds
   - Bug fix: 45 seconds
   - Final demo: 60 seconds

4. **Written tutorial** (Blog)
   - Full code walkthrough
   - Copy-paste friendly
   - SEO optimized

---

## Tutorial Series Workflow

**Create a cohesive multi-part series**

### Series Planning (1 hour)

**Example series**: "Building a SaaS from Scratch"

```bash
Talk to content-calendar-ai: "Plan a tutorial series:
- Topic: Building a SaaS from scratch
- Target audience: Aspiring indie hackers
- Parts: 10 videos
- Schedule: 2 videos per week for 5 weeks
- Progression: Beginner to deployed app"
```

**Series outline:**
```markdown
TUTORIAL SERIES: "Building a SaaS from Scratch"

Part 1: "Idea Validation & Market Research" (Week 1)
Duration: 12 minutes
Build: Nothing yet (planning only)
Key takeaway: How to validate before building

Part 2: "Tech Stack Decision & Project Setup" (Week 1)
Duration: 15 minutes
Build: Project initialized, database setup
Key takeaway: Choosing the right tools

Part 3: "User Authentication System" (Week 2)
Duration: 18 minutes
Build: Complete auth (login, register, JWT)
Key takeaway: Secure authentication

Part 4: "Building the Core Feature" (Week 2)
Duration: 20 minutes
Build: Main app functionality
Key takeaway: MVP development

Part 5: "Frontend Design & UX" (Week 3)
Duration: 16 minutes
Build: Complete UI
Key takeaway: Design for users

Part 6: "Stripe Payment Integration" (Week 3)
Duration: 19 minutes
Build: Payment system
Key takeaway: Monetization from day 1

Part 7: "Email Notifications & Automation" (Week 4)
Duration: 14 minutes
Build: Email system
Key takeaway: User engagement

Part 8: "Testing & QA" (Week 4)
Duration: 17 minutes
Build: Test suite
Key takeaway: Ship with confidence

Part 9: "Deployment & DevOps" (Week 5)
Duration: 15 minutes
Build: Production deploy
Key takeaway: Ship to real users

Part 10: "Marketing & Launch" (Week 5)
Duration: 20 minutes
Build: Landing page, launch strategy
Key takeaway: Getting first customers

Total runtime: 166 minutes (2h 46m of tutorials)
Total build time: 5 weeks
Expected result: Launched SaaS product
```

---

### Recording Strategy

**Batch record multiple parts:**

```bash
# Record 2 parts per session
# 3 hours recording → 2 videos

Session 1 (Parts 1-2):
- Part 1: 45 minutes recording
- 15-minute break
- Part 2: 60 minutes recording
- Result: 2 videos ready for editing

Session 2 (Parts 3-4):
- Part 3: 60 minutes recording
- 15-minute break
- Part 4: 75 minutes recording
- Result: 2 videos ready for editing

[... repeat for all 10 parts ...]
```

---

### Series Cohesion

**Consistent elements across all videos:**

```bash
Talk to template-library: "Create series template:
- Intro animation: Same for all videos
- Outro: Previous/next episode links
- Thumbnail style: Consistent design
- Title format: 'Part X: [Topic] | Building a SaaS'
- Description: Series playlist link
- End screen: Next video + subscribe"
```

**Template output:**
```markdown
SERIES TEMPLATE: "Building a SaaS from Scratch"

INTRO (0:00-0:15):
- Animation: "Building a SaaS from Scratch"
- Episode number: "Part X of 10"
- Quick recap: "Previously..." (Parts 2-10 only)

CONTENT (varies):
[Main tutorial content]

OUTRO (last 30 seconds):
- Recap: "Today we built..."
- Next episode: "Next time we'll..."
- Call to action: "Subscribe to follow the journey"
- End screen: Next video + subscribe button

THUMBNAIL TEMPLATE:
- Background: Gradient (consistent)
- Text: "Part X: [Topic]"
- Icon: Relevant to topic
- Face: Your face (consistent position)

METADATA TEMPLATE:
Title: "Part X: [Topic] | Building a SaaS from Scratch"
Description:
  Part X of my 10-part series on building a SaaS from scratch.

  [Specific content description]

  🎬 SERIES PLAYLIST: [link]
  ⏮️ PREVIOUS EPISODE: [link]
  ⏭️ NEXT EPISODE: [link]

  [Timestamps]
  [Code repo]
  [Resources]
```

---

### Total Series Investment

**Time breakdown:**
- Planning: 1 hour (once)
- Recording: 15 hours (5 sessions x 3 hours)
- Editing: 5 hours (automated batch editing)
- Publishing: 2 hours (setup + scheduling)

**Total**: 23 hours → 10 complete tutorials

**Traditional approach**: 50+ hours (5 hours per video)
**Time saved**: 27 hours (54%)

---

## Problem-Solving Workflow

**Document debugging and optimization in real-time**

### Perfect for:
- Performance optimization
- Bug hunting
- Refactoring
- Architecture decisions

---

### Setup (5 minutes)

```bash
# Start build logging
Talk to build-logger-agent: "Track my performance optimization work on the API"

# Start recording
/record start api-optimization-journey --screen-and-webcam

# Initial state
/record mark "API currently takes 2000ms - way too slow"
```

---

### Problem-Solving Structure

**Part 1: Problem identification (5 minutes)**
```bash
# Show the problem
- Run slow API calls
- Show response times
- Explain impact on users

/record mark "Problem demonstrated - 2000ms response time"
```

**Part 2: Investigation (15 minutes)**
```bash
# Debug the issue
- Add logging
- Profile the code
- Identify bottleneck

/record mark "Found it - N+1 query problem in database"
```

**Part 3: Solution implementation (20 minutes)**
```bash
# Fix the issue
- Write better query
- Add caching layer
- Optimize algorithm

/record mark "Solution implemented - added Redis caching"
```

**Part 4: Verification (10 minutes)**
```bash
# Test the fix
- Run same API calls
- Show new response times
- Compare before/after

/record mark "SUCCESS - 180ms response time now! 11x faster!"
```

**Part 5: Explanation (10 minutes)**
```bash
# Teach the concept
- Why it was slow
- How the fix works
- When to use this pattern

/record mark "Explained caching strategy"
/record stop
```

---

### Editing for Suspense

```bash
Talk to video-editor-ai: "Edit api-optimization-journey as a problem-solving story:

Structure:
- Cold open: Show the final result first (180ms)
- Hook: 'But it wasn't always this fast...'
- Flashback: Show the problem (2000ms)
- Journey: Investigation + multiple attempts
- Climax: The solution that works
- Resolution: Final results + explanation

Pacing:
- Fast-forward through dead ends
- Keep failed attempts (shows real process)
- Slow down for key insights
- Build suspense before reveal

Add:
- Performance graphs
- Side-by-side comparisons
- Dramatic music during debugging
- Celebration music for success"
```

**Editing output:**
```
✅ Problem-solving story edited

Structure:
0:00-0:15 - Hook: "Watch me make this API 11x faster"
0:15-0:30 - Cold open: Show 180ms result
0:30-1:00 - Flashback: The 2000ms problem
1:00-6:00 - Investigation: Finding the bottleneck
6:00-9:00 - Solution: Implementing the fix
9:00-10:00 - Results: Before/after comparison
10:00-11:00 - Explanation: How it works
11:00-11:30 - Outro: Apply this yourself

Kept:
- Failed attempt #1 (shows real process)
- "Aha moment" reaction
- Genuine excitement at success

Added:
- Performance graph overlay
- Side-by-side comparison
- Suspenseful music during debug
- Celebration music at success

Duration: 11:42
Ready for upload
```

---

## Product Launch Workflow

**Document your product build AND create launch content**

### Timeline: 4 Weeks to Launch

---

### Week 1-3: Build + Document

```bash
# Start build documentation
Talk to build-logger-agent: "Document my [product] build journey:
- Track all git commits
- Identify hero moments
- Suggest video ideas
- Create launch narrative"

# Record key moments
Week 1: /record start product-intro
Week 1: /record start tech-stack-decision
Week 1: /record start first-feature-working

Week 2: /record start core-functionality
Week 2: /record start design-walkthrough
Week 2: /record start integration-challenges

Week 3: /record start testing-and-qa
Week 3: /record start performance-optimization
Week 3: /record start deployment-setup
```

---

### Week 4: Create Launch Content

**Monday: Compile build journey (3 hours)**

```bash
Talk to video-editor-ai: "Create product launch video series:

Source: 3 weeks of build recordings
Target: 5-video series

Video 1: 'I Built [Product] in 3 Weeks' (10 minutes)
- Time-lapse of entire build
- Key features showcase
- Live demo

Video 2: 'Behind the Scenes' (8 minutes)
- Challenges faced
- Design decisions
- Funny moments

Video 3: 'Technical Deep Dive' (15 minutes)
- Architecture walkthrough
- Code explanations
- For developers

Video 4: 'Product Demo' (5 minutes)
- User-focused tutorial
- Key features
- For customers

Video 5: 'Lessons Learned' (7 minutes)
- What went well
- What I'd do differently
- Advice for builders"
```

**Tuesday: Create marketing assets (2 hours)**

```bash
Talk to thumbnail-designer: "Create launch assets:
- 5 YouTube thumbnails
- Product Hunt image (1270x760px)
- Twitter launch card
- LinkedIn launch banner
- Website hero image"

Talk to seo-metadata-generator: "Optimize all launch content:
- Video titles and descriptions
- Product Hunt copy
- Social media posts
- Blog post announcement
- Email newsletter"
```

**Wednesday: Set up distribution (1 hour)**

```bash
Talk to distribution-automator: "Schedule product launch:

Launch day: This Friday 6am PST

6:00am - Product Hunt launch
6:05am - YouTube video #1 (main launch video)
6:10am - Twitter thread (10 tweets + video)
6:15am - LinkedIn post (article + video)
6:20am - Reddit posts (r/SideProject, r/startups)
6:30am - Email newsletter (to all subscribers)
7:00am - Hacker News post
8:00am - Indie Hackers post

Throughout day:
- Monitor Product Hunt comments (respond to all)
- Share updates on Twitter (every 2 hours)
- Post remaining videos (1 per day over 5 days)"
```

---

### Launch Day Execution

**Automated sequence:**

```
✅ 6:00am - Product Hunt launched
   Status: #1 Product of the Day
   Votes: 247 → 532 by evening

✅ 6:05am - YouTube video live
   Views: 2.3K first day
   Comments: 87 (responding to all)

✅ 6:10am - Twitter thread
   Impressions: 15K
   Likes: 234
   Retweets: 67

✅ 6:15am - LinkedIn post
   Views: 3.2K
   Engagements: 156

✅ 6:30am - Email newsletter
   Sent: 1,847
   Opened: 38% (703 opens)
   Clicked: 12% (221 clicks)

✅ Throughout day - Engagement
   Product Hunt: All comments responded to
   Twitter: 

…(truncated)