carocut-builder-pipeline

To migrate Remotion assets, use the project_migrate tool to move raws into template-project/public/ and generate resourceMap.ts, constants.ts, and timing.ts automatically. This connects planning outputs directly to Remotion implementation code.

Managing colors and fonts for a Remotion asset pipeline requires editing the generated constants.ts file. The pipeline generates this file with predefined COLORS and FONTS structures, allowing agents to update style configurations directly without modifying asset migration logic.

Yes, incremental asset migration in Remotion ensures raw materials are only added, never deleted. The resourceMap.ts is fully regenerated each time, while constants.ts remains unchanged unless style or color configurations explicitly shift.

Automating timing utilities for Remotion involves running an asset pipeline that generates a timing.ts file. By processing raws/images, raws/audio, and manifests, the pipeline creates timing configurations that synchronize with the migrated resources.

Yes, the Remotion asset pipeline supports agent-driven customization via manifests and memo files. Providing explicit input sources and output targets ensures raws, manifests, and the template-project integrate seamlessly for resource map generation.

Remotion assets may not update if constants.ts is not modified during incremental migration, as it only changes with style or color shifts. Ensure resourceMap.ts is regenerated to reflect newly added images and audio files from the raws directory.