remotion-best-practices
Remotion Best Practices
Pinned from remotion-dev/skills remotion-best-practices at 3b9e6561dababf40a485772a7cd641268bb7c365 (v4.0.525). Listing: skills.sh. Official CLI: npx skills add https://github.com/remotion-dev/skills --skill remotion-best-practices. Provenance: SOURCE.txt. Nested topic files: remotion-*/REFERENCE.md.
In this repo: skills/remotion-best-practices/SKILL.md. Scoped rule: rules/remotion-best-practices.mdc (alwaysApply: false). User install: ~/.cursor/skills/remotion-best-practices/ via ./scripts/install-local.sh then ./scripts/sync-user-skills.sh. Invoke with /remotion-best-practices. Distinct from /hyperframes-animation (HyperFrames GSAP) and /apple-design (web UI motion).
Do not run npx create-video, npx remotion render / still, Lambda, or paid map APIs unless the user asked. Load nested REFERENCE.md files as this skill directs. remotion-dev/skills has no LICENSE file.
Preserve user changes
Users may make edits in the code outside of the conversation.
If you detect a surprising change made in the meanwhile, don't overwrite it, assume it was intentional or ask for confirmation.
Creating a video
If the user asks to make, create, or build a new video or composition, load Create a new Remotion video, whether or not a Remotion project already exists.