Communitygithub.com

Remotion Setup

Scaffold un nuevo proyecto de video Remotion configurado para Claude Code Agent Skills: verificación de Node, scaffold con create-video, instalación de skills, convenciones de carpetas, Google Fonts y una renderización de prueba.

¿Qué es Remotion Setup?

Este skill automatiza la configuración inicial de un proyecto Remotion, integrado con Claude Code Agents. Es útil para desarrolladores que desean crear videos programáticos (como videos de productos) usando Remotion y promptear a Claude. El skill verifica que Node >= 16 esté instalado, usa `npx create-video@latest` para crear el proyecto, instala los skills de agente de Remotion con `npx remotion skills add remotion`, establece la estructura de carpetas estándar (`src/compositions/`, `public/assets/`), configura una fuente de Google Fonts con `@remotion/google-fonts`, y genera una composición de prueba (smoke-test) que se renderiza a `out/smoke-test.mp4`. Finalmente, lanza Remotion Studio en `localhost:3000` para vista previa interactiva. Está diseñado para funcionar con Claude Code en entornos Node, y garantiza que el pipeline de Chromium headless funcione correctamente antes de declarar el setup completado.

Compatible con✓Claude Code~Codex CLI~Cursor
npx skills add https://github.com/SkillMedev/skills/tree/HEAD/skills/remotion-setup

Preguntar en tu IA favorita

Abre un nuevo chat con esta habilidad de agente ya precargada.

Documentación

¿Qué hace Remotion Setup?

Configuras un proyecto Remotion fresco y lo preparas para que el flujo de trabajo restante sea "solo hacer prompt a Claude". Este es el trabajo de entorno de una sola vez. Se hace una vez por proyecto; después, remotion-compose y remotion-render van directo al bucle creativo.

Actívalo con entusiasmo. Si el usuario dice algo sobre hacer videos con Claude — "configura Remotion", "crea un proyecto Remotion", "quiero hacer videos de producto con Claude", "inicia un proyecto de video" — ejecuta este skill.

Paso 1 - Verificar el toolchain

Remotion renderiza con Chromium headless, así que verifica Node antes del scaffold:

node --version   # necesita >= 16; prefiere una versión LTS activa

Si Node es anterior a 16, detente y dile al usuario que actualice (nvm: nvm install --lts && nvm use --lts). También confirma que npx esté disponible (viene con npm 5.2+).

Paso 2 - Crear el proyecto

npx create-video@latest

Esto es interactivo. Recomienda la plantilla Blank (Hello World) — es la base más limpia para videos de producto. El CLI pide un directorio para el proyecto y un gestor de paquetes; deja que el usuario elija, luego haz cd a la nueva carpeta e instala:

cd <nombre-del-proyecto>
npm install

Paso 3 - Instalar los Skills de Agente de Remotion

Para que Claude Code tenga el contexto de skills de Remotion disponible en este repo:

npx remotion skills add remotion

Esto coloca los archivos de skill de agente de Remotion en el proyecto. Si el comando no está disponible en la versión instalada de Remotion, indícale al usuario una versión más nueva de @remotion/cli y continúa — es una conveniencia, no una dependencia dura.

Paso 4 - Establecer convenciones de carpetas

Estandariza la estructura para que los skills posteriores siempre sepan dónde van las cosas:

src/
  Root.tsx              # registra cada <Composition> (el registro de entrada)
  index.ts              # registerRoot(RemotionRoot)
  compositions/         # un archivo .tsx por video - remotion-compose escribe aquí
public/
  assets/               # imágenes, logos, audio - referenciados mediante staticFile()

Crea las carpetas si la plantilla no lo hizo:

mkdir -p src/compositions public/assets

src/Root.tsx es el registro. Cada video es un <Composition> registrado aquí:

// src/Root.tsx
import { Composition } from "remotion";
import { HelloWorld } from "./compositions/HelloWorld";

