seedance-2-5-skill

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Seedance 2.5 Skill

Seedance 2.5 技能

Language route

语言路线

For an English request, follow this file and the
```
*.md
```
references.
For a Chinese request, read the Chinese workflow first, then use the matching
```
*.zh-CN.md
```
reference files.
Keep model IDs, JSON keys, commands, media placeholders, and native-audio symbols exactly as code. Do not translate them.

Do not force every request through one image-grid pipeline. Choose the video route first, then enable only the preparation modules the job needs.

若请求为英文，请遵循本文件及
```
*.md
```
参考文档。
若请求为中文，请先阅读中文工作流，再使用对应的
```
*.zh-CN.md
```
参考文件。
请严格保留模型ID、JSON键、命令、媒体占位符和原生音频符号的代码格式，不要翻译这些内容。

不要强行将所有请求都通过单一图像网格流程处理。请先选择视频生成路线，仅启用任务所需的准备模块。

1. Choose the creative route

1. 选择创意路线

Need	Route	Inputs	Result
One short, simple scene	T2V	Text prompt	One self-contained shot
A multi-shot sequence with readable panels	R2V storyboard	One complete storyboard image	One request turns panel order into a continuous video
A clip controlled by people, product, scene, or style assets	R2V asset references	A small role-specific asset pack	One clip built from those references
A shot with an exact beginning and ending	I2V shot pair	Start and end keyframes	One independently reviewable shot
An uninterrupted action exceeding the supported duration	Extend / chain	Previous generated tail frame and next prompt	Continuation of the same shot
One continuous piece carrying several events	Staged whole-short	Text plus optional references	One request covering ordered stages, each landing on a stated end state
A scoped change to an existing video	Editing	Source video plus target references	The source with only the named region or element changed
A bridge between two finished clips	Seamless transition	Two videos	Generated bridge content between them
Motion, blocking, and camera taken from a 3D preview	Blockout reference	Coarse or fine blockout video plus look references	Final render following the blockout's timing and staging

Use Seedance 2.0 as the executable default. Offer a Seedance 2.5 whole-short route only when the selected provider exposes that model and its actual limits.

The last four routes depend on capabilities that differ per model and per provider. Verify availability before offering one; see capabilities for the 2.0/2.5 comparison and for which published capabilities are platform features rather than API parameters.

需求	路线	输入	结果
单个简短、简单的场景	T2V	文本提示词	单个独立镜头
包含清晰分镜面板的多镜头序列	R2V分镜脚本	完整的分镜脚本图像	一次请求即可将面板顺序转换为连续视频
由人物、产品、场景或风格素材控制的片段	R2V参考素材包	小型角色专属素材包	基于指定参考素材生成的单个片段
有精确起始和结束画面的镜头	I2V镜头帧对	起始和结束关键帧	可独立审核的单个镜头
时长超过支持上限的连续动作	延长/链式生成	上一段生成的尾帧及下一个提示词	同一镜头的续播内容
包含多个事件的连续作品	分阶段完整短片	文本及可选参考素材	一次请求覆盖多个有序阶段，每个阶段都能达到指定的结束状态
对现有视频进行局部修改	编辑	源视频及目标参考素材	仅修改源视频中指定区域或元素的版本
两个已完成片段之间的过渡衔接	无缝转场	两段视频	生成两段视频之间的衔接内容
动作、布局和镜头取自3D预览	布局参考	粗略或精细的布局视频及视觉参考素材	遵循布局视频的时间节奏和场景安排的最终渲染结果

默认使用Seedance 2.0执行任务。仅当所选服务商开放Seedance 2.5完整短片路线及其实际限制时，才提供该选项。

最后四种路线的能力因模型和服务商而异。提供前请先验证可用性；查看能力说明了解2.0/2.5的对比，以及哪些已发布的能力属于平台功能而非API参数。

Storyboard or individual keyframes

分镜脚本或独立关键帧

