Seedance Video

Beruf

Kategorien

Mobil

Do not load all references by default. Read only the files needed for the current task.

2. Keep project-local markdown up to date

Before the first generation in a workspace, check whether these files exist:

• docs/seedance/project-notes.md
• docs/seedance/prompt-retrospective.md

If they exist, read them first and follow the accumulated constraints.

Use scripts/update_project_markdown.py to create or update them whenever either of these happens:

• the user gives stable project constraints
• the prompt is materially refined
• a generation succeeds or fails and there is a lesson worth preserving

project-notes.md is for persistent project-specific cautions and preferences:

• subject continuity
• mandatory or banned camera behavior
• duration or ratio preferences
• audio rules such as “no BGM” or “close-mic SFX only”
• style constraints
• output path conventions

prompt-retrospective.md is for chronological iteration logs:

• what changed in the prompt
• why it changed
• expected effect
• task id or output path
• success/failure and lessons learned

If the user only wants prompt polishing and no API call yet, still update the retrospective when the prompt changes in a meaningful way.

3. Generate videos with the bundled CLI

Use the wrapper script:

"$SKILL_DIR/scripts/run_seedance.sh" generate "PROMPT" --wait --output "outputs/seedance/<name>.mp4"

Status query:

"$SKILL_DIR/scripts/run_seedance.sh" get TASK_ID --json

The copied CLI supports:

• --platform volc|byteplus
• --model
• --first-frame
• --last-frame
• --reference-image
• --generate-audio
• --camera-fixed
• --resolution
• --ratio
• --duration
• --frames
• --wait
• --output
• --last-frame-output
• --json

Authentication comes from the CLI itself. It resolves:

• ARK_API_KEY
• VOLC_ARK_API_KEY
• BYTEPLUS_ARK_API_KEY

If the user wants Seedance 2.0 or another non-default model, pass --model explicitly.

4. Output conventions

Unless the workspace already has a stronger convention, prefer:

• video outputs under outputs/seedance/
• last-frame outputs under outputs/seedance/frames/

Record the final output path or task id in the retrospective after each run.

Prompting Rules

• Do not rush into generation if the user is obviously still exploring prompt direction.
• When refining prompts, preserve the user’s intent and make the minimum changes needed to improve controllability.
• For ASMR, explicitly control sound, pace, and camera stability.
• For Seedance 1.5, be explicit about Voice / SFX / BGM.
• For Seedance 2.0, use image/video references when consistency matters more than pure text prompting.
• If the project has existing markdown notes, treat them as hard constraints unless the user overrides them.

Project Markdown Updates

Use scripts/update_project_markdown.py whenever you have enough signal to preserve a reusable lesson.

Typical call pattern:

python3 "$SKILL_DIR/scripts/update_project_markdown.py" \
  --workspace "$PWD" \
  --project "PROJECT_NAME" \
  --summary "What changed and why" \
  --status "refined" \
  --prompt-title "short-run-name" \
  --prompt-body "final prompt text" \
  --caution "Persistent caution 1" \
  --preference "Persistent preference 1" \
  --lesson "Retrospective lesson 1"

After a real generation run, also include:

• --task-id
• --output
• --model

Resources

scripts/

• scripts/seedance_cli.py: copied uv single-file CLI for Seedance API access
• scripts/run_seedance.sh: stable wrapper that invokes the bundled CLI via uv run
• scripts/update_project_markdown.py: project-local markdown updater for notes and retrospectives

references/

• references/seedance-1.5-guide.md
• references/seedance-2.0-guide.md
• references/seedance-asmr-prompts.md