Higgsfield

Higgsfield AI Prompt Skill

Language rule: Reply in whatever language the user writes in.

---

HARD RULES — pre-delivery checklist

These rules apply to every Higgsfield response. They are written as a pre-delivery checklist the agent runs before sending the response, not as prohibitions stated and then forgotten. The failure mode they prevent is plausibility-over-verification — producing a response that looks correct because the agent's training data knows the rough shape of Higgsfield work, rather than because the agent actually read the skill files and verified the platform's ground truth.

Before delivering any Higgsfield response, confirm in this order:

1. Routing line present. First line of response names which sub-skills you routed to (e.g. "Routing to higgsfield-prompt + higgsfield-camera for an Atmosphere push-in"). One line, then the work. Missing routing line = response is incomplete; add it.

1. Routed sub-skills opened and read in this conversation. Match the user's ask to the routing table below, open the matching sub-skill files with the read tool, and READ them. Root SKILL.md and skills/higgsfield-prompt/SKILL.md are mandatory at minimum on any prompt request. Grepped snippets do not satisfy this rule. Full reads do. If your only access to root SKILL.md or skills/higgsfield-prompt/SKILL.md in this conversation came from grep results, you have not satisfied this rule — open the file. Platform vocabulary, preset names, and model parameters must come from the files because this platform's lineup changes between releases.

1. Named vocabulary verified, not invented. Camera preset names, motion preset names, model names, CLI flag forms, and MCP tool parameter names all come from the skill files or from verification. For model parameters, enums, and durations, verify against specs/model-specs.yaml first — it is generated from a dated models_explore snapshot (see snapshot_date inside the file); if the snapshot is stale (>30 days), verify live instead (higgsfield model get for CLI param schemas; models_explore for MCP). If you found yourself thinking "this flag probably looks like X" or "this preset is probably called Y" — stop. Read the file or run the verification command. Plausibility is not validity. Do not substitute generic video-prompt vocabulary for named Higgsfield presets; do not invent model versions, camera presets, or motion-preset names. If the user names one you don't see in the skill files, say so and ask for clarification.

1. MCSLA structure intact on video prompts. Model · Camera · Subject · Look · Action. Five layers, every video prompt, unless the user explicitly opted out.

1. Shared negative constraints appended. Pull positive-phrasing prevention phrases from skills/shared/negative-constraints.md. Do not paraphrase from training; use the exact phrasing from the file. (Kling 3.0 prefers positive phrasing over negations; using negation-form constraints when the file says positive is a fidelity miss.)

1. Preflight surfaced when applicable. If execution intent is signaled (CLI / MCP / bundled-skills mentioned) AND a video-class or high-cost model is named OR a budget concern is named, surface the two-step preflight (model get / models_explore for schema, then cost estimate). See skills/higgsfield-stack/SKILL.md § Preflight discipline.

1. Aspect ratio is an enum, not a free-form value. Check the model's allowed ratios against specs/model-specs.yaml before writing them into the header; if the snapshot is stale (>30 days), verify live via schema (models_explore / model get). Example of why this matters: Seedance 2.0 supports native 21:9, Kling 3.0 does not. Anamorphic / 2.35:1 / 2.39:1 are style register vocabulary for the Look line, not output ratios. See vocab.md § Aspect Ratio: output spec vs. style register.

1. Prompt under 200 words. Soft cap from MCSLA section. Going over is a signal you're padding rather than locking — tighten.

If any of items 1–8 are missing or unverified, the response is incomplete. Complete them before sending, not after.

---

What Is Higgsfield?

Higgsfield is a cinematic AI video and image generation platform built for filmmakers and creators. Unlike single-model tools, Higgsfield hosts multiple generation engines on one platform — Kling 3.0/3.0 Omni/3.0 Motion Control, Sora 2, Google Veo 3.1/3.1 Lite, Wan 2.7/2.6/2.5, Seedance 2.0/Pro, Minimax Hailuo 2.3/02, Higgsfield DoP (Lite/Standard/Turbo) for video; Soul 2.0, Soul Cinema Preview, Soul Cast, Nano Banana Pro/2, Kling Image 3.0/Omni, Seedream 4.0, GPT Image 2.0, Flux 2/Kontext for images — plus a library of 100+ named Motion Presets, a Soul ID character consistency system, Cinema Studio 2.5, Cinema Studio 3.0 (Business/Team plan), and Cinema Studio 3.5 with Soul Cast AI actors, native dual-channel stereo audio, and 80+ one-click Apps.

---

Working Folders — file handling

The project has a workspace/ folder with three subfolders. Use them for every task that involves a user-provided document or a file you produce. This keeps uploads and deliverables out of the project root.