Use the whole storyboard image in one R2V request by default whenever individual panels remain visually readable. Do not crop it first. Seedance can interpret the ordered panels as one continuous multi-shot video.
Use I2V shot pairs only when independent reshoots or precise start/end states matter more than the transition quality of one R2V generation.
Do not upload every storyboard cell as a default R2V asset pack. Use several R2V images only when each has a distinct role, such as subject, product, setting, style, or motion reference.

只要单个面板视觉清晰，默认在一次R2V请求中使用完整分镜脚本图像，无需预先裁剪。Seedance可将有序面板解读为连续的多镜头视频。
仅当独立重拍或精确的起始/结束状态比单次R2V生成的转场质量更重要时，才使用I2V镜头帧对。
不要默认将每个分镜单元格上传为R2V素材包。仅当每个图像有明确角色（如主体、产品、场景、风格或动作参考）时，才使用多个R2V图像。

2. Enable only needed preparation

2. 仅启用必要的准备工作

Subject brief

主体简介

Use this only for a person, product, prop, hand, vehicle, or scene that must recur. Record 3–5 invariants: silhouette or proportion, signature material or wardrobe, key colour, and any must-preserve marking. Skip it for a one-off atmosphere shot.

For a recurring person, make a clean face close-up and a separate full-body reference. Do not use a front/side/back composite as the identity input; it can be interpreted as multiple people. Multi-angle product references remain useful when the object itself must be shown from several sides.

仅当需要重复出现的人物、产品、道具、手部、车辆或场景时使用此模块。记录3-5个不变特征：轮廓或比例、标志性材质或服饰、关键颜色，以及任何必须保留的标记。一次性氛围镜头无需此步骤。

对于重复出现的人物，需提供清晰的面部特写和单独的全身参考图。不要使用正面/侧面/背面合成图作为身份输入，因为它可能被解读为多个人物。多角度产品参考图在需要从多个角度展示物体时仍然有用。

Keyframes

关键帧

Create a start keyframe for every I2V shot. Add an end keyframe only when the shot must land on a specific action, composition, product pose, or hand position. Use one clean scene per keyframe.

为每个I2V镜头创建起始关键帧。仅当镜头必须达到特定动作、构图、产品姿势或手部位置时，才添加结束关键帧。每个关键帧对应一个清晰的场景。

Storyboard

分镜脚本

Use an existing storyboard directly as the R2V reference. Seedance normally understands panel order and does not require panel numbers, dividers, arrows, or notes to be removed in advance. Make a clean copy only after a test generation actually renders an unwanted divider, number, caption, or multi-panel layout.

When a multi-shot request has no storyboard, use the Seedream template in prompt templates to create one board. Display that board in the host UI, inspect it yourself, then continue to Seedance R2V when it passes review. Showing the board is a progress update, not a user-approval gate.

For a supplied storyboard, display it unless it is already visible in the conversation. Check planned order, readable key beats, recurring-subject consistency, and content-specific constraints such as anatomy, product form, or critical text. Refine a visibly failed board before video generation. Ask the user only when a creative choice cannot be inferred.

If the route deliberately changes to I2V shot pairs, crop panels only then. Inspect the layout first: automatic crops can verify position, not whether the image model drew the intended panel layout.

直接将现有分镜脚本作为R2V参考素材使用。Seedance通常能理解面板顺序，无需预先移除面板编号、分隔线、箭头或注释。仅当测试生成结果中出现了不需要的分隔线、编号、说明文字或多面板布局时，才制作干净的副本。

当多镜头请求没有分镜脚本时，使用提示词模板中的Seedream模板创建分镜脚本。**在宿主UI中展示该分镜脚本，自行检查后，若通过审核再继续进行Seedance R2V生成。**展示分镜脚本是进度更新，而非用户审批环节。

对于用户提供的分镜脚本，若对话中未显示则需展示。检查计划顺序、清晰的关键节拍、重复主体的一致性，以及特定内容的约束（如解剖结构、产品形态或关键文字）。在生成视频前优化明显不合格的分镜脚本。仅当无法推断创意选择时，才询问用户。

