media-forgemf-cameralisted

# media-forge:mf-camera Use one clear camera idea per short clip unless the user asks for a multi-shot sequence. The best camera direction has a start frame, movement, speed, subject relationship, and endpoint. Avoid stacking moves that fight each other, such as drone rise, dolly-in, handheld shake, and orbit in the same five-second shot. This camera grammar is provider-agnostic craft language — it applies whether the underlying call goes to Veo, Kling, Higgsfield, or Seedance. For Kling's own DoP-verb cheatsheet and Higgsfield's Cinema Studio lens dictionary, see `kling-prompting` and `higgsfield-prompting`; this skill is the shared vocabulary underneath both. Load `[ref:quick-ref]` for prompt assembly, `[ref:cinematography-shot-language]` for professional shot contracts, `[ref:directing-engine]` to derive the move from the scene's one intention so it reinforces light, performance, and sound instead of competing, and `[ref:vocab/zh]` or `[ref:vocab/ru]` when camera wording must be multilingual. ## Intent When a user asks about camera, they are really asking where the viewer's body stands and what the viewer is made to feel from there. Camera grammar is empathy mechanics: a push-in is leaning closer, a locked frame is holding your breath. Choose the move that puts the audience where the user's feeling lives. ## Camera Contract State: shot scale, angle, movement, speed, subject relationship, and endpoint. A prompt-ready camera phrase should be physically possible and tie