higgsfield-stack
Higgsfield Stack — Coexistence With Official Tooling
What this sub-skill is for
"The Higgsfield stack" means Higgsfield's own official execution tooling: their command-line interface (CLI), their custom MCP connector for claude.ai and the Claude desktop app, and their three bundled skills (higgsfield-generate, higgsfield-soul, higgsfield-product-photoshoot). 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 two 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. Different jobs, no overlap. Our skill never invokes their CLI; their stack never invents prompt logic. The user gets one prompt from us and one execution path from them.
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). |
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. | 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/skills (v0.3.0). Three skills: higgsfield-generate, higgsfield-soul, higgsfield-product-photoshoot. Install via npx skills add higgsfield-ai/skills. Invoke as /higgsfield:generate, /higgsfield:soul, /higgsfield:product-photoshoot. |
Skill files matching those names visible in the agent's skill directory; user invokes one of those slash commands; user mentions installing higgsfield-ai/skills. |
Agents that consume Cowork-style skill bundles. All three skills drive the CLI under the hood — they are workflow/transport guidance, not prompt engineering. |