若故意切换为I2V镜头帧对路线，此时才裁剪面板。先检查布局：自动裁剪可验证位置，但无法判断图像模型是否绘制了预期的面板布局。

3. Design continuity and cuts

3. 设计连续性与剪辑

First-and-last frames control one shot; they do not mean every shot must inherit the prior clip's tail.

Transition	Use prior tail as next start?	Design rule
One uninterrupted action	Yes	Generate in sequence and inspect the seam
Hard cut to a new angle, place, product, or time	No	Design each shot independently
Match cut	Usually no	Match movement direction, shape, colour, or composition
Occlusion or whip transition	No	End with the occluding action; start the next shot inside or after it
Insert or cutaway	No	Use an object, environment, or product detail as a bridge

Put important cuts, matches, and occlusions in the storyboard and prompt. Do not rely on a cross-dissolve to repair unrelated shots.

首尾帧控制单个镜头；并不意味着每个镜头都必须继承上一段剪辑的尾帧。

转场类型	是否将上一段尾帧作为下一段起始帧？	设计规则
连续无间断动作	是	按顺序生成并检查衔接处
硬切至新角度、新地点、新产品或新时间	否	独立设计每个镜头
匹配剪辑	通常否	匹配运动方向、形状、颜色或构图
遮挡或甩镜转场	否	以遮挡动作结束；下一个镜头从遮挡内部或之后开始
插入镜头或切出镜头	否	使用物体、环境或产品细节作为衔接

将重要的剪辑、匹配和遮挡效果写入分镜脚本和提示词。不要依赖交叉溶解来修复不相关的镜头。

4. Write the video prompt

4. 撰写视频提示词

Scope: put each instruction where it applies

范围：将每个指令放在适用的位置

Before writing blocks, sort what you know by what it governs. Instructions in the wrong place are the most common cause of drift — a global rule written inside beat 1 stops applying at beat 4.

Scope	Governs	Contents
Global	The whole piece	Film type, scene, style, one-sentence premise, camera principle
Locks	Anything that must not drift	Identity, reference roles, audio source, continuity, negatives
Time	One beat or stage	Stage events and their end states

Restate the two or three most expensive locks at the physical end of the prompt; recency helps. That is a placement convention, not a fourth scope — the content still belongs to Locks and appears there first.

This mirrors the model-agnostic spec format in the Universal Video Prompt Skill. Use that skill when one brief has to run on more than one model; use this file for Seedance-specific writing. This is a required companion for a complete Seedance 2.5 Skill setup. If the link does not resolve, help the user install

universal-video-prompt-skill

before continuing; do not invent the missing shared specification.

撰写模块前，先按管辖范围整理已知信息。指令放错位置是内容偏离的最常见原因——写在第1阶段的全局规则到第4阶段将不再适用。

范围	管辖内容	包含信息
全局	整个作品	影片类型、场景、风格、一句话主题、镜头原则
锁定项	任何不能偏离的内容	身份信息、参考素材角色、音频来源、连续性、否定约束
时间阶段	单个节拍或阶段	阶段事件及其结束状态

在提示词的末尾重申2-3个最重要的锁定项；最近的信息更有效。这是排版惯例，而非第四个范围——内容仍属于锁定项，且需先在锁定项部分列出。

这与通用视频提示词技能中的模型无关规范格式一致。当一个需求需要在多个模型上运行时，使用该技能；本文件仅用于Seedance专属的提示词撰写。这是完整Seedance 2.5技能设置的必备配套内容。若链接无法解析，请帮助用户安装

universal-video-prompt-skill

后再继续；不要自行编造缺失的共享规范。

Blocks

模块

Use only the blocks that affect the shot:

text

[subject/reference binding]
+ [one observable action]
+ [space and important object relationships]
+ [one primary camera move, coherent composite move, or a cut]
+ [light/style when it matters]
+ [audio or dialogue when enabled]
+ [end state, for any stage that must land somewhere specific]
+ [must-preserve constraints]

