What problem does it solve? Users working with Higgsfield's official tooling (CLI, MCP connector, bundled skills) alongside a prompt-engineering skill often face confusion about which layer owns prompt construction versus execution, leading to duplicated logic, invalid CLI flags, and wasted generation credits. ## Core Features & Use Cases - Layer Separation Rules: Defines that prompt construction (MCSLA structure, vocabulary, negative constraints) stays in this skill while authentication, uploads, job submission, and polling belong to Higgsfield's CLI, MCP, or bundled skills. - Two-Step Preflight Discipline: Documents schema verification (higgsfield model get <model> or models_explore) followed by cost estimation (higgsfield generate cost or get_cost: true) before any paid generation. - Detection and Handoff Templates: Provides signals for detecting which execution surface is present and one-line handoff templates for CLI, MCP, or bundled skills. - Use Case: A user in Claude Code asks for a Kling 3.0 video prompt and mentions having the Higgsfield CLI installed; the skill produces the prompt, appends a preflight cost-check recommendation, and hands off with the correct higgsfield generate create invocation line. ## Quick Start Ask the assistant to write a Higgsfield video prompt and mention that you have the Higgsfield CLI or MCP connector installed so it can add the correct preflight and handoff guidance.