Skip to content

tim-hub/powerball-harness / .claude/skills/generate-video

generate-video

Verified

Generates product demo videos and release walkthroughs via Remotion. Use when creating video documentation or animated demos.

FileKindSize
SKILL.mdskill md6.6 KB
assets/backgrounds/backgrounds.jsonconfig4.9 KB
assets/sounds/sounds.jsonconfig5.7 KB
package.jsonmanifest710 B
references/MIGRATION-11.2.mdmarkdown7.9 KB
references/analyzer.mdmarkdown4.5 KB
references/asset-customization.mdmarkdown11.2 KB
references/best-practices.mdmarkdown8.6 KB
references/direction-guide.mdmarkdown14.6 KB
references/generator.mdmarkdown25.9 KB
references/image-generator.mdmarkdown9.0 KB
references/image-patterns.mdmarkdown14.5 KB
references/image-quality-check.mdmarkdown6.9 KB
references/naming-conventions.mdmarkdown6.0 KB
references/planner.mdmarkdown7.6 KB
references/visual-effects.mdmarkdown11.0 KB
remotion/components/BackgroundLayer.tsxother7.5 KB
remotion/components/EmphasisBox.tsxother5.9 KB
remotion/components/ProgressIndicator.tsxother6.8 KB
remotion/components/README.mdmarkdown8.5 KB
remotion/components/TransitionWrapper.tsxother5.7 KB
remotion/components/index.tsscript1004 B
remotion/tsconfig.jsonconfig617 B
schemas/README.mdmarkdown8.1 KB
schemas/animation.schema.jsonconfig5.2 KB
schemas/assets.manifest.schema.jsonconfig5.9 KB
schemas/character.schema.jsonconfig16.0 KB
schemas/direction.schema.jsonconfig4.5 KB
schemas/emphasis.schema.jsonconfig8.6 KB
schemas/examples/scenario-example.jsonconfig1.6 KB
schemas/examples/scene-example.jsonconfig1.6 KB
schemas/examples/video-script-example.jsonconfig5.1 KB
schemas/examples/visual-patterns/comparison-example.jsonconfig1.0 KB
schemas/examples/visual-patterns/concept-example.jsonconfig2.1 KB
schemas/examples/visual-patterns/flow-example.jsonconfig1.8 KB
schemas/examples/visual-patterns/highlight-example.jsonconfig745 B
schemas/scenario.schema.jsonconfig3.6 KB
schemas/scene.schema.jsonconfig8.2 KB
schemas/validate-schemas-basic.jsscript2.7 KB
schemas/validate-schemas.jsscript6.6 KB
schemas/video-script.schema.jsonconfig7.6 KB
schemas/visual-patterns.schema.jsonconfig14.2 KB
scripts/README.mdmarkdown7.4 KB
scripts/generate-schemas.jsexecutablescript6.2 KB
scripts/load-assets.jsexecutablescript14.1 KB
scripts/merge-scenes.jsexecutablescript15.0 KB
scripts/render-video.jsexecutablescript14.0 KB
scripts/template-registry.jsexecutablescript10.0 KB
scripts/validate-scenario.jsexecutablescript8.0 KB
scripts/validate-scene.jsexecutablescript4.3 KB
scripts/validate-video.jsexecutablescript13.0 KB
src/schemas/animation.tsscript3.7 KB
src/schemas/assets.manifest.tsscript2.8 KB
src/schemas/character.tsscript6.5 KB
src/schemas/direction.tsscript3.2 KB
src/schemas/emphasis.tsscript5.2 KB
src/schemas/index.tsscript423 B
src/schemas/scenario.tsscript2.7 KB
src/schemas/scene.tsscript5.5 KB
src/schemas/video-script.tsscript9.4 KB
src/schemas/visual-patterns.tsscript8.2 KB
src/types/README.mdmarkdown4.1 KB
src/types/components.tsscript6.0 KB
src/types/index.tsscript108 B
src/utils/README.mdmarkdown6.1 KB
src/utils/converters.jsscript5.9 KB
src/utils/converters.tsscript5.7 KB
src/utils/index.tsscript109 B
templates/image-prompts/comparison.txtmarkdown1.3 KB
templates/image-prompts/concept.txtmarkdown2.3 KB
templates/image-prompts/flow.txtmarkdown2.8 KB
templates/image-prompts/highlight.txtmarkdown3.2 KB
templates/intro-3min.jsonconfig8.9 KB
templates/teaser-90s.jsonconfig7.0 KB
tests/asset-loader.test.jsscript12.1 KB
tests/character-schema.test.jsscript7.9 KB
tests/converters.test.jsscript8.3 KB
tests/determinism.test.jsscript11.4 KB
tests/e2e/merge-e2e.test.jsscript13.3 KB
tests/e2e/render.test.jsscript6.1 KB
tests/fixtures/minimal-video-script.jsonconfig1.2 KB
tests/merge-scenes.test.jsscript17.2 KB
tests/schema-validation.test.jsscript3.7 KB
tests/validation-integration.test.jsscript12.9 KB
tests/visual-patterns.test.jsscript12.1 KB