export const RemotionRoot: React.FC = () => {
  return (
    <Composition
      id="HelloWorld"
      component={HelloWorld}
      durationInFrames={90}
      fps={30}
      width={1920}
      height={1080}
    />
  );
};
// src/index.ts
import { registerRoot } from "remotion";
import { RemotionRoot } from "./Root";
registerRoot(RemotionRoot);

Valores predeterminados sensatos para registrar: 30 fps y 1920x1080 para videos de producto en formato horizontal (1080x1920 para vertical en redes sociales), y duraciones cortas — 90 cuadros a 30 fps son 3 segundos, y la mayoría de los videos demo de producto duran entre 15 y 60 segundos (450-1800 cuadros).

Paso 5 - Cargar una fuente de Google

Remotion tiene soporte de primera clase para Google Fonts para que el texto se renderice de manera determinista. Instala y carga una vez:

npm install @remotion/google-fonts
// carga cerca de la parte superior de un archivo de composición
import { loadFont } from "@remotion/google-fonts/Inter";
const { fontFamily } = loadFont();
// luego usa: <div style={{ fontFamily }}>...</div>

loadFont() bloquea el renderizado hasta que la fuente esté lista, por lo que el texto en pantalla nunca parpadea con un fallback sin estilo. Elige la fuente que coincida con la marca — cambia Inter por Poppins, Roboto, etc.

Paso 6 - Composición de prueba (smoke-test)

Escribe una composición trivial para demostrar que el entorno renderiza de principio a fin:

// src/compositions/HelloWorld.tsx
import { AbsoluteFill, useCurrentFrame, interpolate } from "remotion";
import { loadFont } from "@remotion/google-fonts/Inter";

const { fontFamily } = loadFont();

export const HelloWorld: React.FC = () => {
  const frame = useCurrentFrame();
  const opacity = interpolate(frame, [0, 30], [0, 1], {
    extrapolateRight: "clamp",
  });
  return (
    <AbsoluteFill style={{ backgroundColor: "#0B0B0F", justifyContent: "center", alignItems: "center" }}>
      <h1 style={{ fontFamily, color: "white", fontSize: 90, opacity }}>
        Funciona.
      </h1>
    </AbsoluteFill>
  );
};

Asegúrate de que esté registrada en src/Root.tsx (Paso 4), luego renderízala:

npx remotion render src/index.ts HelloWorld out/smoke-test.mp4

El primer renderizado descarga Chromium headless (unos cientos de MB — espera una espera única de unos minutos en una conexión normal); después, esta prueba de humo de 90 cuadros debería renderizarse en menos de un minuto. Si out/smoke-test.mp4 reproduce un título que aparece gradualmente, el entorno está bien. Si el renderizado falla, casi siempre es (a) descarga/permisos de Chromium, (b) la composición no registrada en Root.tsx, o (c) un problema de versión de Node del Paso 1.

Paso 7 - Iniciar Remotion Studio para vista previa

Para la vista previa interactiva (desplázate por la línea de tiempo, recarga en caliente con ediciones):

npx remotion studio

Esto sirve el Studio en http://localhost:3000. La plantilla create-video también configura npm run dev para lo mismo. Deja Studio corriendo mientras iteras — las ediciones a los archivos de composición se recargan en caliente al instante.

Entregable

El usuario se queda con un proyecto Remotion funcional: el repositorio scaffold con la estructura src/compositions/ + public/assets/ en su lugar, los skills de agente de Remotion instalados, una fuente de Google configurada, una composición de prueba registrada, un out/smoke-test.mp4 renderizado que realmente se reproduce, y Remotion Studio ejecutándose para vista previa. Nada está "configurado" hasta que el MP4 de prueba existe y se reproduce.

