Professional video prompts, not AI slop.
Seedance 2.0 is the video model on Higgsfield. The skills in this repo are deep engineering frameworks — camera motion, lighting physics, temporal consistency, subject tracking. Claude uses them to architect prompts that look cinematic instead of generic.
Clone or download the skills from GitHub:
https://github.com/beshuaxian/higgsfield-seedance2-jineng Drop the skill files into ~/.claude/skills/. Restart Claude Code. The skills load automatically at the start of every session.
These are the same skills used to produce the cinematic examples you see on my page. They turn a one-line idea into a multi-paragraph Seedance prompt with lens specs, color grading notes, and camera blocking.
Key Takeaway You don't need to know prompt engineering. The skills do it. You describe the business. Claude writes the Seedance prompt.
Describe the business. Claude does the rest.
Once Playwright MCP and the Seedance skills are installed, you talk to Claude in plain English. No technical prompts. No camera jargon.
Example prompts that work:
- "Create a 15-second product video for a local coffee shop."
- "Make a cinematic lifestyle ad for a fitness studio in Miami."
- "Generate a luxury real estate walkthrough for a $2M penthouse."
Claude reads the business type, pulls the right Seedance skill (cinematic, e-commerce, real estate, food/beverage), architects the prompt, opens Higgsfield in the browser, and starts generating. You watch.
The first time you run it, Claude will pause so you can log into Higgsfield manually. After that, the session stays open and every generation is hands-off.
The structure that keeps Claude on rails.
Claude works best with a fixed project shape. Create this folder on your machine before your first run:
my-project/ ├── CLAUDE.md ├── SESSION-RESUME.md ├── images/ ├── videos/ ├── reference/ └── output/ CLAUDE.md is the brain. SESSION-RESUME.md saves you when a session crashes. images/, videos/, and output/ hold everything Higgsfield generates. reference/ is where you drop brand assets, logos, and product photos Claude can upload.
Keep every client or project in its own folder with its own CLAUDE.md. Claude reads the file automatically the moment you open a session in that directory.
The single most important file in your project.
Claude reads this at the start of every session. It defines your tools, your default settings, the exact workflow Claude must follow, and the rules it can't skip. Copy this as your starting point and tweak for your own style.
# My Higgsfield Workflow ## Tools Image generation: Higgsfield NanoBanana 2 Video generation: Higgsfield Cinema Studio ## Default Settings Aspect ratio: 9:16 Image count: 8 Quality: 2K unlimited ON Extra free gens: OFF ## Workflow 1. Navigate to higgsfield.ai/image/nano_banana_2 2. Confirm settings before generating 3. For each prompt: a. Clear prompt bar via JS b. Take screenshot to verify bar is empty c. Type prompt slowly d. Click Generate e. Clear bar via JS again f. Wait 7 seconds g. Repeat 4. Save outputs to /images/YYYY-MM-DD/ ## Rules - Always clear the prompt bar via JS before typing - Always screenshot after clearing to confirm it's empty - Never skip settings confirmation - Go straight to generating, no prompt previewsThe one thing that breaks every batch. Here's the fix.
This is the most important piece in the entire guide. When you run a batch on Higgsfield, the prompt bar does not clear properly between generations. Text from the last prompt bleeds into the next one. Claude types into a dirty field. The whole batch breaks.
The fix is to clear the prompt bar with JavaScript before every new prompt. It resets the field and fires the event Higgsfield needs to register the change.
const editor = document.querySelector('[id="hf:tour-image-prompt"] [contenteditable]') || document.querySelector('[contenteditable="true"]'); editor.innerHTML = '
'; editor.dispatchEvent(new Event('input', { bubbles: true })); Drop that snippet into your CLAUDE.md rules so Claude runs it automatically on every prompt. The per-prompt cycle should look like this:
1
Run the JS clear snippet
Resets the contenteditable field.
2
Screenshot to confirm empty
If not empty, clear again.
3
Type the prompt slowly
Use slowly: true on the Playwright type call.
4
Click Generate, clear again, wait 7s
Then repeat for the next prompt.
Claude crashes mid-batch. You don't lose your work.
Long sessions crash. It happens. Without a recovery file, you lose track of which prompts generated and which ones didn't — and you start from zero. The fix is a SESSION-RESUME.md file Claude updates as it works.
If a session crashes, open a fresh one and say:
"Read SESSION-RESUME.md and continue from where we left off."
Use this structure:
# Session Resume ## Model NanoBanana 2, URL: higgsfield.ai/image/nano_banana_2 ## Settings - Aspect ratio: 9:16 - 2K unlimited: ON - Extra free gens: OFF ## Progress | # | Description | Status | |---|----------------------|-----------| | 1 | [subject/character] | Generated | | 2 | [subject/character] | Generated | | 3 | [subject/character] | Pending | ## Next: #3 How To Use It Tell Claude to update the table after every successful generation. If anything breaks, you always know the next prompt in the queue.
One folder per day. Never lose an asset.
Tell Claude to save everything dated. Higgsfield exports don't come with clean filenames, so a dated folder structure is the only thing that keeps batches straight:
images/ └── 2026-04-14/ ├── char-01.png ├── char-02.png └── char-03.png Add this line to your CLAUDE.md rules:
Save all outputs to /images/YYYY-MM-DD/
That's the full setup. Playwright, skills, folder, CLAUDE.md, the JS fix, crash recovery, dated outputs. One prompt triggers unlimited cinematic video. Right now Higgsfield has up to 70% off Seedance 2.0 with unlimited generations — the cheapest way to access the best video model on the market.