references/planner.md

View on GitHub
# Video Planner - Scenario Planner

Automatically proposes scene composition from analysis results, then confirms and adjusts with the user.

---

## Overview

This is the scenario planner executed in Step 2 of `/generate-video`.
It receives output from analyzer.md and proposes the optimal scene composition.

> **Important**: Scene composition must follow the funnel-specific guidelines in [best-practices.md](best-practices.md)

## Input

Analysis results from analyzer.md:
- Project information (name, description)
- Detected feature list
- Recommended video type
- Recent changes

---

## Funnel-Specific Template Selection

### Step 0: Confirm Purpose (Required)

Confirm the video's purpose and select the appropriate template.

| Purpose (Funnel) | Video Type | Target Length | Composition Core |
|-------------------|------------|---------------|------------------|
| Awareness to Interest | LP/Ad Teaser | 30-90 sec | Pain → Result → CTA |
| Interest → Consideration | Intro Demo | 2-3 min | Complete 1 use case |
| Consideration → Conviction | Demo/Release Notes | 2-5 min | Preemptively address objections |
| Conviction → Decision | Walkthrough | 5-30 min | Real operations + evidence |
| Retention/Utilization | Onboarding | 30 sec - few min | Shortest path to Aha moment |

### 90-Second Teaser Template

**Use case**: LP/Ads, Awareness to Interest funnel

```
0:00-0:05 (150f)  → HookScene: Pain or desired outcome
0:05-0:15 (300f)  → ProblemPromise: Target user and promise
0:15-0:55 (1200f) → WorkflowDemo: Signature workflow
0:55-1:10 (450f)  → Differentiator: Basis for differentiation
1:10-1:30 (600f)  → CTA: Next step
```

### 3-Minute Intro Demo Template

**Use case**: Consideration, Interest → Consideration funnel

```
0:00-0:10 (300f)  → Hook: Conclusion + pain
0:10-0:30 (600f)  → UseCase: Use case declaration
0:30-2:20 (3300f) → Demo: Complete walkthrough on real screen
2:20-2:50 (900f)  → Objection: Address one common concern
2:50-3:00 (300f)  → CTA: Call to action
```

### 20-Minute Walkthrough Template

**Use case**: Decision, Conviction → Decision funnel

```
0:00-1:00   → Intro: Target audience and challenges
1:00-8:00   → BasicFlow: Basic flow
8:00-12:00  → Objections: Top 2 objections
12:00-15:00 → Security: Management/security
15:00-20:00 → CaseStudy+CTA: Success stories + CTA
```

## Scene Templates

### Common Scenes

| Scene | Recommended Duration | Content | Required |
|-------|---------------------|---------|----------|
| **Intro** | 3-5 sec | Logo + tagline + fade in | Yes |
| **CTA** | 3-5 sec | URL + contact + fade out | Yes |

### Product Demo Scenes

| Scene | Recommended Duration | Content |
|-------|---------------------|---------|
| **Feature Introduction** | 5-10 sec | Feature name + one-line description |
| **UI Demo** | 10-30 sec | Playwright capture |
| **Highlight** | 5-10 sec | Emphasize key characteristics |

### Architecture Explanation Scenes

| Scene | Recommended Duration | Content |
|-------|---------------------|---------|
| **Overview Diagram** | 5-10 sec | Overall architecture Mermaid diagram |
| **Detailed Explanation** | 10-20 sec | Zoom into each component |
| **Data Flow** | 10-15 sec | Sequence diagram animation |

### Release Notes Scenes

| Scene | Recommended Duration | Content |
|-------|---------------------|---------|
| **Version Display** | 3-5 sec | vX.Y.Z + release date |
| **Change List** | 5-15 sec | Added/Changed/Fixed animation |
| **Before/After** | 10-20 sec | Side-by-side UI change comparison |
| **New Feature Demo** | 10-30 sec | UI demo of added features |

