MV pipeline

Every music video on this site was made the same way: I direct, Claude Code builds. Behind it is a handbook I keep in my production folder — the rules, a step-by-step workflow, the engines to copy and everything that went wrong — with skills and a reviewer agent, so every new session starts from what the last ones learned.

Eleven steps, each leaving a file in the project: the direction, references, an asset plan, sourcing, the animatic, the tracks, the type, effects and masks, the camera, the grade, then the mix, QA and the master. Open creative choices are settled in numbered rounds of questions, each with a recommendation; a sample at the final standard comes before the whole; assets are found before they are generated, with every licence logged.

• kinetic-type — titles and lyrics that perform: strokes assembling, words moving to the beat, checked for reading time
• still-motion — a still illustration that breathes, blinks and sways its hair
• layered-puppet-pv — a character cut into layers with bone chains in her hair, toward After Effects / Live2D quality
• pv-lyric-mv — the 恋の星 route: prepared poses, layered stages and expressive type

Before delivery a reviewer agent watches the render against its brief, and small Python tools look at the sound, the composition, the colour scopes and how long each line stays readable. When something goes wrong, the fix is written into the handbook's pitfalls, so it doesn't happen twice.

The same discipline as my day job in QA: a checklist, small steps each with its own check, and a written record of every failure.