remotion

digitalsamba/claude-code-video-toolkit · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/digitalsamba/claude-code-video-toolkit --skill remotion
0 commentsdiscussion
summary

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

skill.md

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

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.

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.

how to use remotion

How to use remotion on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add remotion
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/digitalsamba/claude-code-video-toolkit --skill remotion

The skills CLI fetches remotion from GitHub repository digitalsamba/claude-code-video-toolkit and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/remotion

Reload or restart Cursor to activate remotion. Access the skill through slash commands (e.g., /remotion) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.667 reviews
  • Tariq Lopez· Dec 28, 2024

    Registry listing for remotion matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Amelia Lopez· Dec 28, 2024

    Useful defaults in remotion — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Liam Sharma· Dec 24, 2024

    remotion is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Zara White· Dec 20, 2024

    Solid pick for teams standardizing on skills: remotion is focused, and the summary matches what you get after install.

  • Dev Smith· Dec 16, 2024

    I recommend remotion for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Olivia Bhatia· Dec 12, 2024

    remotion reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Olivia Chawla· Dec 4, 2024

    remotion fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Layla Ramirez· Nov 19, 2024

    remotion reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Yuki Liu· Nov 19, 2024

    We added remotion from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Aanya Sharma· Nov 15, 2024

    Keeps context tight: remotion is the kind of skill you can hand to a new teammate without a long onboarding doc.

showing 1-10 of 67

1 / 7