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

schemas/README.md

View on GitHub
# Video Generation JSON Schemas

JSON Schema definitions for the video generation workflow. These schemas define the structure of scenarios, scenes, and complete video scripts.

## Schema Files

| Schema | Purpose | Version |
|--------|---------|---------|
| **scenario.schema.json** | High-level scenario structure with sections | 1.0.0 |
| **scene.schema.json** | Individual scene definition with content and direction | 1.0.0 |
| **video-script.schema.json** | Complete video script with metadata and settings | 1.0.0 |

## Schema Overview

```
Scenario (High-level structure)
    |
    +-- Section 1 (Intro)
    |   +-- Scene 1.1
    |   +-- Scene 1.2
    |
    +-- Section 2 (Demo)
    |   +-- Scene 2.1
    |   +-- Scene 2.2
    |   +-- Scene 2.3
    |
    +-- Section 3 (CTA)
        +-- Scene 3.1

Video Script = Metadata + Scenes + Output Settings
```

## Usage

### 1. Basic Validation (No Dependencies)

```bash
node validate-schemas-basic.js
```

This performs basic JSON and structure validation without external dependencies.

### 2. Full Validation with ajv

```bash
# Install dependencies first
npm install ajv ajv-formats

# Run full validation
node validate-schemas.js
```

### 3. Programmatic Usage

```javascript
const Ajv = require('ajv');
const addFormats = require('ajv-formats');
const fs = require('fs');

// Initialize ajv
const ajv = new Ajv({ strict: false });
addFormats(ajv);

// Load schemas
const sceneSchema = JSON.parse(fs.readFileSync('scene.schema.json'));
const videoScriptSchema = JSON.parse(fs.readFileSync('video-script.schema.json'));

// Add schemas
ajv.addSchema(sceneSchema);
ajv.addSchema(videoScriptSchema);

// Validate data
const validate = ajv.compile(videoScriptSchema);
const valid = validate(myVideoScriptData);

if (!valid) {
  console.error(validate.errors);
}
```

## Schema Details

### scenario.schema.json

Defines the high-level structure of a video scenario.

**Key Fields**:
- `title`: Scenario title
- `description`: Purpose and content overview
- `sections[]`: Ordered list of sections
  - `id`: Unique section identifier
  - `title`: Section name
  - `description`: Section purpose
  - `order`: Display order (0-indexed)
  - `duration_estimate_ms`: Estimated duration
- `metadata`: Generation metadata
  - `version`: Schema version
  - `generated_at`: ISO 8601 timestamp
  - `video_type`: Type enum (lp-teaser, intro-demo, etc.)
  - `target_funnel`: Marketing funnel stage

**Example**: See [examples/scenario-example.json](examples/scenario-example.json)

### scene.schema.json

Defines an individual video scene with content, visual direction, and assets.

**Key Fields**:
- `scene_id`: Unique scene identifier
- `section_id`: Parent section reference
- `order`: Order within section
- `type`: Scene type enum (intro, ui-demo, cta, etc.)
- `content`: Scene content
  - `text`: Primary text
  - `image`: Image asset path
  - `duration_ms`: Scene duration
  - `url`: For Playwright captures
  - `actions[]`: UI automation actions
  - `mermaid`: Diagram definition
  - `code`: Code snippet with highlights
- `direction`: Visual effects
  - `transition`: In/out transitions
  - `emphasis`: Visual emphasis effects
  - `background`: Background configuration
  - `camera`: Camera movement (3D)
- `assets[]`: Scene assets
  - `type`: Asset type (image, video, audio, font)
  - `source`: Path or URL
  - `generated`: AI-generated flag
- `audio`: Audio configuration
  - `narration`: Voice-over
  - `sfx[]`: Sound effects

**Example**: See [examples/scene-example.json](examples/scene-example.json)

### video-script.schema.json

Complete video script with all scenes, metadata, and output settings.

**Key Fields**:
- `metadata`: Video metadata
  - `title`: Video title
  - `version`: Script version
  - `created_at`: Creation timestamp
  - `video_type`: Type enum
  - `scenario_id`: Reference to source scenario
