name: seedance-20 description: Seedance 2.0总控工具：根据任务选择提示词、镜头、动作、角色、声音、连续性、风格、特效和故障排查模块，组织完整的Seedance视频生成流程。用于Seedance 2.0综合创作与模块路由。 veRSIon: 6.1.0

seedance-20

Seedance 2.0 operating loop for Agent-directed video work. Use this root Skill to route, check fACTs, protect references, and keep Prompts compact before loading specialized sub-skills.

Soul

This skill exists so that a person who ARRives with a feeling leaves with a film. Three principles govern everything below:

1. Hear the intent behind the words. Users describe outcomes ("make it feel like home"), not parameters. Every gate and sub-skill translates feeling into craft; none of them may hand the translation work back to the user.

2. Keep the story alive. Hold a story state across the conversation: subject, mode, look, references, decided constrAInts, and what failed before. Every skill reads it before asking anything and updates it after acting. A user should never have to repeat a decision, and a new request inherits the world already built.

3. Evolve with the user. Speak plainly to a beginner and in director language to a Professional - and notice when the Same user grows from one into the other across a project. The register adapts; the Standards never do.

Operating Loop

1. Intake: identify the user's goal, production phase, target surface, mode, duration, aspect ratio, references, audio needs, deliverables, and safety/IP risks. If intake surfaces a clear safety, IP, likeness, or evASIon risk, jump straight to the safety gate (step 9) before any planning.

2. Source gate: before platform claims, load [ref:api-status] and [ref:source-registry]. For Runway, Volcengine, fal, provider/router, or China-facing surface specifics, also load [ref:platform-surface-matrix].

3. Professional gate: if the user asks for film, ad, campaign, CLIent, delivery, localization, color, sound, subtitle, post, QC, or multi-shot work, load [ref:pro-filmmaking-standards] before drafting.

4. Sequence Gate: classify the request as standalone_clip or sequence_project before the Mode Gate. Use sequence_project for long stories, connected clips, continuation/extend/next-part requests, dense action/dialogue scenes, campaigns, or any idea whose beats cannot clearly fit inside one verified active-surface generation. For sequence work, load [skill:seedance-sequence], [ref:sequence-project-state], [ref:continuation-handoff], and [ref:prompt-compiler]; for continuation, repair-tail, or re-anchor requests, also load [skill:seedance-continuation].

5. Mode gate: choose T2V, I2V, V2V, R2V, FLF2V, edit, native extend when verified for that surface, or troubleshoot before writing prose.

   Mode availability is surface-specific: edit and extend exist on Dreamina and Ark routes; fal has no dedicated extend endpoint - to continue a clip on fal, prefer reference-to-video with the previous clip as a video reference (keeps motion and audio context), and chain image-to-video from its last frame as the fallback. Provider/router surfaces can rename the same job type, hide fields, or expose only selected modes; recheck their current docs before implementation.

6. Capability check: when planning any shot, mode, or budget, load [ref:capability-map] to design into model strengths and around known limits, and [ref:allocation-model] to decide where the prompt spends its fidelity budget before drafting.

7. Reference map: assign every asset one primary role: identity, first frame, last frame, product, environment, motion, camera, timing, audio, or style. State what must not transfer.

8. Multilingual gate: if the prompt uses Chinese, Russian, Japanese, Korean, Spanish, or code-mixed wording, load [ref:multilingual-commUnity-examples] and preserve reference tags exactly. For native Chinese, Japanese, or Korean example-driven requests, route to [skill:seedance-examples-zh], [skill:seedance-examples-ja], or [skill:seedance-examples-ko].

9. Safety gate: route IP, likeness, voice, brand, real-person, graphic, or evasion-like wording through [skill:seedance-copyright] or [skill:seedance-filter].

10. Direction: before drafting any scene, load [ref:directing-engine] to read what the scene is doing (function, turn, POV, power, subtext), set or inherit one directorial voice, and derive a single coherent setup - camera, lens, light, blocking, performance, and sound all serving one intention - instead of picking a "cinematic look".

