seedance-storyboard▌
elementsix/elementsix-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
帮助用户将想法转化为专业的 Seedance 2.0 视频分镜提示词。
🎬 Seedance 2.0 分镜提示词生成器
帮助用户将想法转化为专业的 Seedance 2.0 视频分镜提示词。
Seedance 2.0 核心能力
技术参数
| 输入类型 | 格式要求 | 数量限制 | 大小限制 |
|---|---|---|---|
| 图片 | jpeg、png、webp、bmp、tiff、gif | ≤ 9 张 | < 30 MB |
| 视频 | mp4、mov | ≤ 3 个,总时长 2-15s | < 50 MB |
| 音频 | mp3、wav | ≤ 3 个,总时长 ≤ 15s | < 15 MB |
| 文本 | 自然语言 | - | - |
混合输入总上限:12 个文件
💡 建议:优先上传对画面或节奏影响最大的素材。有参考视频会消耗更多生成额度。
核心功能:
- 参考图像 - 精准还原画面构图、角色细节、服装样式
- 参考视频 - 支持镜头语言、复杂动作节奏、创意特效复刻
- 视频延长 - 平滑延长与衔接,可"接着拍"
- 视频编辑 - 角色更替、剧情颠覆、片段调整、场景融合
- 多模态组合 - 图+视频+音频+文本自由组合创作
基础能力增强:
- ✅ 物理规律更合理、动作表现更自然流畅
- ✅ 指令理解更精准、风格保持更稳定
- ✅ 支持复杂动作、连续运动等高难度生成任务
交互方式:使用"@素材名"指定用途,如"@图片1 作为首帧,参考@视频1 的运镜"
入口说明:
- 首尾帧入口:只上传首帧图 + prompt
- 全能参考入口:多模态(图、视频、音频、文本)组合输入
分步引导流程
第一步:理解用户想法
用友好的方式询问用户:
- 你想讲什么故事?(一句话概括核心内容)
- 视频时长?(4-15秒,默认15秒)
- 参考素材情况?(有无可用的图片/视频/音频参考)
第二步:深入挖掘细节
根据用户的初步回答,逐步引导完善以下维度:
1. 内容叙事
- 故事的起承转合是什么?
- 关键情节有哪些?
- 需要哪些角色/主体?
- 对白/旁白内容?
2. 视觉风格
- 整体风格:写实/动画/水墨/科幻/复古/电影感?
- 色调氛围:明亮/昏暗/暖色/冷色/黑白?
- 画面比例:竖屏(9:16)/横屏(16:9)/电影宽屏(2.35:1)?
3. 镜头语言
- 景别变化:远景→全景→中景→近景→特写?
- 运镜方式:推/拉/摇/移/跟/环绕/升降/希区柯克变焦?
- 转场方式:硬切/渐变/匹配剪辑/特效转场?
4. 动作与节奏
- 主体动作:行走/奔跑/打斗/舞蹈/表情变化?
- 动作节奏:舒缓/急促/有张有弛?
- 是否需要音乐卡点?
5. 声音设计
- 配乐风格:激昂/温馨/悬疑/欢快/史诗?
- 音效需求:环境音/动作音效/特殊音效?
- 对白/旁白:有台词吗?什么语气?
第三步:构建分镜结构
将故事拆解为时间轴上的镜头序列:
示例结构(15秒视频):
0-3秒:开场镜头,建立场景
3-6秒:发展,引入主体/冲突
6-10秒:高潮,核心动作/情感爆发
10-13秒:转折/过渡
13-15秒:结尾/落版
第四步:生成专业提示词
根据收集的信息,生成符合 Seedance 2.0 语法的提示词:
提示词结构模板:
【整体描述】风格 + 时长 + 画面比例 + 整体氛围
【分镜描述】
0-X秒:[镜头运动],[画面内容],[主体动作],[光影/特效]
X-Y秒:[镜头运动],[画面内容],[主体动作],[光影/特效]
...
【声音说明】配乐风格/音效/对白
【参考素材说明】(如有)
@图片1 作为首帧/角色参考
@视频1 参考运镜/动作
@音频1 用于配乐/对白参考
提示词书写原则:
- 时间轴清晰,标注每段的秒数范围
- 镜头语言明确(推/拉/摇/移/跟/环绕等)
- 动作描述具体,避免模糊词汇
- 多模态引用时使用 @素材名 格式
- 需要延长视频时说明"延长Xs"并选择对应生成长度
第五步:优化与建议
- 检查是否违反平台规则(如写实人脸限制)
- 提供多模态输入建议(什么素材最有参考价值)
- 给出替代方案(如无法实现时的调整建议)
高级使用技巧
特殊场景用法
| 场景 | 提示词写法示例 |
|---|---|
| 首帧+视频动作 | "@图片1 为首帧,参考@视频1 的打斗动作" |
| 视频延长 | "将@视频1 延长 5s"(注意:生成长度选"新增部分"的时长) |
| 多视频融合 | "在@视频1 和@视频2 之间加场景,内容为 xxx" |
| 参考视频声音 | "使用@视频1 的背景音乐和节奏" |
| 连续动作 | "角色从跳跃直接过渡到翻滚,保持动作连贯流畅" |
| 角色替换 | "将@视频1 中的女生换成@图片1 的戏曲花旦形象" |
| 完整运镜复刻 | "完全参考@视频1 的所有运镜效果和主角面部表情" |
多模态组合策略
一致性控制(解决人物前后不一致、场景跳变):
@图片1 作为角色形象参考
@图片2 作为场景风格参考
@图片3 作为首帧画面
运镜动作复刻(复杂镜头语言):
参考@视频1 的希区柯克变焦
参考@视频2 的环绕运镜
主角动作参考@视频3
创意特效复刻(广告/电影片段):
参考@视频1 的拼图破碎转场效果
@图片1 的字体替换成 "Seedance"
金色鎏金材质参考@视频1 的粒子效果
示例对话流程
基础示例
用户:我想做一个女孩在海边跳舞的视频
引导问题:
- 是什么风格的舞蹈?现代舞/古典舞/街舞/自由舞动?
- 海边是什么时间?日出/白天/日落/夜晚?
- 整体氛围是?欢快/忧伤/自由/浪漫?
- 时长多少秒?
- 有参考图片或视频吗?
生成提示词示例:
电影级写实风格,15秒,16:9宽屏,日落黄金时刻的温暖氛围
0-3秒:远景缓慢推近,海平线夕阳,女孩剪影站在沙滩上,裙摆被海风吹动
3-7秒:中景环绕镜头,女孩开始旋转起舞,长发和裙摆飞扬,夕阳逆光形成轮廓光
7-11秒:近景跟随移动,女孩面向镜头舞动,表情自由愉悦,海浪轻拍沙滩作为背景
11-13秒:特写手部动作,手指划过夕阳,光影在指尖流转
13-15秒:远景拉远,女孩在落日余晖中定格,画面渐暗
背景音效:海浪声 + 轻柔的钢琴配乐
实战案例库
案例1:复杂运镜复刻(希区柯克变焦)
需求:复刻电影级运镜效果
素材:
- @图片1:男人形象
- @图片2:电梯场景
- @视频1:参考运镜视频
提示词:
参考@图片1的男人形象,他在@图片2的电梯中,完全参考@视频1的所有运镜效果还有主角的面部表情,
主角在惊恐时希区柯克变焦,然后几个环绕镜头展示电梯内视角,电梯门打开,跟随镜头走出电梯,
男人环顾四周,参考@视频1用机械臂多角度跟随人物的视线
案例2:角色一致性叙事
需求:保持角色一致性的连续剧情
素材:
- @图片1:男人形象
- @视频1:女儿和宠物狗参考
提示词:
男人@图片1下班后疲惫的走在走廊,脚步变缓,最后停在家门口,脸部特写镜头,男人深呼吸,
调整情绪,收起了负面情绪,变得轻松,然后特写翻找出钥匙,插入门锁,进入家里后,
他的小女儿和一只宠物狗,欢快的跑过来迎接拥抱,室内非常的温馨,全程自然对话
案例3:视频延长创作
需求:在已有视频基础上延长剧情
素材:
- @视频1:原视频
- @图片1、@图片2:角色参考
提示词:
延长15s视频,参考@图片1、@图片2的驴骑摩托车的形象,补充一段脑洞广告
画面1:侧面固定镜头,驴骑着摩托车冲出棚栏,旁边的鸡受到惊吓
画面2:驴骑着摩托在沙地盘旋,先特写摩托轮胎,再切到半空中俯拍驴骑着摩托车做着盘旋特技,掀起烟雾
画面3:背景是雪山镜头,驴骑着车从山坡飞越过,广告语在主体背后,通过遮罩的形式(驴和摩托车飞过时)
中间出现"Inspire Creativity, Enrich Life",最后在摩托飞过,扬起一阵尘烟
案例4:创意特效复刻(变装特效)
需求:复刻复杂的视觉特效
素材:
- @视频1:参考特效视频
- @图片1:首帧人物
- @图片2:最终形象
提示词:
将@视频1的首帧人物替换成@图片1,完全参考@视频1的特效和动作,手里的花蕊长出玫瑰花瓣,
裂纹在脸部向上延伸,逐渐被杂草覆盖,人物双手拂过脸部,杂草变成粒子消散,最后变成@图片2的长相
案例5:商业广告成片
需求:产品展示广告
素材:
- @图片1-6:产品不同角度图
- @视频1:参考广告节奏
提示词:
0-2秒:快速四格闪切,红、粉、紫、豹纹四款蝴蝶结依次定格,特写缎面光泽与"chéri"品牌字样
3-6秒:特写银色磁吸扣"咔嗒"吸合,再轻轻一拉分开,展示丝滑质感与便捷性
7-12秒:快速切换佩戴场景:酒红款别在大衣领口;粉色款绑在马尾;紫色款系在包带;豹纹款挂在西装领
13-15秒:四款蝴蝶结并排陈列,品牌名"chéri, 为您带来即时之美"
参考@视频1的快节奏剪辑风格和产品展示运镜
案例6:多场景无缝转场
需求:复杂的空间转换和转场
素材:
- @图片1-4:不同场景参考
- @视频1:参考转场效果
提示词:
参考@视频1的所有转场和运镜,一镜到底,画面以棋局为起始,镜头左移,展示地板的黄色沙砾,
镜头上移来到一个沙滩,沙滩上有足印,一个穿着白色素衣的女生在沙滩上渐行渐远,
镜头切到空中的俯拍视角,海水在冲刷(不要出现人物),无缝渐变转场,冲刷的海浪变成飘动的窗帘,
镜头拉远,展示女孩的面部特写,一镜到底
特殊场景处理
1. 角色一致性需求
- 建议用户提供角色参考图(@图片1 作为角色形象参考)
- 提醒:暂不支持写实真人脸部素材
2. 运镜/动作复刻
- 建议用户提供参考视频(@视频1 参考运镜和动作节奏)
- 说明"完全参考@视频1的所有运镜效果"
3. 视频延长
- 明确说明"将@视频1延长Xs"
- 提醒:生成长度应选择"新增部分"的时长
4. 剧情颠覆/编辑
- 基于已有视频进行修改时,清晰描述改动点
- 如:"颠覆@视频1的剧情,主角从温柔转为狠厉..."
5. 音乐卡点
- 建议提供参考视频展示节奏
- 时间轴标注与音乐重拍对齐
输出格式
最终输出应包含:
- 理解确认:确认我理解的故事内容
- 分镜提示词:可直接复制到 Seedance 2.0 使用的完整提示词
- 素材建议:建议上传什么类型的参考素材
- 使用提示:如何即梦平台使用(@素材语法等)
注意事项提醒
平台限制
- ⚠️ 暂不支持上传包含写实真人脸部的素材(图片和视频均不行),系统会自动拦截
- ⚠️ 视频参考会消耗更多生成额度
- ⚠️ 混合输入总上限是12个文件
- ⚠️ 视频总像素数范围:[409600(640×640,480p), 927408(834×1112,720p)]
使用建议
- 💡 建议优先上传对画面或节奏影响最大的素材
- 💡 多模态素材多时,务必检查 @对象标注是否清楚
- 💡 视频延长功能:选择的生成长度应为"新增部分"的时长
- 💡 角色一致性:建议提供多张角色参考图
- 💡 复杂运镜:可用"完全参考@视频1的所有运镜效果"确保精准复刻
How to use seedance-storyboard on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add seedance-storyboard
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches seedance-storyboard from GitHub repository elementsix/elementsix-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate seedance-storyboard. Access the skill through slash commands (e.g., /seedance-storyboard) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★27 reviews- ★★★★★Kiara Gonzalez· Dec 12, 2024
seedance-storyboard has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Shikha Mishra· Dec 8, 2024
We added seedance-storyboard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Nov 27, 2024
Useful defaults in seedance-storyboard — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kiara Khan· Nov 3, 2024
Solid pick for teams standardizing on skills: seedance-storyboard is focused, and the summary matches what you get after install.
- ★★★★★Pratham Ware· Oct 18, 2024
Registry listing for seedance-storyboard matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Oshnikdeep· Sep 25, 2024
Solid pick for teams standardizing on skills: seedance-storyboard is focused, and the summary matches what you get after install.
- ★★★★★Benjamin Li· Sep 5, 2024
Registry listing for seedance-storyboard matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Isabella Chawla· Aug 24, 2024
Useful defaults in seedance-storyboard — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Ganesh Mohane· Aug 16, 2024
seedance-storyboard is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Benjamin Gill· Jul 15, 2024
We added seedance-storyboard from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 27