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.

2. 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.

3. 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 <model> 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.

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