---

## Scenario Generation Logic

### Step 1: Template Selection by Video Type

```
Select base template based on recommended video type:
    |
    +-- LP/Ad Teaser (30-90 sec)
    |   +-- Hook → ProblemPromise → WorkflowDemo → Differentiator → CTA
    |
    +-- Intro Demo (2-3 min)
    |   +-- Hook → UseCase Declaration → Real Screen Demo → Objection → CTA
    |
    +-- Release Notes (1-3 min)
    |   +-- Hook → Version → Before/After → New Feature Demo → CTA
    |
    +-- Architecture Explanation (5-30 min)
    |   +-- Intro → Overview Diagram → Detailed Explanation x N → Data Flow → Management/Security → CTA
    |
    +-- Onboarding (30 sec - few min)
        +-- Welcome → Quick Win → Next Steps
```

**Key Principles**:
- Don't show logo or company intro for too long at the start (prevent drop-off)
- Place CTAs not only at the end but also in the middle
- Tell a "pain → solution" story, not a feature list

### Step 2: Generate Scenes from Detected Features

```python
# Pseudocode
for feature in detected_features:
    if feature.type == "auth":
        add_scene("Auth Flow Demo", duration=15, source="playwright")
    elif feature.type == "dashboard":
        add_scene("Dashboard Introduction", duration=20, source="playwright")
    elif feature.type == "api":
        add_scene("API Overview", duration=10, source="mermaid")
```

### Step 3: Duration Optimization

| Video Length | Recommended Use | Scene Count Guide |
|-------------|-----------------|-------------------|
| 15 sec | Social media ads | 3-4 |
| 30 sec | Short videos | 5-6 |
| 60 sec | Standard demo | 8-10 |
| 2-3 min | Detailed explanation | 15-20 |

---

## User Confirmation Flow

### Proposal Display

```markdown
🎬 Scenario Plan

**Video Type**: Product Demo
**Total Duration**: 45 sec

| # | Scene | Duration | Content | Source |
|---|-------|----------|---------|--------|
| 1 | Intro | 5 sec | MyApp - Task management made easy | Template |
| 2 | Auth Flow | 15 sec | Login screen demo | Playwright |
| 3 | Dashboard | 20 sec | Main feature introduction | Playwright |
| 4 | CTA | 5 sec | myapp.com | Template |

Is this composition acceptable?
1. OK, start generation
2. I want to edit
3. Cancel
```

### AskUserQuestion Implementation

```
AskUserQuestion:
  question: "Would you like to generate the video with this scenario?"
  header: "Scenario Confirmation"
  options:
    - label: "OK, start generation"
      description: "Generate the video with this scene composition"
    - label: "I want to edit"
      description: "Add/remove/modify scenes"
    - label: "Cancel"
      description: "Cancel video generation"
```

### Edit Mode

When the user selects "I want to edit":

```markdown
📝 Scenario Editor

You can edit with the following commands:

- **Add**: "Add a demo of Feature X"
- **Remove**: "Remove scene 2"
- **Modify**: "Shorten intro to 3 seconds"
- **Swap**: "Swap scenes 2 and 3"
- **Done**: "This is fine"

What would you like to edit?
```

---

## Output Format

planner.md output (input to generator.md):

```yaml
video:
  type: "product-demo"
  total_duration: 45
  resolution: "1080p"
  fps: 30

scenes:
  - id: 1
    name: "intro"
    duration: 5
    template: "intro"
    content:
      title: "MyApp"
      tagline: "Task management made easy"
      logo: "public/logo.svg"

  - id: 2
    name: "auth-demo"
    duration: 15
    template: "ui-demo"
    source: "playwright"
    content:
      url: "http://localhost:3000/login"
      actions:
        - click: "[data-testid=email-input]"
        - type: "user@example.com"
        - click: "[data-testid=login-button]"

  - id: 3
    name: "dashboard"
    duration: 20
    template: "ui-demo"
    source: "playwright"
    content:
      url: "http://localhost:3000/dashboard"
      actions:
        - wait: 1000
        - scroll: "down"

  - id: 4
    name: "cta"
    duration: 5
    template: "cta"
    content:
      url: "https://myapp.com"
      text: "Try it now"
```

---

## Notes

- If there are too many scenes, lower-priority ones are automatically excluded from the proposal
- Users can manually add scenes
- Scenes with Playwright source require the app to be running
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 198kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 198kUpdated Claude CodeCodexVerifiedInstall