Pphill teaches ai
LiveVideo · Claude Code

Rough-cut v1.0

Editing a take is maybe 80% mechanical: cutting dead air, pulling the "ums", re-timing captions to the shorter timeline. Rough-cut does that part on its own. It deliberately leaves colour, b-roll, transitions and sound design alone — that is the 20% that is actually yours. Take the build brief below and have Claude build you the basic version, or skip the build and get the finished plugin.

Build it yourselfRuns in your browser — nothing is uploaded.
Loading tool…

Under the hood

The ideas worth stealing

01

Do the mechanical 80%

The useful line to draw is not "can AI edit?" but "which parts of editing have no taste in them?" Trimming silence has no taste. Choosing the b-roll does. Automate the first, never the second.

02

The orchestrator is the product

The Python is unremarkable — a few hundred lines of ffmpeg wrangling any competent developer would write the same way. A bug in a script gives you a slightly wrong cut; a bug in the file that decides which script runs when gives you a tool that cuts the wrong things confidently. Spend your review time there.

03

Keep a human in the judgment calls

It stops before anything subjective — which lines to cut, which opening is the strongest hook — and asks. A pipeline that asks is worth more than one that guesses confidently.

Try another one