본문으로 건너뛰기
cccskills
무료GitHub에 공개

remotion-transitions

This skill should be used when the user asks to create custom Remotion transitions, asks about "cool transitions", "cinematic transitions", "striped transitions", "glitch transitions", "custom TransitionPresentation", or wants to build scene-to-scene transitions in Remotion beyond the built-in library. Also triggers for "how to make transitions in Remotion", "custom transition", "high-energy transitions", "energy transitions", "branded transitions".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(9)

  • SKILL.md2.6 KB
  • .claude-plugin/plugin.json726 B
  • CHANGELOG.md676 B
  • LICENSE1.0 KB
  • README.md2.5 KB
  • references/animation-math.md5.1 KB
  • references/custom-transition-pattern.md4.3 KB
  • references/transition-catalog.md14.0 KB
  • skills-lock.json242 B

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Remotion Custom Transitions

This skill teaches you how to build production-grade, high-energy custom transitions in Remotion using the TransitionPresentation API — the same pattern used in Fyltr's Instagram Reel campaign.

Quick Reference

  • Custom Transition Pattern — The TransitionPresentation API, the exact component shape, and how timing works
  • Transition Catalog — 6 battle-tested transitions with full source: Striped Slam, Zoom Punch, Diagonal Reveal, Emerald Burst, Vertical Shutter, Glitch Slam
  • Animation Math — Easing functions, stagger formulas, spring configs, and the clamp extrapolation pattern used throughout

Core Concept

Remotion's @remotion/transitions package exposes a TransitionPresentation type. You implement a component that receives:

  • presentationProgress — 0 at transition start → 1 at transition end
  • presentationDirection — "exiting" (old scene) or "entering" (new scene)
  • children — the scene being wrapped

The same component wraps both scenes simultaneously. You animate different things depending on direction.

Golden Rules

  1. Never use CSS transitions/animations — all motion via interpolate() / spring() driven by presentationProgress
  2. Never use useCurrentFrame() inside a transition component — use presentationProgress only
  3. Always return { component, props: {} } — the props object must exist even if empty
  4. Create instances outside components at module level to keep them stable across re-renders
  5. Pair with linearTiming (for dramatic frame-perfect transitions) or springTiming (for springy physics)

When to Load References

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

이 스킬의 문제 신고