| Folder | Role | Your behavior | |--------|------|---------------| | workspace/input/ | Documents the user wants you to read (scripts, story bibles, briefs, character sheets, references). | Read from here first. If the user uploaded a file that landed elsewhere in the project root, move it into workspace/input/ before working with it. When you need a document from the user, ask them to drop it in workspace/input/. | | workspace/output/ | Files you generate for the user (prompt packs, shot breakdowns, batch CSVs, reports, exported docs). | Write every file deliverable here, not to the project root. Tell the user the path when you finish. | | workspace/processed/ | Inputs you have finished consuming. | When a task is complete, move the source from input/ to processed/ so input/ stays clean. Never delete the user's files — relocate them. |

Rules:

• Never scatter user uploads or generated files across the project root or skill folders — route them through workspace/.
• Treat workspace/input/ as the canonical place to look when the user says "the script / bible / reference I gave you."
• These three folders' contents are local-only (git-ignored); do not assume anything in them is committed.

Fast Path — Simple Creative Requests

If the user provides a clear creative intent ("write me a prompt for a car chase at night") with no specific constraints, generate immediately using these sensible defaults:

> Fast Path still requires reading skills/higgsfield-prompt/SKILL.md first — Fast Path means skip clarifying questions, NOT skip the file read.

| Parameter | Default | |-----------|---------| | Aspect ratio | 16:9 | | Duration | 8s | | Style | Cinematic | | Video model | Kling 3.0 (character-focused) or Sora 2 (action/scale) | | Image model | Soul 2.0 (portrait) or Nano Banana 2 (everything else) |

Do not ask clarifying questions. Deliver a ready-to-paste prompt. Mention the defaults used so the user can adjust if they want something different.

> If you did not read skills/higgsfield-prompt/SKILL.md earlier in this conversation, read it now before writing the prompt.

Full Path — Production Requests

When the user signals production-grade intent (Cinema Studio, multi-shot, specific model, budget constraints, client work), confirm before generating:

Required:

• Generation type: Image / Video / App (one-click)
• Video duration: 5s / 10s (image-to-video clips are 3–5s; text-to-video up to 10s+)
• Aspect ratio: 16:9 / 9:16 / 1:1 / 4:5 / 4:3 / 2.35:1 (default: 16:9)
• Model preference (or ask Claude to recommend — see skills/higgsfield-models/SKILL.md)

Optional (skip if user already provided):

• Visual style: Cinematic / VHS / Super 8MM / Anamorphic / Abstract
• Soul ID character reference (if character consistency needed)
• Reference image for image-to-video
• Motion preset preference

> Ask everything in one message — do not split across multiple rounds.

---

Route to the Right Skill

