I used Kimi K3 on a 36-second reference-led motion project. The goal wasn't to ask for a finished video from one prompt. I wanted an editable reconstruction I could keep directing at the code and shot level.

K3 inspected the source with ffmpeg, extracted frames, identified edit points, and helped rebuild the sequence as separate code-driven clips. GSAP carried the timing and motion curves, generated textures supplied the material layer, and Three.js handled the procedural particle fields.

The first render got the broad structure in place, but it wasn't production-ready. Most of the work was in matched-frame review, clip retiming, scale and framing corrections, texture replacement, particle-density tuning, and repeated renders.

What impressed me was K3's ability to retain enough context across that loop to keep the whole sequence editable. The limitation was visual judgment: I still had to define hierarchy, material response, and the stopping criteria for each shot.

For people using K3 on larger vibe-coded projects, has it been more valuable for the first build or for staying coherent through revisions?

I used Kimi K3 to rebuild a 36-second launch film as editable code — the first render was only the beginning