Skills: Clarify supported interactivity input ranges

[JonnyBurger]

Summary

• clarify which useVideoConfig() expressions are supported in interactivity input ranges
• fix the example to destructure durationInFrames
• keep the documentation and public Remotion skill aligned

Validation

• bun run build
• bun run stylecheck
• bun test packages/studio-server/src/test/update-keyframes.test.ts

Closes #9724

Preview

• Interactivity best practices

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
bugs	Ready	Preview, Comment	Jul 27, 2026 2:42pm
remotion	Ready	Preview, Comment	Jul 27, 2026 2:42pm

[pullfrog]

Reviewed changes — clarifies which interpolate() ranges support useVideoConfig() expressions and adds durationInFrames to the inline example.

• Clarify supported useVideoConfig() usage — the input range may use durationInFrames, fps, width, height destructured from useVideoConfig() (bare identifiers, number * fps, fps * number, durationInFrames - number); output range, easing, extrapolation, and output must be hardcoded.
• Fix code example destructuring — adds durationInFrames to the useVideoConfig() destructuring in the inline-values example, since it's now explicitly listed as a supported input-range value.
• Trailing whitespace cleanup — removes trailing spaces and extra blank lines in both files.

  ^{｜ View workflow run ｜ Using DeepSeek Pro (free via Pullfrog for OSS) (Claude Opus not used — the program covers this model; add its provider key to run your pick) ｜ 𝕏}