← Back to list
🎬

remotion Checked

Toolkit-specific Remotion patterns — custom transitions, shared components, and project conventio…
🎬 Video & Motion skills By calesthio Version v1.0.0 Added 2026-09-07 Updated 2026-09-07 Source ↗
7.2Overall rating
2Views
5Downloads
56.5kStars

Installation

🤖 Install via AI

Copy the prompt below and send it to your AI assistant (e.g. Claude Code) — it will follow the instructions and install automatically.

Install the "remotion" skill by following the instructions at https://skill123.me/install/remotion.
⌨️ Command line install

Run in your terminal — downloads and installs to ~/.claude/skills/.

curl -fsSL https://skill123.me/install/remotion.sh | bash
📦 Download ZIP

Download the zip and extract it into your skills directory (e.g. ~/.claude/skills/), then restart your session.

⬇ Download v1.0.0 · 7 KB
📊 Static rating
7.2/10
Trigger
6.5
Structure
8.7
Workflow
4.4
Content
9.0
Engineering
7.0
Security
9.5

Six-dimension rubric with reviewer rationale.

View scorecard ↓
🛡 Dynamic test
—

Not live-tested yet — this skill is rated on static analysis only.

About this skill

Toolkit-specific Remotion patterns — custom transitions, shared components, and project conventions. For core Remotion framework knowledge (hooks, animations, rendering, etc.), see the remotion-official skill.

Remotion — Toolkit Extensions

> **Core Remotion knowledge** lives in .claude/skills/remotion-official/ (synced from the official remotion-dev/skills repo). This file covers **toolkit-specific** patterns only.

Documentation

Toolkit-specific Remotion patterns — custom transitions, shared components, and project conventions. For core Remotion framework knowledge (hooks, animations, rendering, etc.), see the remotion-official skill.

Remotion — Toolkit Extensions

> **Core Remotion knowledge** lives in .claude/skills/remotion-official/ (synced from the official remotion-dev/skills repo). This file covers **toolkit-specific** patterns only.

Shared Components

Reusable video components in lib/components/. Import in templates via:


import { AnimatedBackground, SlideTransition, Label } from '../../../../lib/components';

| Component | Purpose |

|-----------|---------|

| AnimatedBackground | Floating shapes background (variants: subtle, tech, warm, dark) |

| SlideTransition | Scene transitions (fade, zoom, slide-up, blur-fade) |

| Label | Floating label badge with optional JIRA reference |

| Vignette | Cinematic edge darkening overlay |

| LogoWatermark | Corner logo branding |

| SplitScreen | Side-by-side video comparison |

| NarratorPiP | Picture-in-picture presenter overlay |

| Envelope | 3D envelope with opening flap animation |

| PointingHand | Animated hand emoji with slide-in and pulse |

| MazeDecoration | Animated isometric grid decoration for corners |

Custom Transitions

The toolkit includes a transitions library at lib/transitions/ for scene-to-scene effects beyond the official @remotion/transitions package.

### Using TransitionSeries


import { TransitionSeries, linearTiming } from '@remotion/transitions';
// Import custom transitions from lib (adjust path based on your project location)
import { glitch, lightLeak, clockWipe, checkerboard } from '../../../../lib/transitions';
// Or import from @remotion/transitions for official ones
import { slide, fade } from '@remotion/transitions/slide';

<TransitionSeries>
  <TransitionSeries.Sequence durationInFrames={90}>
    <TitleSlide />
  </TransitionSeries.Sequence>
  <TransitionSeries.Transition
    presentation={glitch({ intensity: 0.8 })}
    timing={linearTiming({ durationInFrames: 30 })}
  />
  <TransitionSeries.Sequence durationInFrames={120}>
    <ContentSlide />
  </TransitionSeries.Sequence>
</TransitionSeries>

### Available Custom Transitions

View full documentation

| Transition | Options | Best For |

|------------|---------|----------|

| glitch() | intensity, slices, rgbShift | Tech demos, edgy reveals, cyberpunk |

| rgbSplit() | direction, displacement | Modern tech, energetic transitions |

| zoomBlur() | direction, blurAmount | CTAs, high-energy moments, impact |

| lightLeak() | temperature, direction | Celebrations, film aesthetic, warm moments |

