/kling-3-0-deep-dive

name: kling-3-0-deep-dive
description: >
  Deep operating guidance for Kling 3.0 video generation. Use when selecting Kling 3.0
  for a shot, designing multi-shot scene structure, writing Kling-native cinematic
  prompts, planning Elements or Motion Control references, using start/end frame
  anchors, handling native audio or dialogue, building product/commercial shots,
  choosing duration/aspect/quality settings, troubleshooting artifacts, or comparing
  Kling 3.0 against Seedance 2.0, Veo, Sora, DoP/Cinema, or other Higgsfield video
  routes. Complements shot-specifier and video-generator by turning Kling 3.0's
  scene-based model behaviour into practical production rules.

Kling 3.0 Deep Dive

Use this skill when `shot-specifier` routes a shot to `kling3_0` or when `video-generator` is about to submit Kling 3.0 jobs through the Higgsfield Model Context Protocol (MCP).

Kling 3.0 is best treated as a **scene-directed cinematic video model**. It responds well to shot labels, camera behaviour, physical motion, clear timing, and simple subject/environment constraints. Think like a director and camera operator: what is the shot, what moves, how does the camera react, what does the audience hear, and where does the shot end?

Live-Schema Rule

Before any production generation, inspect the live Higgsfield MCP schema through `video-generator`. Public guides disagree on exact model IDs, quality modes, text capabilities, Elements support, Motion Control support, native audio options, duration ranges, and media roles.

Use the limits below as planning defaults only. If the live MCP schema is narrower, follow the live schema. If the selected Kling route cannot accept the required anchors, Elements, motion references, or audio parameters, stop and ask for a production decision.

S01 session 2 observed a narrower Higgsfield MCP surface than public Kling guides describe: Kling accepted `start_image` and `end_image`, did not expose a generic reference-image role, did not expose `sound`, did not expose `cfg_scale`, and downloaded 16:9 outputs at `1344x768`. Treat Elements, Motion Control, CFG, sound toggles, and labelled resolution choices as schema-gated features, not assumptions.

When Kling 3.0 Is The Right Route

Prefer Kling 3.0 when the shot needs:

• explicit scene structure or 2-6 shot coverage in a single generation;
• clean cinematic camera movement: pans, tracks, dollies, orbits, reveals, drone moves;
• physically grounded movement, environmental interaction, impact, or macro texture;
• landscape establishing shots, machine/drone POV, exteriors, product hero moves, or

camera-motion-led b-roll;

• start/end frame control or transition shaping;
• Elements or Motion Control when the live tool exposes them;
• native ambient audio, sound effects, or structured dialogue when the scene can be

labelled unambiguously.

Do not default to Kling 3.0 when the shot's main problem is heavy reference-driven identity preservation across many generated clips. Seedance 2.0 remains the safer default when reference images must carry character, prop, or recurring visual element identity. Also avoid asking Kling to invent exact UI, logos, legal copy, or critical text. Bake text into a frame or add it in post.

Planning Defaults

| Decision | Default | Reason | |----------|---------|--------| | Single-shot duration | 3-5 s for best quality; 6-8 s for simple one-vector moves | Shorter clips reduce drift and slot cleanly into edits | | Multi-shot duration | 2-6 scenes, each with explicit duration; total up to live MCP limit | Kling responds strongly to labelled scene structure | | Upper limit | 15 s only when each beat is timed and physically simple | Long clips need progression, not one overloaded paragraph | | Aspect ratio | Choose before prompting | Aspect ratio changes composition pressure and camera path | | 16:9 | Cinematic exteriors, landscapes, horizontal movement, narrative coverage | Gives room for camera logic and environment | | 9:16 | One subject, product hero, or hook; reserve negative space for overlays | Tall frames punish busy backgrounds | | 1:1 or 4:5 | Product/feed variants when supported | Keeps products readable and avoids wasted side detail | | Resolution | Request the manifest's resolution hint when exposed; verify actual pixels after download | S01 current MCP evidence emitted `1344x768` even for 16:9 production shots | | Quality | Draft in faster tiers; final in high quality after motion and framing are right | High quality is not a fix for bad direction |

Prompt Structure

Kling prompts should read like production direction, not keyword lists.

Use this default order for a single shot:

Camera + Subject and action physics + Environment + Lighting + Texture + Audio/style

Use this default order for structured narrative or dialogue:

Scene + Characters + Action timeline + Camera + Audio and style

For product/commercial shots, use:

Environment + Lighting + Camera movement + Product behaviour + Composition constraints

Write one to three rich sentences per shot. Specificity matters more than length. If the prompt becomes a list of competing details, split the shot.

Multi-Shot Structure

Kling 3.0 should receive labelled shots when the scene has more than one beat or camera angle. Do not compress a storyboard into one paragraph.

Total: 12 s / 3 shots / 16:9.
Shot 1 (0-4 s): Wide establishing shot...
Shot 2 (4-8 s): Medium tracking shot...
Shot 3 (8-12 s): Close-up reaction...
Audio: ...
Style: ...

Each shot needs:

• framing;
• subject and action;
• camera behaviour;
• duration;
• transition or continuity note;
• audio/dialogue if applicable.

Use multi-shot mode when narrative order and coverage matter more than perfect single identity preservation. For identity-critical characters, combine multi-shot structure with Elements or clean reference images when the live MCP route supports them.

Camera And Motion La