| User wants | Route to | |------------|----------| | User unsure which workspace/tool fits, or asks "what should I use for X" | higgsfield-workspaces | | Write or improve a prompt | higgsfield-prompt + relevant sub-skills | | Develop a character / world / story / premise before prompting, build a character sheet / story bible, lock a visual style ("visual DNA"), keep a character consistent across many shots, or "I keep getting generic AI characters" | higgsfield-character-design | | Cinematic still image prompt (shot framing, angles) | higgsfield-image-shots | | GPT Image 2.0 / gpt-image-2 prompt, UI mockup, infographic, character/reference sheet, layout-dense image, or static-ad recreation | higgsfield-gpt-image-2 | | Choose the right model | higgsfield-models | | Camera movement guidance (video) | higgsfield-camera | | Named motion preset (Explosion, Werewolf, etc.) | higgsfield-motion | | Visual style selection | higgsfield-style | | Character consistency across shots | higgsfield-soul | | VFX presets (Air Bending, Plasma, etc.) | higgsfield-motion | | One-click App workflow | higgsfield-apps | | Genre recipe (action, horror, ad, etc.) | higgsfield-recipes | | Fix a failing generation | higgsfield-troubleshoot | | Moodboard, style direction, Soul Hex color | higgsfield-moodboard | | Visual consistency across a project | higgsfield-moodboard | | Mixed Media presets (Noir, Sketch, Particles, etc.) | higgsfield-mixed-media | | Photodump style preset / social-feed photo-dump aesthetic | photodump-presets.md (root reference) | | Artistic style transformation, preset stacking | higgsfield-mixed-media | | Higgsfield Assist (GPT-5 copilot) | higgsfield-assist | | Credit optimization, plan selection, budget strategy | higgsfield-assist | | Cinema Studio 2.5 / Cinema Studio 3.0 / Cinema Studio 3.5 / multi-shot sequence workflow / Soul Cast | higgsfield-cinema | | Optical physics, camera bodies, lenses, Hero Frame | higgsfield-cinema | | Elements system (@Characters/@Locations/@Props) | higgsfield-cinema | | Director Panel, Speed Ramp, shot modes, Popcorn | higgsfield-cinema | | Cinema Studio 3.0 Smart mode, @ references, native audio | higgsfield-cinema | | Cinema Studio 3.5 — three-pill UI, Style Settings, Camera Settings, Manual Style, AI director toggle | higgsfield-cinema | | User mentions Marketing Studio, DTC Ads, ms_image, or marketing_studio_video model | higgsfield-marketing-studio | | User wants UGC / Tutorial / Unboxing / Hyper Motion / Product Review / TV Spot / Wild Card / UGC Virtual Try On / Pro Virtual Try On ad video | higgsfield-marketing-studio | | User mentions hook+setting picklists, preset / custom / text-generated avatars in MS context, or 4–15s ad video constraints | higgsfield-marketing-studio | | User wants to run a full campaign pipeline — research → plan → generate → publish → report, "create a campaign", "100 UGC videos", content plan, batch ads, cost-savings report | higgsfield-content-factory | | User mentions Higgsfield Canvas, a node-based / node-graph workspace, an infinite board, chaining prompts→images→videos into a pipeline, Shared Canvas, or a ComfyUI-style node workflow | higgsfield-canvas | | Multi-shot workflow, chaining tools, full production pipeline | higgsfield-pipeline | | Short film, branded content, Popcorn → video → assembly | higgsfield-pipeline | | Vibe Motion, kinetic typography, animated text, infographic/data/presentation animation, logo/brand animation as code (Remotion — crisp text, exact brand colors, deployable, real-time edits) | higgsfield-vibe-motion | | Animated AD / brand promo as an AI-generated video built brief → storyboard sheet → Seedance ("make a motion", "motion design ad", "animate my logo into a video", "promo/ad video", classicMD/highMD) | higgsfield-motion-design | | Vibe Motion vs Motion Design (both say "motion graphics / brand / logo animation"): want crisp text, exact colors, deployable code, editable canvas → higgsfield-vibe-motion (Remotion code); want a cinematic/kinetic AI video clip (pixel render, native audio, no guaranteed-crisp text) → higgsfield-motion-design (Seedance). When unsure, ask "should the text/logo stay perfectly crisp and editable (code), or is this a rendered video clip?" | — | | Pre-generation memory check, apply past failure fixes | higgsfield-recall | | User reports a generation result (kept/rejected/flagged) — log it to the ledger | higgsfield-recall | | Takes-per-kept ratios, credit budgeting from logged data | higgsfield-assist | | Audio design, dialogue cues, SFX, ambient sound | higgsfield-audio | | Seedance 2.0 / Pro prompt, flagged prompt, credit waste on Seedance | higgsfield-seedance | | Precise facial expression / FACS / Action Unit codes (AU12, AU6…), forced or uncanny or mixed expression, close-up micro-performance, monologue/dialogue facial acting, "which AU code for anger/fear", FACS reference sheet | higgsfield-facs | | "Make a shotlist", break a script/brief/treatment into many connected Seedance prompts, director's shotlist, global style prefix + @-glossary + named per-scene prompts as one editable HTML | higgsfield-shotlist-director | | User has Higgsfield CLI / MCP / bundled skills installed and asks how this skill works alongside them | higgsfield-stack | | User mentions higgsfield auth login, higgsfield generate create, mcp.higgsfield.ai/mcp, /higgsfield:generate, or asks "do I need both" | higgsfield-stack | | User asks where the prompt construction ends and the CLI/MCP execution begins (handoff questions) | higgsfield-stack |

---

Check Templates for Genre Match

Before writing a prompt from scratch, check if the user's request matches a common genre pattern. The templates/ folder contains 10 annotated example templates with line-by-line breakdowns, recommended models, negative constraints, and variations.

| User request matches | Check template | |---------------------|----------------| | Chase, pursuit, action, parkour | templates/01-cinematic-action-chase.md | | Product, commercial, ad, UGC | templates/02-product-ugc-showcase.md | | Horror, scary, creepy, dread | templates/03-horror-atmosphere.md | | Fashion, editorial, lookbook | templates/04-fashion-editorial.md | | Sci-fi, cyberpunk, VFX, space | templates/05-sci-fi-vfx.md | | Portrait, character intro, close-up | templates/06-portrait-character-intro.md | | Landscape, nature, establishing shot | templates/07-landscape-establishing-shot.md | | Comedy, social media, TikTok, skit | templates/08-comedy-social-media.md | | Romance, intimate, couple, wedding | templates/09-romantic-intimate.md | | Dance, music, performance, concert | templates/10-dance-music-performance.md |

Use the template as a starting point — adapt the example prompt to the user's specific request. The annotations explain WHY each element works, helping you make informed substitutions.

Technique templates (templates/seedance/) — structure templates for Seedance prompts where the user request is technique-shaped rather than genre-shaped:

| Technique need | Template | |---|---| | Pre-visualize multi-character spatial geometry before prompting | templates/seedance/top-down-map.md | | Multi-character shot with cross-character relationships | templates/seedance/multi-character-anchor.md | | Single-character shot with position + pose + contact-point locks | templates/seedance/single-character-position.md | | Worked example: two-character anchoring end-to-end | templates/seedance/worked-example-two-character.md | | Anime / stylized-2D animation — layered formula + style block + character turnaround | `templates/seeda

…

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: OSideMedia
• Source: OSideMedia/higgsfield-ai-prompt-skill
• License: MIT
• Homepage: https://higgsfield.ai

Install and usage instructions live in the source repository linked above.