| clockWipe() | startAngle, direction, segments | Time-related content, playful reveals |

| pixelate() | maxBlockSize, gridSize, scanlines, glitchArtifacts, randomness | Retro/gaming, digital transformations |

| checkerboard() | gridSize, pattern, stagger, squareAnimation | Playful reveals, structured transitions |

**Checkerboard patterns:** sequential, random, diagonal, alternating, spiral, rows, columns, center-out, corners-in

### Transition Examples


// Tech/cyberpunk feel
glitch({ intensity: 0.8, slices: 8, rgbShift: true })

// Warm celebration
lightLeak({ temperature: 'warm', direction: 'right' })

// High energy zoom
zoomBlur({ direction: 'in', blurAmount: 20 })

// Chromatic aberration
rgbSplit({ direction: 'diagonal', displacement: 30 })

// Clock sweep reveal
clockWipe({ direction: 'clockwise', startAngle: 0 })

// Retro pixelation
pixelate({ maxBlockSize: 50, glitchArtifacts: true })

// Checkerboard patterns
checkerboard({ pattern: 'diagonal', gridSize: 8 })
checkerboard({ pattern: 'spiral', gridSize: 10 })
checkerboard({ pattern: 'center-out', squareAnimation: 'scale' })

### Transition Duration Guidelines

| Type | Frames | Notes |

|------|--------|-------|

| Quick cut | 15-20 | Fast, punchy |

| Standard | 30-45 | Most common |

| Dramatic | 50-60 | Slow reveals |

| Glitch effects | 20-30 | Should feel sudden |

| Light leak | 45-60 | Needs time to sweep |

### Preview Transitions

Run the showcase gallery to see all transitions:


cd showcase/transitions && npm run studio

Toolkit Best Practices

1. **Frame-based animations only** — Avoid CSS transitions/animations; they cause flickering during render

2. **Use fps from useVideoConfig()** — Make animations frame-rate independent

3. **Clamp interpolations** — Use extrapolateRight: 'clamp' to prevent runaway values

4. **Use OffthreadVideo** — Better performance than <Video> for complex compositions

5. **delayRender for async** — Always block rendering until data is ready

6. **staticFile for assets** — Reference files from public/ folder correctly

7. **All projects use 30fps** — Timing: frames = seconds × 30

8. **playbackRate must be constant** — For variable/extreme speeds, pre-process with FFmpeg

Project Timing Conventions

| Scene Type | Duration | Notes |

|------------|----------|-------|

| Title | 3-5s (90-150f) | Logo + headline |

| Overview | 10-20s | 3-5 bullet points |

| Demo | 10-30s | Adjust playbackRate to fit |

| Stats | 8-12s | 3-4 stat cards |

| Credits | 5-10s | Quick fade |

**Pacing:** ~150 words/minute for voiceover. Voiceover drives timing.

Advanced API

For detailed API documentation on all hooks, components, renderer, Lambda, and Player APIs, see reference.md (reference.md).

License Note

Remotion has a special license. Companies may need to obtain a license for commercial use. Check https://remotion.dev/license

---

Feedback & Contributions

If this skill is missing information or could be improved:

  • **Missing a pattern?** Describe what you needed
  • **Found an error?** Let me know what's wrong
  • **Want to contribute?** I can help you:

1. Update this skill with improvements

2. Create a PR to github.com/digitalsamba/claude-code-video-toolkit

Just say "improve this skill" and I'll guide you through updating .claude/skills/remotion/SKILL.md.

Score breakdown

Trigger
6.5
What and delegation boundary to remotion-official are clear, but few user trigger scenarios
Structure
8.7
160-line SKILL.md with 499-line API reference offloaded; reference.md sits at root not references/
Workflow
4.4
Component and transition catalogs plus best practices, but no stepwise workflow or error handling
Content
9.0
Concrete tables with option values and frame timings, clean formatting
Engineering
7.0
Frontmatter valid and reference.md exists, but lib/ imports and remotion-official skill are not shipped
Security
9.5
Static content only, official remotion.dev and GitHub links, no scripts or secrets
Useful toolkit-specific Remotion companion with well-offloaded API reference and concrete transition tables, but it is a pattern catalog with no workflow, guards, or verification, and depends on non-shipped toolkit paths and a sibling skill.