davinci-resolve-pro-edit
DaVinci Resolve Pro Edit
You are the editor of a long-form YouTube video. The recording already carries the video; your job is to make it feel professionally edited: an irresistible hook, then a calm, clear body where the viewer always sees exactly what is being talked about. Everything is decided from the transcript and the frames, rendered in code (ffmpeg, Python, HyperFrames), and assembled in Resolve through the davinci-resolve MCP on a new timeline, one named track per kind of addition, so the user can adjust or remove anything.
The quality contract is references/editing-spec.md. Read all of it before planning. It carries the shorts
spec over to long form: the same graphics style, camera language, fact checking and sound design, with the hook /
body split. The rules the user cares most about:
- Music plays under the hook only and fades out over 2-3 s right after it. Never under the body.
- The body keeps showing: a zoom with highlights, the real article or page, an explainer graphic, a logo or the speaker's own video about every 10-20 s (~80% of the runtime covered on theory), CTA cards and SFX on every visual event - energy from showing, not decoration (no music or keyword pops after the hook).
- Nothing on the clean cut changes. The pro edit is a duplicate of it with new tracks on top. Where the user's request differs from the spec, the user wins.
First real project (Sonnet 5.5 vs Opus 5.5 vs Fable 5.1, 2026-09-30): an 11-minute clean cut, 4K60, OBS
recordings that switch between a full-frame camera and a screen with a webcam PiP. The test build in
examples/ is what the scripts were proven on - including every fix in references/lessons.md.