仅使用影响当前镜头的模块：

text

[主体/参考素材绑定]
+ [一个可观察的动作]
+ [空间布局及重要物体关系]
+ [一个主要镜头运动、连贯复合运动或一次剪辑]
+ [光线/风格（若重要）]
+ [音频或对话（若启用）]
+ [结束状态（适用于必须达到特定状态的阶段）]
+ [必须保留的约束]

End states carry multi-event work

结束状态承载多事件任务

For anything with more than one event, state what is visibly true when each stage ends. This is the highest-leverage single addition to a multi-stage prompt: it converts "keep it consistent" into something the model can target and you can check.

text

weak:   the two of them keep working on the bouquet
strong: end state: the florist holds the bouquet in the left hand;
        the scissors are back on the right side of the bench

An end state must be visible. "She feels relieved" is not one; "her shoulders drop and the frown clears" is. Read long video for the staged structure in full.

对于包含多个事件的内容，说明每个阶段结束时可见的真实状态。这是多阶段提示词中最有效的优化：它将“保持一致”转化为模型可定位、你可检查的目标。

text

弱表述：他们俩一直在制作花束
强表述：结束状态：花艺师左手拿着花束；剪刀放回工作台右侧

结束状态必须是可见的。“她感到放松”不是有效结束状态；“她肩膀下垂，眉头舒展”才是。阅读长视频了解完整的分阶段结构。

Time granularity: decide before writing beats

时间粒度：撰写节拍前先确定

Granularity is a prior decision. Writing beats at second precision and then downgrading means rewriting them.

Granularity	Use when
None — event order only	One continuous action, mood pieces, single shots. Timestamps here fragment the shot
Stages + end states	Most narrative work. Default
Second-level	Only under an external hard constraint: music, lip sync, reference handoff, a beat that must land at a fixed time

Infer it when the input settles it — a supplied music or voiceover track means second-level, a stated mood piece means none, an explicit fixed beat means second-level. When the request is a multi-event narrative with no external constraint, ask, and recommend with a reason rather than presenting a bare menu.

Timestamps allocate a time budget; they are not frame-accurate edit points, and actions may land slightly before or after a boundary. Do not demand impossible density such as three distinct actions inside one second.

Name reference roles explicitly, for example

Image 1: person

Image 2: product

Image 3: kitchen setting

For multi-shot R2V, list
```
Shot 1
```
,
```
Shot 2
```
, and
```
Shot 3
```
in event order. Set duration in provider controls rather than forcing exact seconds in text.
Prefer one primary movement per shot. A composite movement is valid when its direction, relation to the subject, and speed express one synchronized intent.
When native audio is enabled, use
```
（）
```
for music,
```
<>
```
for sound effects,
```
{}
```
for dialogue, and
```
【】
```
for on-screen captions.
State only constraints that are costly to redo.

Read the reference matching the job:

File	Read it for
prompt templates	Route-specific templates
prompt blocks	Reusable camera, audio, constraint patterns
long video	Staged structure, end states, timestamp rules
multi reference	Binding many assets without confusing them
real person	Believable human subjects, and when to omit the detail
transitions	Which transitions to generate and which to edit
editing and extension	Changing or continuing existing video
capabilities	2.0 vs 2.5 limits; platform features vs API parameters
model profile	Measured per-model behaviour and compile notes
cinematography	Detailed visual decisions
troubleshooting	Fault-specific fixes
execution adapters	Runner and adapter configuration

粒度需要预先确定。先以秒级精度撰写节拍再降级意味着重写。

粒度	使用场景
无——仅事件顺序	连续动作、氛围片段、单个镜头。此处添加时间戳会割裂镜头
阶段+结束状态	大多数叙事作品。默认选项
秒级	仅受外部硬约束时：音乐、唇形同步、参考素材交接、必须在固定时间点出现的节拍

当输入内容明确时，可推断粒度——提供的音乐或旁白轨道意味着秒级，明确的氛围片段意味着无粒度，明确的固定节拍意味着秒级。当请求是无外部约束的多事件叙事时，询问用户并给出推荐理由，而非仅提供选项菜单。