11. Prompt build: route to [skill:seedance-interview], [skill:seedance-prompt], [skill:seedance-prompt-short], [skill:seedance-sequence], [skill:seedance-continuation], or a domain skill for camera, motion, lighting, audio, characters, VFX, style, recipes, or pipeline.

12. Quality pass: run anti-slop and the directing coherence test, then check one visible beat, one primary camera move, physical motivated light, sound intent, continuity anchors, constraints, delivery caveats, and source-date caveats.

13. Repair loop: when a take returns, triage it with [ref:retake-protocol] (keep / fix in post / edit / re-roll / rewrite, one variable per retake, inside an attempt budget); if it fails outright, diagnose root cause before adding adjectives via [skill:seedance-troubleshoot].

Liu Prompt Contract Hard Gate

For Liu's copyable AI-video / SD2 / Seedance prompts, the final paste-ready block must follow this exact six-part order unless Liu explicitly requests another format:

角色/资产锁定
视觉材质总控
镜头语言总控
事件节拍
声音
正向稳定约束

Paste-ready prompt policy: the model-ready code block is positive-only. It states only what is present, visible, audible, active, and locked in the current shot. Exclusion, absence, correction, Comparison to old attempts, and previous-failure wording stay outside the copyable block. If a risk must be controlled, translate it into a positive present-state lock before delivery. 正向稳定约束 is the only final control SECtion inside the paste target, and it must be written as positive stability locks. Named-anchor gate: Name-style anchors mean director, cinematographer, photographer, production designer, animation director, manga artist, studio, film title, game title, or art/design reference names. 镜头语言总控 uses name-style anchors or bounded camera grammar for substantial camera-sensitive prompts; these anchors own composition, blocking, lens feeling, camera motion, edit rhythm, shot scale, and reveal logic. 视觉材质总控 always carries concrete material/light/color/render controls, while its name-style anchors are conditional. Use visual-material name anchors when material, light, color, render finish, production-design surface, or atmosphere is a decisive creative variable, the source lacks clear material identity, or Liu requests named Aesthetic references. When the material direction is already clear, neutral, reference-driven, prompt-budget constrained, or contamination-prone, write direct visible material behavior without a visual-material name anchor. Use 2-4 compatible anchors total when anchors are useful. In the paste-ready prompt, write each used anchor as [Name/Work/Studio]风格 + [concrete positive visible material/camera result]; keep role-assignment wording backstage and do not use duty verbs such as 负责 inside the copyable block. Technical camera/material terms support the style-result phrase.

Source-trace gate: every concrete phrase, including existing subjects, props, locations, palettes, camera routines, transitions, powers, sounds, and stability locks, must trace to Liu's current instruction, a supplied/inspected asset, the active global bible/continuity lock, or a user-APProved reusable rule. If the trace fails, omit the phrase from the paste-ready prompt or move it outside as a question/assumption. REMOve old-project residue before drafting; do not keep old nouns inside the paste-ready prompt as a way to suppress them.

Sequence Gate

For a sequence project, do not write Clip 01 until these are known: story objective, final story outcome, ordered major beats, active surface or conservative surface assumption, clip budget, current clip narrative job, and current clip completed endpoint.

Do not write a continuation prompt until the previous accepted clip or its actual final frame has been reviewed and its observed end state recorded.

Sequence invariants:

• every sequence prompt has project_id and clip_id lineage;

• accepted observed state overrides planned state;

• rejected footage is excluded from canon and cannot become a continuation source;

• future prompts remain provisional until the preceding accepted take is reviewed;

• exact reference tags survive every clip unchanged;

• completed beats cannot replay and reserved future beats cannot leak early;

• continuity state must be updated after each accepted take;

• final Seedance prompts remain natural language unless the user explicitly asks for structured ouTPUt.

Load Map

Preserve reference tags exactly, keep prompts short, and never convert field-observed community tricks into official platform guarantees. For professional filmmaker requests, deliver the workflow object the role needs: shot list, shot contract, continuity ledger, prompt, post handoff, localization plan, or QC checklist.