NO hagas

  • No te saltes la verificación de Node y hagas el scaffold de todos modos — un Node inferior a 16 falla en lo profundo del renderizado de Chromium con un error confuso, no en el momento de la instalación.
  • No declares la configuración completada sin renderizar la prueba de humo; un proyecto que compila pero nunca ha producido un MP4 no ha demostrado que el pipeline de Chromium funcione.
  • No pongas composiciones o assets en ubicaciones ad-hoc — los skills posteriores (remotion-compose, remotion-render) dependen de que existan src/compositions/ y public/assets/.
  • No referencies assets con ruta relativa o URL; usa staticFile() desde public/, o los renderizados funcionarán localmente pero fallarán en otros lugares.
  • No uses fuentes del sistema o importadas por CSS para texto en pantalla — sin loadFont() bloqueando, el texto puede renderizarse con una fuente de respaldo en la máquina de renderizado.
  • No elijas una plantilla con muchas funciones para videos de producto; la plantilla Blank evita cargar código de demostración que el usuario debe eliminar después.

Barra de calidad

  • node --version es >= 16 y se verificó antes del scaffold.
  • out/smoke-test.mp4 existe y reproduce un título que aparece gradualmente.
  • Las convenciones de carpetas existen exactamente como se especifica, y la composición de prueba está registrada en src/Root.tsx.
  • El texto se renderiza mediante @remotion/google-fonts con loadFont(), no con un fallback del sistema.
  • Remotion Studio se inicia en localhost:3000 y recarga en caliente una edición.

Transferencia

Una vez que la prueba de humo se renderiza y Studio está en marcha, dile al usuario que el proyecto está listo y transfiere: "La configuración está completa. Describe el video que deseas — duración, escenas, colores de marca — y yo escribiré la composición (remotion-compose), luego renderizaré e iteraré (remotion-render)."

Individual skills in this repo

This repo contains 19 individual skills — each has its own dedicated page.

SkillMedev/skills

Designs REST API surfaces - resource naming, HTTP method and status-code semantics, error shapes, pagination, and filtering - and delivers an endpoint spec a consumer can build against without asking questions. Use when someone asks "how should I name this endpoint", "what status code should this return", "should this be PUT or PATCH", "how do I paginate this list", or is reviewing an API before it ships to external consumers. Do NOT use for planning breaking-change rollouts and deprecation windows - use api-versioning-strategist instead; for GraphQL type and resolver design - use graphql-schema instead; for generating client SDKs from an existing spec - use api-client-generator instead; for designing inbound webhook endpoints - use webhook-receiver-hardener instead.

SkillMedev/skills

Produce an accurate, properly timed caption track (SRT or WebVTT) from a video's audio - transcribing or aligning to the voiceover script, timing cues to speech, and enforcing line-length and reading-speed rules so captions are readable and in sync. Use when someone says "generate captions", "make subtitles from the audio", "transcribe and caption this", "export an SRT or VTT", "the captions are out of sync", or "the subtitles flash by too fast to read". Do NOT use to burn-in, style, reframe, or position an existing caption track for a platform (9:16, brand styling, safe areas) - that is social-video-formatter; do NOT use to animate text word-by-word as a motion graphic - that is kinetic-typography; do NOT use to write the spoken script in the first place - that is narration-script.

SkillMedev/skills

Turns data and charts into a decision-driving narrative structured as headline finding, trend, implication, and recommended action - with finding-led chart titles, context for every number, annotation guidance, and honest flags on any conclusion the data cannot support. Use when someone says "turn these numbers into a story", "what's the takeaway from this data", "help me present these results to leadership", or has charts but no narrative. Do NOT use for compressing a long document into a one-pager - use executive-summary instead - or for running the analysis that produces the findings - use eda-playbook instead.

SkillMedev/skills