时间戳分配时间预算；它们不是帧精确的编辑点，动作可能略早或略晚于边界。不要要求在1秒内完成三个不同动作这种不可能的高密度任务。

明确命名参考素材角色，例如

Image 1: person

、

Image 2: product

、

Image 3: kitchen setting

。

对于多镜头R2V，按事件顺序列出
```
Shot 1
```
、
```
Shot 2
```
、
```
Shot 3
```
。在服务商控件中设置时长，而非在文本中强制指定精确秒数。
每个镜头优先使用一个主要运动。当复合运动的方向、与主体的关系和速度表达出统一意图时，复合运动是有效的。
启用原生音频时，使用
```
（）
```
表示音乐，
```
<>
```
表示音效，
```
{}
```
表示对话，
```
【】
```
表示屏幕字幕。
仅陈述重做成本高的约束。

阅读与任务匹配的参考文档：

文件	用途
提示词模板	路线专属模板
提示词模块	可复用的镜头、音频、约束模式
长视频	分阶段结构、结束状态、时间戳规则
多参考素材	绑定多个素材而不混淆
真实人物	逼真的人物主体，以及何时省略细节
转场效果	哪些转场需要生成，哪些需要后期编辑
编辑与延长	修改或续播现有视频
能力说明	2.0与2.5的限制对比；平台功能vs API参数
模型配置文件	实测的各模型行为及编译说明
电影摄影	详细的视觉决策
故障排查	针对特定故障的修复方案
执行适配器	运行器和适配器配置

5. Generate, review, and finish

5. 生成、审核与收尾

For a generated storyboard, create only the still first, display it in the conversation, and inspect it before any video request.
For a supplied storyboard, display the input unless it is already visible, then verify it fits the chosen route.
If the board passes review, generate one representative video pass without waiting for approval. Otherwise refine or regenerate the board first.
Review identity, locks, stage end states, composition, motion, seam, and audio in that order, and stop at the first failure — later checks are wasted effort on a wrong identity. Regenerate only the failed shot or segment.
Generate chains in order because the next segment needs the real prior tail. Generate cut-based clips independently and edit the planned transition.

The bundled script is a draft assembler, not a colour-grading or music-mixing system.

对于生成的分镜脚本，先创建静态图，在对话中展示，检查后再发起视频生成请求。
对于用户提供的分镜脚本，若对话中未显示则展示，然后验证其是否符合所选路线。
若分镜脚本通过审核，无需等待批准即可生成一个代表性的视频版本。否则先优化或重新生成分镜脚本。
按身份信息、锁定项、阶段结束状态、构图、运动、衔接处、音频的顺序审核，遇到第一个失败项即停止——身份错误时后续检查都是无用功。仅重新生成失败的镜头或片段。
按顺序生成链式内容，因为下一段需要上一段真实的尾帧。独立生成基于剪辑的片段，然后编辑计划的转场效果。

配套脚本是草稿汇编工具，而非调色或混音系统。

Atlas execution layer

Atlas执行层

Keep creative route selection independent from how a job is submitted. The default models are Seedream 5.0 Pro for stills and Seedance 2.0 for video; users may override them only after verifying route support.

In an agent conversation, use the Atlas Cloud Skill as the default direct generation route. It can discover a model, upload local media, submit an image or video request, poll, and retrieve outputs. Report

Execution: atlas-skill

only when it actually submitted the generation.

Use

atlas-mcp

only when the user explicitly selects MCP and its generation tools are exposed. Use

atlas-cli

only when the user explicitly selects a terminal, script, CI, or batch run. If the Atlas Cloud Skill is missing, help install

AtlasCloudAI/atlas-cloud-skills

before selecting a fallback.

Before reporting that an Atlas Cloud API key is missing, check the credentials in the selected execution process. For the REST runner, check

ATLASCLOUD_API_KEY

first and

