/higgsfield-workspaces

name: higgsfield-workspaces
description: "Use when the user is unsure which Higgsfield workspace fits their task, needs to decide between Cinema Studio / Lipsync Studio / Draw-to-Video / Viral Hub presets / Click to Ad / Higgsfield Audio (Sora 2 Trends is built on the retired Sora 2), or is asking 'what should I use for X'. This sub-skill routes by production problem BEFORE model selection."
user-invocable: true
metadata:
  tags: [higgsfield, workspaces, routing, decision, cinema-studio, lipsync, draw-to-video, viral-hub, sora-trends, click-to-ad, higgsfield-audio]
  version: 1.3.0
  updated: 2026-09-26
  parent: higgsfield

Higgsfield Workspaces — Task-First Decision Layer

<!-- CONTENTS — generated by scripts/build_index.py; do not hand-edit --> **Contents**

• [Introduction](#introduction)
• [The Decision Matrix](#the-decision-matrix)
• [Workspace Descriptions](#workspace-descriptions)
• [Cinema Studio](#cinema-studio)
• [Lipsync Studio](#lipsync-studio)
• [Draw to Video / Sketch to Video](#draw-to-video--sketch-to-video)
• [Viral Hub presets](#viral-hub-presets)
• [Sora 2 Trends](#sora-2-trends)
• [Click to Ad](#click-to-ad)
• [Higgsfield Audio](#higgsfield-audio)
• [Higgsfield Collab](#higgsfield-collab)
• [The Six-Step Project Logic](#the-six-step-project-logic)
• [Relationship to MCSLA](#relationship-to-mcsla)
• [Related skills](#related-skills)

<!-- /CONTENTS -->

Introduction

Higgsfield is organized around workspaces, each one tuned for a specific kind of production work. The right starting question is not "which model should I use?" but "what am I actually trying to make?" Inside a workspace, model choice still matters — it shapes quality, speed, and cost — but a workspace mismatch costs more time than a suboptimal model. Pick the workspace by the task, then pick the model by the result you want.

---

The Decision Matrix

| Your production problem | Start with workspace | |-------------------------|----------------------| | Cinematic scene with deliberate camera direction | Cinema Studio | | Speaking character, dubbing, or avatar video | Lipsync Studio | | Rough idea, sketch, or storyboard test | Draw to Video / Sketch to Video | | Fast short-form or viral-style content | Viral Hub presets (Sora 2 Trends is built on the retired Sora 2 — see its section) | | Product ad or ecommerce variation | Click to Ad | | Narration, voice swap, or translation | Higgsfield Audio |

If the user's task matches more than one row, pick the workspace whose output most closely resembles the final deliverable — you can always chain into another workspace for polish or audio later.

---

Workspace Descriptions

Cinema Studio

The professional filmmaking environment on Higgsfield. Built for multi-shot, character-consistent sequences where camera direction, genre framing, and visual cohesion matter. Cinema Studio 2.5 offers optical physics (camera body + lens stack) and built-in color grading; Cinema Studio 3.0 (Business/Team plan) adds native audio, Smart camera planning, and longer durations. Choose this workspace when the work needs to feel like a film. For prompt construction, Director Panel use, optical stack selection, and multi-shot planning, see `higgsfield-cinema`.

Lipsync Studio

The workspace for putting words into a character's mouth. It pairs an image, video, or generated face with an audio track and synchronizes the lip movement to the speech. Use it for dubbed performances, talking-head avatars, character dialogue, and lipsync work layered on top of existing video generations. For audio layer design (dialogue, SFX, ambient, BGM) that feeds into Lipsync Studio, see `higgsfield-audio`. For character reference management and Soul Cast avatar generation that commonly sits upstream, see `higgsfield-soul`.

Draw to Video / Sketch to Video

The workspace for taking a rough sketch, blocking diagram, or storyboard panel and turning it into a generated video. It exists to bridge the gap between paper-stage ideation and motion testing — the place to validate a shot idea before it earns the credits and time of a full Cinema Studio build.

**When to use:**

• Early ideation, when you're still deciding what the shot wants to be.
• Shot blocking experiments — testing how a composition reads in motion.
• Pre-production validation before committing to Cinema Studio scene work.
• Fast iteration on framing, staging, and silhouette before the prompt or

reference set is locked.

**Input characteristics:** the workspace is forgiving. Hand-drawn storyboards, blocking diagrams with stick figures or geometric placeholders, even a crude napkin sketch all work as input. Quality of line is not the point — clarity of compositional intent is. A messy sketch with a clear staging idea outperforms a polished sketch whose staging is muddled.

**The prompt's role:** the sketch carries composition and blocking; the prompt carries everything else. Subject details, environment, lighting, mood, and material qualities all live in the prompt. Think of the prompt as describing the realized scene the sketch was hinting at — the sketch told the engine *where* things sit and *how* they move; the prompt tells it *what* they are.

**Scope — this workspace, not a Seedance reference slot.** Here the sketch *is* the input the workspace is built to realize, and a draft that inherits its layout is the point. Attached to a Seedance generation it is a different regime: a drawing in the first-frame role becomes frame one, drawing and all, and a position diagram goes in **last** as a position reference only — one incomplete-record house run found it does not reliably move blocking (`../higgsfield-seedance/FAILURE-MODES.md` § A fight generated as separate clips comes back choppy; `../../templates/seedance/staging-reference.md`; `../shared/house-rulings.md` P2-11). Do not carry "the sketch carries blocking" from here into a Seedance prompt.

**Output expectations:** test-quality, short. The ou