osidemedia/higgsfield-ai-prompt-skill/higgsfield-cinema

Higgsfield Cinema Studio 2.5

QUICK FACTS

Generated-checked block (scripts/build_index.py verifies anchors). Read the linked sections for full context — these lines are routing aids, not the rules themselves.

• Four Cinema Studio versions are on the platform (2.5 / 3.0 / 3.5 / 4.0) — user-selected, no auto-routing; always detect the version first →
• Cinema Studio 4.0 (cinematic_studio_video_4_0, CLI workflow schema 2026-09-26): the same four modes as seedance_2_5 (t2v / omni_reference / video_edit / video_extension), 480p–1080p, start/end image + image/video/audio refs; the 3.5 enum pills are GONE — camera / lens / aperture / era / genre / pacing are free *_id strings with no published values, so never invent one →
• 4.0 vs 3.5 at the API: no multi_shots / multi_prompt, no genre enum, no enhance_prompt; prompt now REQUIRED; audio defaults ON; duration default 5s (range unpublished) →
• Hard 512-character prompt cap; 2.5 @ Element chips eat ~80–100 hidden chars each →
• Elements System: define @Characters/@Locations/@Props once, call everywhere →
• 3.5 main UI = three pills (Genre / Style / Camera), each Auto by default — override only with a creative reason →
• 7 confirmed 3.5 genres: General · Action · Horror · Comedy · Noir · Drama · Epic — never invent genre names →
• Style presets: 8 Color Palettes · 6 Lighting · 9 Camera Moveset Styles, or free-form Manual Style →
• Camera axes: 3 bodies · 5 lenses · focal 8/14/35/50/75mm · aperture f/1.4–f/4–f/11; two camera vocabularies coexist — vocabulary follows the selected model →
• Output enums: 7 aspect ratios incl. 21:9 · 480p/720p/1080p · duration 4–15s · Sound On/Off →
• Lead every delivered shot with the one-line settings strip (UI presets ≠ prompt text; never restate strip values in the body) →
• The UI shot counter caps internal cuts — "strictly N shots" must keep N within it (observed cap 4; API exposes no max — UI behavior, verify live) →
• Manual Style = saved ≤2,000-char block of project LAWS (grade, lighting law, texture, performance register); it replaces the preset axes →
• 480p drafts validate the prompt, NOT the take — no seed param; transfer a look via Hero Frame + start/end-frame pinning →
• Resolution matrix has two axes: shot physics × delivery context; 4K-finish pipelines master at model max res in std mode →
• Seedance fast mode cannot output 1080p — drafting in fast then "switching up" silently changes mode AND res →
• Big reference blocks live beside this file: 2.5 + 3.0 per-mode output templates in references/output-formats-2-5-3-0.md; Motion / Outfit / Palette / Product sheet specs in references/reference-sheet-types.md →

Cinema Studio is Higgsfield's professional filmmaking environment — a full production workflow for multi-shot, character-consistent cinematic content. It's fundamentally different from single-clip generation: you're building sequences, not individual videos.

Cinema Studio vs Standard Generation

Cinema Studio 4.0 has no column here on purpose. Its API parameter surface is

verified (§ Cinema Studio 4.0); its UI, plan gating, duration range and output quality

are not — a column of "unverified" cells would read as data. Use the 4.0 section.

Use Cinema Studio when:

• You need 2+ shots that must feel like the same film
• Character geometry must be locked across cuts
• You want professional optical physics (lens flare, depth of field, sensor grain) — 2.5 only
• You're building a short film, branded content, or any sequence longer than one clip

Stick with standard generation when:

• Single clip is sufficient
• Speed matters more than consistency
• Exploring ideas before committing to a full sequence

⚠ Version Detection — Ask First

Before generating any Cinema Studio output, always ask the user:

Which Cinema Studio are you in — 2.5, 3.0, 3.5, or 4.0?

If the user has already stated their version (e.g., "I'm using 3.0" or "Cinema Studio 3.0"), remember it and don't ask again. But never assume — the versions have fundamentally different feature sets.

Why this matters:

• 2.5 has optical physics (camera body + lens stack), color grading, 3D Mode, grid generation
• 3.0 has none of those — outputting them wastes the user's time and causes confusion
• 3.0 has features 2.5 doesn't: native audio, Smart shot control, 21:9 ultrawide, 15s duration
• 3.5 brings back a camera panel with its own vocabulary, plus named Style presets (§ Cinema Studio 3.5)
• 4.0 replaces the 3.5 preset enums with opaque *_id values and adds editing + extension modes (§ Cinema Studio 4.0) — a 3.5 settings strip is not a 4.0 settings strip
• Speed Ramp options differ between versions
• Genre lists differ between versions

Once the version is known, use ONLY that version's output format and feature set. Never mix features from one version into output for the other.

The 10-Step Cinema Studio 2.5 Workflow

Cinema Studio 2.5 extends the pipeline in both directions: pre-production (Soul Cast + location prompt) before generation, and post-production (color grading) after.

 1. SCRIPT        → Write or paste your scene description / shot list
 2. SOUL CAST     → (New in 2.5) Generate AI actors from parameters or use saved Elements
 3. REFERENCE     → Upload character photo → create Reference Anchor (or use Soul Cast actor)
 4. ELEMENTS      → (Optional) Define @Characters, @Locations, @Props if needed
 5. OPTICAL STACK → Select camera body + lens + focal length + aperture (image mode)
 6. HERO FRAME    → Generate a key image that defines the visual tone
 7. COLOR GRADE   → (New in 2.5) Apply color grading to keyframes before video generation
 8. CAMERA CONFIG → Set Director Panel movement + Speed Ramp + Duration in UI
 9. SHOT MODE     → Choose Single Shot / Multi-Shot Auto / Multi-Shot Manual
10. GENERATE → EXPORT → Chain into timeline or export to editing

Elements System — Define Once, Call Everywhere

Elements are Cinema Studio's reusable asset library. Create a Character, Location, or Prop once and reference it with @ in any subsequent prompt.

Three element types:

Creation workflow:

1. Open Elements panel → New Element → choose type
2. Upload reference image(s)
3. Name the element (this becomes the @ tag)
4. Add description (appearance details, key features)
5. Save → now available across all shots in this project

Per-Character Emotion: In Multi-Shot mode, each character can have an emotion setting per scene. The available emotions are:

Set emotion per character per scene in the UI — this keeps expression changes out of the prompt field and lets the model handle the subtlety of facial animation.

@ tag rule — use exactly what the user provides, nothing more Only use @ tags for Elements the user has explicitly given you in this conversation. If they give you @Marcus but no location or prop tags, write the location and props as plain description. Never invent or assume @ tags for anything the user hasn't named. Each @ tag the user gives you = they have that Element set up. Silence = they don't.

No Elements provided — write everything as description:

A woman with dark hair and a red coat walks through a narrow downtown alley at night.
She carries a worn leather briefcase. She stops under a streetlight, turns to camera.

User provides @Sarah only — use it, describe the rest:

@Sarah walks through a narrow downtown alley at night.
She carries a worn leather briefcase. She stops under a streetlight, turns to camera.

User provides @Sarah, @DowntownAlley, @LeatherBriefcase — use all three:

@Sarah walks through @DowntownAlley, carrying @LeatherBriefcase.
She stops under a streetlight, turns to camera.