ATLAS_CLOUD_API_KEY

as a compatibility alias. Do not infer credential availability from a different provider, plugin, or process; each execution channel can have an independent credential scope.

If neither key exists, direct the user to

https://www.atlascloud.ai/console/api-keys?utm_source=github&utm_campaign=awesome-seedance-2.5-prompts-skills

. Never ask them to paste the key in chat. Tell them to set

ATLASCLOUD_API_KEY

in the submitting process or the host's secure environment settings, then refresh or restart the execution session if needed. If the key exists in a parent or host configuration but is absent from the submitting process, report an environment-scope mismatch instead of saying the user has no key.

将创意路线选择与任务提交方式分开。默认模型为：静态图使用Seedream 5.0 Pro，视频使用Seedance 2.0；仅在验证路线支持后，用户才可覆盖默认设置。

在Agent对话中，默认使用Atlas Cloud Skill作为直接生成路线。它可发现模型、上传本地媒体、提交图像或视频请求、轮询状态并获取输出。仅当实际提交生成任务时，才报告

Execution: atlas-skill

。

仅当用户明确选择MCP且其生成工具开放时，才使用

atlas-mcp

。仅当用户明确选择终端、脚本、CI或批量运行时，才使用

atlas-cli

。若Atlas Cloud Skill缺失，请帮助用户安装

AtlasCloudAI/atlas-cloud-skills

后再选择备用方案。

报告Atlas Cloud API密钥缺失前，请检查所选执行进程中的凭据。对于REST运行器，先检查

ATLASCLOUD_API_KEY

，再检查兼容别名

ATLAS_CLOUD_API_KEY

。不要从其他服务商、插件或进程推断凭据可用性；每个执行渠道都有独立的凭据范围。

若两个密钥都不存在，请引导用户访问

https://www.atlascloud.ai/console/api-keys?utm_source=github&utm_campaign=awesome-seedance-2.5-prompts-skills

。切勿要求用户在聊天中粘贴密钥。告知用户在提交进程或宿主的安全环境设置中设置

ATLASCLOUD_API_KEY

，必要时刷新或重启执行会话。若密钥存在于父级或宿主配置中，但提交进程中缺失，请报告环境范围不匹配，而非告知用户没有密钥。

Billable task state machine

计费任务状态机

Apply these rules to every image and video generation:

After submission, record the prediction ID and logical stage immediately.
Treat
```
starting
```
,
```
queued
```
,
```
pending
```
, and
```
processing
```
as active. Poll the same ID every 2 seconds; never submit another task for that stage.
Treat
```
completed
```
and
```
succeeded
```
as successful terminal states. Download and inspect the output before starting a dependent stage.
Treat
```
failed
```
,
```
timeout
```
, and
```
canceled
```
as terminal failures. A new task requires an explicit retry decision; report the old ID and possible extra cost first.
A zero or missing processing-time field, delayed output, a local polling timeout, a stopped turn, or a temporary status-query error is not proof of failure. Preserve the ID and resume polling.
Interpret
```
continue
```
as “resume the existing task,” never as permission to retry. Do not submit video while its required storyboard is still active.

The 2-second interval applies to every Atlas execution route in this workflow. For

atlas-skill

, repeat its prediction-result step with the same ID. For

atlas-mcp

, call

atlas_get_prediction

with the same ID every 2 seconds. The MCP server performs a single status lookup per tool call; the agent owns the loop. The bundled REST and CLI adapters enforce the interval in code. A status lookup is read-only and must never be replaced with another generation call.

When the runner must resume, set

execution.resumePredictionIds.<stage>

to the existing ID. Supported stage keys include

grid

ref1

ref2

seg1

shot1

, and

clip1

. Never create a replacement merely because a prior polling process ended.

scripts/generate.mjs

cannot invoke an agent Skill or MCP server. It is a separate batch runner: it defaults to

atlas-rest

, and can use

atlas-cli

only when explicitly set in

execution.adapter

. It never selects CLI automatically. See execution adapters.

bash

