agentleFS
casooncasoon/ai-agent-config/skills/remotion/SKILL.md

remotion

Skill1 starsChanged 47 days agoMITView on GitHub

Remotion workflow for animated explainer videos embedded in Astro sites — composition setup, render pipeline (ProRes → MP4 → WebP poster), frontmatter integration, and Astro component embedding. Use when building or integrating Remotion videos into an Astro project.

37 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use aeon-update, auto-workflow and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronjmarsSkill

    aeon-update

    Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.

    Also in 4 projects that use this

  • aaronjmarsSkill

    auto-workflow

    Two-mode aeon.yml workflow builder - analyze inspects URLs and emits a tiered, signal-verified skill-enablement plan plus an aeon.yml diff; enable flips slugs to enabled:true and opens a PR.

    Also in 4 projects that use this

  • +10 more from aaronjmars

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 29 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use interpolate with extrapolateLeft/Right: 'clamp' for all animations.

    line 29
  2. Distinctive:

    Always render a ProRes master first, then derive MP4 from it — never render MP4 directly (lower quality, no intermediate for re-encoding):

    line 34
  3. Very specific:

    Add video fields to the content schema (content.config.ts):

    line 63
  4. Very specific:

    Keep a separate teaserImage for OG/social — video poster is not a substitute.

    line 77

“Common” is measured: kept by at least 6 in 10 of the 29 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Remotion

Remotion renders React components to video. Typical use: short animated explainers (30–120 s) embedded as hero elements in articles or landing pages.

Composition setup

Register in src/Root.tsx:

<Composition
  id="MyCompositionId"
  component={MyComponent}
  defaultProps={{}}
  durationInFrames={900}
  fps={30}
  width={1920}
  height={1080}
/>

Standard spec: 1920×1080, 30 fps. Duration: 30 s = 900 frames, 60 s = 1800 frames.

Use interpolate with extrapolateLeft/Right: 'clamp' for all animations. Crossfade scenes with a 10–12 frame overlap.

Render pipeline

Always render a ProRes master first, then derive MP4 from it — never render MP4 directly (lower quality, no intermediate for re-encoding):

npm run render:final -- <CompositionId>

Expected output in out/<CompositionId>/:

FilePurpose
master.movProRes master — internal only, do not deploy
720p.mp4H.264 delivery file
poster-720p.pngFrame at ~2 s — convert to WebP before deploying

Typical sizes for a 30 s animation: 720p MP4 ≈ 500 KB–2 MB. No CDN needed below ~4 MB.

Poster conversion

PNG frames are large (600 KB–1 MB). Convert to WebP immediately:

cwebp -q 85 out/<CompositionId>/poster-720p.png -o out/<CompositionId>/poster-720p.webp

Typical WebP result: 15–40 KB.

Astro frontmatter integration

Add video fields to the content schema (content.config.ts):

heroVideo:       z.string().optional(),
heroVideoPoster: z.string().optional(),

Reference in MDX frontmatter:

heroVideo: '/videos/<CompositionId>/720p.mp4'
heroVideoPoster: '/videos/<CompositionId>/poster-720p.webp'

Keep a separate teaserImage for OG/social — video poster is not a substitute.

Embedding in Astro

Minimal inline embed:

{heroVideo && (
  <video
    src={heroVideo}
    poster={heroVideoPoster}
    autoplay muted loop playsinline
    aria-label="Animated explainer"
  />
)}

For a reusable component, accept src, poster, title, and an optional class prop. Add prefers-reduced-motion support:

<video
  class:list={['hero-video', className]}
  src={src}
  poster={poster}
  autoplay={!prefersReducedMotion}
  muted loop playsinline
  aria-label={title}
/>

What NOT to add

  • VideoObject structured data — only useful when video is the primary page content, not a decorative header element.
  • Captions — not needed for silent/music-only animation-only videos.
  • WebM variant — H.264 MP4 with faststart covers all modern browsers.
  • Cloudflare Stream or similar CDN — only necessary above ~4 MB per video.
  • Direct MP4 render — always go through a ProRes master.

Narrative structure for explainers

  1. Hook — show the visible symptom or the unseen mechanism.
  2. Mechanics — reveal the internal structure (loop, pipeline, decision tree).
  3. Contrast or failure case — contrast sharpens the aha moment.
  4. Aha — one consequence the viewer didn't know before.
  5. Close — what changes now.

Scene pacing: fade in at frame 0, fade out at 12 frames before cut, crossfade 12 frames into next scene.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.