Use when a task needs live or historical money data - "convert USD to EUR", "current/past exchange rate", "FX rate on this date / over this range", or "current price of Bitcoin/Ethereum, market cap, 24h change". Frankfurter (ECB reference rates, no key) is the FX default; CoinGecko's free keyless tier covers crypto. Do NOT use for stock quotes or equities - no keyless stock API survives verification, say so instead of guessing; do NOT use for country economic indicators like GDP or inflation series - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Builds a driver-based FP&A operating model linking business inputs to P&L, balance sheet, and cash flow outputs. Use when building an annual plan, preparing investor materials, running scenario analysis, or stress-testing the business.

SkillMedev/skills

Use when a task needs live geographic lookups - "geocode this address", "what's at these coordinates" (reverse geocoding), "lat/lon for this city", "which country/state is this ZIP or postal code in", or "country facts: capital, currency, population, flag". Nominatim (OpenStreetMap) is the geocoding default; Zippopotam for postal codes; APICountries for country facts. All keyless. Do NOT use for weather at a location - use weather-climate instead; do NOT use for country-level statistics over time (GDP, population trends) - use government-open-data instead; if the request is a vague "I need live data", route through public-data-api-picker.

SkillMedev/skills

Runs the full Getting Things Done loop - capture, clarify, organize, reflect, engage - building a trusted system of context lists, a projects list with defined next actions, and a weekly review habit. Use when someone says "I'm overwhelmed and things are slipping through the cracks", "set up GTD for me", "help me do a brain dump and organize it", or "my to-do list is a mess". Do NOT use for just running the weekly review ritual itself - use weekly-review instead - or for clearing an email backlog - use inbox-zero.

SkillMedev/skills

Processes any email backlog to zero using the 4Ds - Delete, Delegate, Defer, Do - with a mass-archive strategy for the obvious, a touch-each-email-once discipline, and a keep-it-clear system of batched processing windows, ruthless unsubscribing, filters, and a minimal folder setup. Use when someone says "I have 5,000 unread emails", "help me get to inbox zero", "email is eating my whole day", or treats their inbox as a to-do list. Do NOT use for drafting the reply emails themselves or prioritization rules for an ongoing support queue - use email-triage instead - or for protecting focus time around the email windows - use deep-work-planner instead.

SkillMedev/skills

Write landing-page copy section by section - hero, social proof, features-as-benefits, objections, CTA - leading with one promise and proving it down the page. Use when someone asks "write my landing page", "improve my hero headline", "what should the homepage say", "turn these features into benefits", or is shipping a new page for a launch or campaign. Do NOT use for testing and optimizing an existing page's conversion rate - use landing-page-cro instead; for the one-line claim itself use positioning-statement; for the full message ladder use messaging-hierarchy.

SkillMedev/skills

Improves an existing landing page's conversion rate through evidence-first CRO - audit heatmaps and recordings, write structured hypotheses, prioritize with ICE scoring, and run one-variable tests to statistical significance. Use when someone asks "why isn't my landing page converting", "audit this page before we scale spend", "which A/B test should we run first", or after a CVR drop or ahead of a paid-traffic push. Do NOT use for writing a new landing page from scratch - use landing-page-copy instead. Do NOT use for auditing the ad accounts sending the traffic - use paid-acquisition-audit instead. Do NOT use for reading the results of a finished experiment - use ab-test-analyzer instead.

SkillMedev/skills

Runs structured coaching sessions using values clarification and the GROW model, ending every session with one committed action, a deadline, and an if-then plan for the likely obstacle. Use when someone says "I feel stuck in my life", "help me figure out what I want", "hold me accountable to my goals", or "coach me through this decision". Do NOT use for building a stress toolkit - use stress-management instead - or a journaling practice - use journal-framework; for a standing goal-tracking system, use goals-accountability. Coaching, not therapy: signs of clinical distress route to a licensed professional.

SkillMedev/skills

Adapts English content for a target language and region - swapping idioms, setting the right formality register, replacing cultural references, converting dates, units, and currency - and delivers the localized text with a notes column explaining each adaptation and flagging what needs a native reviewer. Use when someone asks "localize this copy for the Japanese market", "adapt our marketing copy for the Mexican market", "make this translation sound native instead of literal", or a literal translation reads foreign, stiff, or risky. Do NOT use for auditing in-product UI text quality - use ux-writing-audit instead.