undefined

以下规则适用于所有图像和视频生成任务：

提交后立即记录预测ID和逻辑阶段。
将
```
starting
```
、
```
queued
```
、
```
pending
```
、
```
processing
```
视为活跃状态。每2秒轮询同一ID；切勿为该阶段提交另一任务。
将
```
completed
```
和
```
succeeded
```
视为成功终端状态。下载并检查输出后，再启动依赖阶段。
将
```
failed
```
、
```
timeout
```
、
```
canceled
```
视为终端失败状态。新任务需要明确的重试决策；先报告旧ID及可能产生的额外费用。
处理时间字段为零或缺失、输出延迟、本地轮询超时、对话中断或临时状态查询错误不代表任务失败。保留ID并恢复轮询。
将
```
continue
```
解读为“恢复现有任务”，而非允许重试。分镜脚本仍在处理时，切勿提交视频生成请求。

2秒轮询间隔适用于本工作流中的所有Atlas执行路线。对于

atlas-skill

，使用同一ID重复执行预测结果步骤。对于

atlas-mcp

，每2秒调用一次

atlas_get_prediction

并传入同一ID。MCP服务器每次工具调用执行一次状态查询；轮询循环由Agent负责。配套的REST和CLI适配器在代码中强制执行该间隔。状态查询是只读操作，切勿替换为另一个生成调用。

当运行器必须恢复时，将

execution.resumePredictionIds.<stage>

设置为现有ID。支持的阶段键包括

grid

、

ref1

、

ref2

、

seg1

、

shot1

和

clip1

。切勿仅因之前的轮询进程结束而创建替代任务。

scripts/generate.mjs

无法调用Agent Skill或MCP服务器。它是独立的批量运行器：默认使用

atlas-rest

，仅当在

execution.adapter

中明确设置时才可使用

atlas-cli

。它不会自动选择CLI。请查看执行适配器。

bash

undefined

Generate a storyboard only. The runner prints [storyboard-preview] with an

仅生成分镜脚本。运行器会打印[storyboard-preview]及绝对路径；开始视频工作前，请展示并检查该图像。

absolute path; display and inspect that image before starting video work.

—

GRID_ONLY=1 node scripts/generate.mjs scripts/myjob.json

Run only the first independent clip or segment as a quality gate.

仅运行第一个独立片段或分段作为质量验证。

CLIPS_MAX=1 node scripts/generate.mjs scripts/myjob.json SEGS_MAX=1 node scripts/generate.mjs scripts/myjob.json


```json
{ "execution": { "adapter": "atlas-cli" } }

Available runner modes:

```
grid
```
: crop a model storyboard and make one independent I2V clip per panel; suitable for a hard-cut montage.
```
shot-pairs
```
: make independent I2V shots from
```
segments[]
```
, with a
```
first
```
and optional
```
last
```
keyframe index.
```
reference
```
: send a small role-specific set of R2V references. A reference may be generated from a prompt or read from a local file.
```
chain
```
: continue one action by feeding the generated tail frame to the next segment. It is an alignment aid, not a guarantee of an invisible seam.

For fault-specific fixes, read troubleshooting.

CLIPS_MAX=1 node scripts/generate.mjs scripts/myjob.json SEGS_MAX=1 node scripts/generate.mjs scripts/myjob.json


```json
{ "execution": { "adapter": "atlas-cli" } }

可用运行器模式：

```
grid
```
：裁剪模型分镜脚本，为每个面板生成独立的I2V片段；适用于硬切蒙太奇。
```
shot-pairs
```
：从
```
segments[]
```
生成独立的I2V镜头，包含
```
first
```
及可选的
```
last
```
关键帧索引。
```
reference
```
：发送一组小型角色专属的R2V参考素材。参考素材可由提示词生成或从本地文件读取。
```
chain
```
：将生成的尾帧传入下一个分段，以延续动作。这是对齐辅助工具，不保证衔接处完全无痕迹。

如需针对特定故障的修复方案，请阅读故障排查。