/higgsfield-stack

name: higgsfield-stack
description: "Use when the user mentions the Higgsfield CLI (binaries `higgsfield` / `higgs` / `hf`, `higgsfield auth login`, `higgsfield generate create`, `higgsfield workflow`, the `@higgsfield/cli` npm package), the Higgsfield MCP custom connector (`mcp.higgsfield.ai/mcp`) or its bundled workflows (`get_workflow_instructions` — character-sheet, thumbnail-generation, ugc-* videos, faceless-video, narrator, subtitles, product-photoshoot, brand-asset-creation, ad-multiplier, video-editing / Higgsedit, website-builder-flow), Higgsfield's bundled skills repo (`higgsfield-ai/skills` — `higgsfield-generate`, `higgsfield-soul-id`, `higgsfield-product-photoshoot`, `higgsfield-brandkit`, `higgsfield-marketplace-cards`, `higgsfield-websites`, `higgsfield-video-explainer`, `higgsfield-youtube-thumbnail`, invoked as `/higgsfield:generate` etc.), or asks how this skill coexists with those tools (`do I need both`, `how does this work with the CLI/MCP/skills`, `should Higgsfield's workflow do this or you`)."
user-invocable: true
metadata:
  tags: [higgsfield, stack, cli, mcp, official-skills, bundled-workflows, coexistence, handoff, environment]
  version: 1.3.1
  updated: 2026-09-26
  parent: higgsfield

Higgsfield Stack — Coexistence With Official Tooling

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

• [What this sub-skill is for](#what-this-sub-skill-is-for)
• [The three official surfaces](#the-three-official-surfaces)
• [The bundled skills at 0.12.0](#the-bundled-skills-at-0120)
• [Preflight discipline — check cost and balance before generating](#preflight-discipline--check-cost-and-balance-before-generating)
• [Two-step preflight](#two-step-preflight)
• [Verified preflight surfaces](#verified-preflight-surfaces)
• [Plan tier, not surface, controls queue priority](#plan-tier-not-surface-controls-queue-priority)
• [When to surface preflight in this skill's output](#when-to-surface-preflight-in-this-skills-output)
• [Iteration-budget projection (production-benchmarks tie-in)](#iteration-budget-projection-production-benchmarks-tie-in)
• [How our skill fits in](#how-our-skill-fits-in)
• [Coexistence rules](#coexistence-rules)
• [Higgsfield's bundled workflows](#higgsfields-bundled-workflows)
• [Coexistence rules for Higgsfield's workflows](#coexistence-rules-for-higgsfields-workflows)
• [Naming overlap — `higgsfield-soul-id` (theirs) vs `higgsfield-soul` (ours)](#naming-overlap--higgsfield-soul-id-theirs-vs-higgsfield-soul-ours)
• [Detection guidance](#detection-guidance)
• [Handoff templates](#handoff-templates)
• [Seedance preflight integration](#seedance-preflight-integration)
• [What this sub-skill does NOT do](#what-this-sub-skill-does-not-do)
• [Related sub-skills](#related-sub-skills)

<!-- /CONTENTS -->

What this sub-skill is for

"The Higgsfield stack" means Higgsfield's own official tooling: their command-line interface (CLI), their custom MCP connector for claude.ai and the Claude desktop app — which now ships its own **bundled workflows** — and their bundled-skills repo (`higgsfield-ai/skills`, v0.12.0). Any one of those tools — or any combination — may be present in the user's environment alongside this prompt skill. This sub-skill documents how the surfaces coexist, what each one owns, and how a clean handoff looks.

The core principle is a layer split. This skill is the prompt-construction + production-discipline layer: MCSLA structure, named platform vocabulary, model selection criteria, Seedance preflight, Cinema Studio depth, Soul Character Anchor Block, Two-Tool Refinement Pipeline guidance, anti-bombast register, shared negative constraints. Their stack is the execution layer: authentication, file uploads, job submission, polling, retries, returning a result URL. Our skill never invokes their CLI.

**What changed in 2026.** The execution layer is no longer prompt-free. Higgsfield's connector now carries 16 named workflows (character sheets, thumbnails, UGC videos, faceless video, ad multiplication, editing …) that bring their own prompt engines, and several of their bundled skills enhance prompts on the backend. The split still holds for direct generation; for requests that are squarely one of their workflows, § Higgsfield's bundled workflows says what this library adds and what it hands off.

---

The three official surfaces

| Surface | What it is | Detection signals | Best fit | |---|---|---|---| | **Higgsfield CLI** | Binary distributed at https://github.com/higgsfield-ai/cli. Binary names: `higgsfield`, `higgs`, `hf`. Install via `curl -fsSL https://raw.githubusercontent.com/higgsfield-ai/cli/main/install.sh \| sh` or `brew install higgsfield-ai/tap/higgsfield`. Auth via `higgsfield auth login` (device flow). As of 1.1.23 its commands include `generate`, `model`, `workflow`, `preset`, `voices`, `upload`, `soul-id`, `marketing-studio`, `product-photoshoot`, `marketplace-cards`, `website`, `workspace`, `account`. | User types `higgsfield`, `higgs`, or `hf` in conversation; user says "I have the CLI installed"; user pastes output from `higgsfield ... --json` | Claude Code, Codex, Cursor, or any terminal-native agent. Per Higgsfield's own guidance: if the user is in Claude Code or Codex, prefer the CLI over the MCP. | | **Higgsfield MCP** | Custom connector at https://mcp.higgsfield.ai/mcp. Separate product from the CLI. Installed in claude.ai or the Claude desktop app via Settings → Connectors → Add custom connector. Ships **bundled workflows** loaded with `get_workflow_instructions` (§ Higgsfield's bundled workflows). | User is in claude.ai web or the Claude desktop app (not a terminal); user mentions "the connector" or "MCP" or `mcp.higgsfield.ai`; the current Claude session has tools whose names mention Higgsfield generation. | claude.ai web, Claude desktop app, environments without a terminal. | | **Higgsfield bundled skills** | Skill repo at https://github.com/higgsfield-ai/skil