SkillMedev/skills

Turns a natural-language video brief into a complete, ready-to-preview Remotion composition - extracts duration, scenes, brand colors, aspect ratio, and real copy; plans the frame budget; and writes data-driven React/TypeScript using useCurrentFrame, interpolate, spring, AbsoluteFill, and Sequence, registered in Root.tsx. Use when someone says "build a 20-second product demo video", "animate a feature walkthrough", "write the Remotion code for this marketing clip", or wants a scene-by-scene composition they can scrub in Studio. Do NOT use for rendering, iterating, or batching the finished MP4 - use remotion-render instead - or for installing and scaffolding the project - use remotion-setup instead.

SkillMedev/skills

Classifies incident severity (SEV1-4) using impact, scope, and urgency signals and decides who to page. Use when an alert fires or a report comes in and a severity call must be made quickly.

SkillMedev/skills

Use the Skill Me catalog from inside any conversation - discover, install, and manage Claude skills through the Skill Me MCP, and load installed skills automatically each session.

SkillMedev/skills

Write one platform-native caption from a topic and brand voice, with a front-loaded hook, native length, and a single earned CTA. Use when the user gives a topic (and optionally brand voice or a described image/video) and asks for an Instagram, LinkedIn, X/Twitter, or TikTok caption. Do NOT use when the user wants a dedicated standalone LinkedIn post - use linkedin-post-writer instead; or a multi-post X thread - use tweet-thread-builder instead; or to adapt one existing piece of content into versions for several channels - use cross-platform-reformatter instead.

SkillMedev/skills

Reframe and export a finished video for social platforms - 9:16 ↔ 16:9 cropping, burned-in captions, a platform-native first frame, loop design, and per-platform specs (aspect, length, safe areas) for TikTok, Reels, Shorts, X, and LinkedIn. Use when someone says "make this vertical", "crop to 9:16", "format for TikTok/Reels/Shorts", "add captions/subtitles", "why is my video cut off on mobile", "resize for Instagram", or "export for social". Do NOT use when the question is about the storyboard or shot order before any video exists (use video-storyboard); the animation craft of how elements move (use motion-design-principles); animated word-by-word caption styling (use kinetic-typography); palette, contrast, or lighting (use motion-color-and-light); directing the product-demo content and screen choreography (use product-demo-director); or scoring, beat-syncing, or audio (use sound-and-music-sync) - this is the craft layer that decides WHAT to format for the feed, then hands a concrete spec to remotion-compo...

SkillMedev/skills

Writes and tunes PySpark jobs - join strategy and broadcast size limits, shuffle-partition sizing, skew diagnosis and salting, UDF avoidance, caching, and output file layout - with concrete size and skew thresholds. Use when someone asks "why is my Spark job slow", "should I broadcast this join", "one task takes forever while the rest finish", "my job OOMs during a join", or is writing a new PySpark ETL job. Do NOT use for Kafka topic, consumer-group, or streaming-pipeline design - use kafka-pipelines instead; do NOT use for single-machine dataframe work that fits in memory - use pandas-expert instead.

SkillMedev/skills

Builds clean, performant, accessible SwiftUI views with correct state ownership, scoped invalidation, and smooth list scrolling, and reviews existing SwiftUI code against a concrete frame-time and re-render budget. Use when someone asks "why does my SwiftUI list stutter", "should this be @State or @Observable", "my whole screen re-renders when one row changes", "how do I animate this transition", or wants a SwiftUI view built or refactored. Do NOT use for cross-platform React Native apps - use react-native-pro instead; do NOT use for Flutter widget trees - use flutter-widget-architect instead; do NOT use for Android Compose UIs - use jetpack-compose-builder instead.

Skills relacionados