- `scenes[]`: Array of scene objects (references scene.schema.json)
- `total_duration_ms`: Total video duration
- `output_settings`: Rendering configuration
  - `width`, `height`: Resolution
  - `fps`: Frame rate (24, 30, 60)
  - `codec`: Video codec (h264, h265, vp9, av1)
  - `format`: Output format (mp4, webm, mov, gif)
  - `quality`: Quality preset
  - `preset`: Resolution preset (1080p, 4k, etc.)
- `audio_settings`: Global audio
  - `bgm`: Background music configuration
  - `master_volume`: Master volume control
- `branding`: Brand configuration
  - `logo`: Logo path
  - `colors`: Brand colors
  - `fonts`: Font configuration
- `transitions`: Global transition settings

**Example**: See [examples/video-script-example.json](examples/video-script-example.json)

## Scene Types

| Type | Description | Use Case |
|------|-------------|----------|
| `intro` | Opening title/logo | First scene, brand introduction |
| `ui-demo` | UI walkthrough with Playwright | Feature demonstrations |
| `architecture` | System architecture diagram | Technical explanations |
| `code-highlight` | Code snippet with highlights | Developer-focused content |
| `changelog` | Release notes display | Version updates |
| `cta` | Call to action | Final scene, conversions |
| `feature-highlight` | Specific feature focus | Feature marketing |
| `problem-promise` | Problem + solution statement | Value proposition |
| `workflow` | Multi-step workflow demo | Process explanations |
| `objection` | Address common objections | Objection handling |
| `custom` | Custom scene type | Flexible usage |

## Video Types (video_type)

| Type | Duration | Funnel Stage | Purpose |
|------|----------|--------------|---------|
| `lp-teaser` | 30-90s | Awareness | Landing page, social ads |
| `intro-demo` | 2-3min | Interest | Product introduction |
| `release-notes` | 1-3min | Consideration | Feature updates |
| `architecture` | 5-30min | Decision | Technical deep-dive |
| `onboarding` | 30s-3min | Retention | User onboarding |
| `custom` | Variable | Any | Custom purpose |

## Audio Sync Rules

When using narration, follow these timing rules:

| Rule | Value | Reason |
|------|-------|--------|
| **Audio start** | Scene start + 1000ms | 1-second breathing room |
| **Scene length** | 1000ms + audio length + 500ms | Padding for transitions |
| **Transition** | 450-500ms overlap | Smooth cross-fade |
| **Scene start calc** | Previous scene start + duration - 450ms | Overlap handling |

**Always check audio duration first**:
```bash
ffprobe -v error -show_entries format=duration \
  -of default=noprint_wrappers=1:nokey=1 audio.mp3
```

## Validation

### Required Fields by Schema

**scenario.schema.json**:
- ✅ title, description, sections, metadata

**scene.schema.json**:
- ✅ scene_id, section_id, order, type, content
- ✅ content.duration_ms

**video-script.schema.json**:
- ✅ metadata, scenes, total_duration_ms, output_settings
- ✅ output_settings: width, height, fps
- ✅ metadata: title, version, created_at

### Common Validation Errors

| Error | Cause | Solution |
|-------|-------|----------|
| `Missing required property` | Required field not provided | Add the missing field |
| `Invalid enum value` | Invalid type/format value | Use allowed enum values |
| `Pattern mismatch` | ID format incorrect | Use lowercase-with-hyphens |
| `Invalid date-time` | Timestamp format wrong | Use ISO 8601 format |
| `Invalid $ref` | Schema reference broken | Ensure scene.schema.json is loaded |

## Examples

All example files are located in the `examples/` directory:

1. **scenario-example.json** - 90-second teaser scenario
2. **scene-example.json** - Intro scene with effects
3. **video-script-example.json** - Complete video script

## Integration

These schemas are used by:

1. **Planner** (planner.md) - Generates scenario and scene structures
2. **Generator** (generator.md) - Reads video-script.json and renders video
3. **Validation** - Ensures generated data conforms to expected structure

## Version History

| Version | Date | Changes |
|---------|------|---------|
| 1.0.0 | 2026-02-02 | Initial release with core schemas |

## References

- [JSON Schema Draft-07](https://json-schema.org/draft-07/json-schema-release-notes.html)
- [ajv Documentation](https://ajv.js.org/)
- [Best Practices Guide](../references/best-practices.md)
- [Planner Reference](../references/planner.md)
- [Generator Reference](../references/generator.md)
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