Seedance 2 5 Video Director

Seedance 2.5 Video Director

Translate a video idea, existing prompt, storyboard, or labeled image/video/audio set into a controllable Seedance 2.5 prompt. Direct the model-specific execution; do not replace genre-specific story development when another director Skill already supplies it.

Installation onboarding protocol

1. Show references/first-use-onboarding.md only when the installer or runtime explicitly indicates that the Skill was just installed, or when the user explicitly asks for help, installation guidance, a tutorial, the input template, or examples.
2. A new conversation or the Skill's first invocation in a conversation is not evidence of a new installation. Never repeat onboarding merely because conversation-level or cross-session state is unavailable.
3. For an ordinary video request, immediately perform the requested task without prepending onboarding content.
4. When installation onboarding is genuinely triggered, display its 学习指导, 最小输入模板, and 学习示例, then continue the same request without asking the user to repeat it.
5. The onboarding guide teaches usage only. It must not silently replace the user's requested duration, ratio, assets, dialogue, operation, or deliverable.

Required loading order

1. Apply the installation onboarding protocol above only when its explicit trigger is present.
2. Read references/capabilities-and-limits.md for every request. Validate media and duration before drafting.
3. Read references/prompt-blueprints.md and load only the selected primary-mode section.
4. Read references/multimodal-patterns.md whenever the request includes reference media or any specialist capability.
5. Read references/realistic-direction-patterns.md whenever the request includes realistic human acting, dialogue, emotional conflict, a relationship scene, sports/variety live coverage, obstacle physics, or a user-supplied example whose structure should be adapted.
6. Read references/official-examples.md only when a concrete provider example is needed to resolve an underspecified structure, optimize an existing prompt, or check a difficult mode. Do not copy an example mechanically.

Boundary

• Produce planning and text prompts only. Never invoke video generation, spend credits, submit jobs, or claim a video was generated.
• Keep this Skill provider-specific. Do not present these limits or syntaxes as universal rules for other video models.
• When a genre director Skill is also active, preserve its story, shot intent, visual anchors, and continuity card; use this Skill to adapt them to Seedance 2.5 modes, asset references, timing, and prompt syntax.

Select one primary mode

Use explicit user wording first, then infer from duration, source media, and requested operation. Select exactly one primary mode; add zero or more specialist capabilities.

Treat realistic-person direction, multiple-person locking, timbre reference, BGM removal, creative transfer, local removal/replacement, perspective reconstruction, and green-screen compositing as specialist capabilities, not extra primary modes.

If two primary modes remain materially plausible and would produce different prompts, ask one compact question that names the competing modes. Do not ask for information that can be safely inferred.

Minimal-question policy

• Preserve every explicit user parameter. Never silently replace a requested duration, ratio, dialogue, asset role, editing target, or protected element.
• Lock the requested deliverable before drafting. 只要脚本, 只要提示词, 只诊断, and 按原结构改写 are output constraints, not stylistic suggestions.
• Treat 人物参考图, 角色参考图, or 情侣参考图 as a complete visible-character reference by default. Apply the detailed scope rules in multimodal-patterns.md; do not silently reduce the reference to face identity or redesign visible wardrobe.
• For an ordinary new video with no duration, use 15 seconds and label it as a supplemented default.
• For a ratio that cannot be inferred from the target platform or supplied media, use 16:9 and label it as a supplemented default.
• For Long Video, extension, or an explicitly precision-timed request, require the exact duration because it changes the structure.
• Require clarification when an asset identity or role is ambiguous, an edit target cannot be located, extension direction is missing, two videos lack an intended order, or the requested inputs exceed a platform limit and no safe reduction is evident.
• Otherwise, make restrained defaults and proceed. Group all indispensable questions into one turn.

Direction workflow

1. Lock the request. Record primary mode, deliverable type, duration, ratio, resolution when relevant, language, visual direction, sound policy, and requested output mode. Mark inferred defaults.
2. Inventory assets. Use only media the user actually supplied or explicitly numbered. Normalize labels to @Image N, @Video N, and @Audio N without changing their order.
3. Build the asset lock table. For every asset, record label | role | active time | preserve | do not inherit. Omit the table only when there are no assets.
4. Lock example inheritance. If the user supplies an example, list which dimensions transfer: hierarchy/detail level, timing, story, camera, performance, style, or asset scope. 参考结构 transfers hierarchy and granularity only unless the user says otherwise.
5. Assign specialist capabilities. Add only capabilities the request needs. Keep each instruction tied to a subject, source, destination, or time range.
6. Choose the blueprint and control depth. Follow the selected mode in references/prompt-blueprints.md. Match the user's requested detail level; do not collapse a high-control example into a generic short prompt or force a simple request into a timestamp screenplay.
7. Write continuity locks. Cover only relevant invariants: identity, count, wardrobe, prop ownership, geography, subject scale, camera axis, light direction, palette, material, voice, dialogue, and protected source footage.
8. Draft the requested artifact. For prompts, order instructions from global intent to asset binding, chronological execution, audio, continuity, and prohibitions. For scripts, use playable scene logic, shot progression, dialogue, performance, sound, and an ending state without provider-wrapper boilerplate.
9. Audit. Check duration, dialogue capacity, references, mode syntax, asset roles, performance causality, camera grammar, continuity, edit scope, audio policy, example-transfer scope, and contradictions before responding.