Back to Details

video-request-architect

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Video Request Architect

视频请求架构师

Follow shared release-shell rules in:
  • postplus-shared
    release-shell rules
Use this skill after the scene logic already exists.
This skill is for:
  • converting storyboard logic into full-video requests
  • separating provider-agnostic prompt architecture from provider fields
  • making short test iterations easy to diagnose
  • preserving reference boundaries and negative constraints
This skill is not for choosing the segment pattern from scratch.
遵循以下共享发布框架规则：
  • postplus-shared
    发布框架规则
请在场景逻辑已确定后使用此技能。
本技能适用于：
  • 将故事板逻辑转换为完整的视频请求
  • 将与服务商无关的提示架构和服务商专属字段分离
  • 简化短测试迭代的诊断流程
  • 保留参考边界和负面约束
本技能不适用于从零开始选择片段模式。

Core Rule

核心规则

Prompt architecture comes before provider syntax.
First write the request as a director's brief. Then map it into model-specific fields.
提示架构优先于服务商语法。
首先以导演简报的形式撰写请求， 然后将其映射到模型专属字段中。

Method

方法

Read 
references/request-architecture.md
.
If the task needs an explicit learn/do-not-copy block for references, also use 
reference-contract-builder
.
阅读 
references/request-architecture.md
。
如果任务需要针对参考内容明确的“可学习/不可复制”模块，也请使用 
reference-contract-builder
。

Default Workflow

默认工作流

1. Lock the experiment goal

1. 锁定实验目标

State what is being tested:
  • hook replication
  • camera realism
  • persona continuity
  • benefit proof
  • CTA readability
Do not write the request as if every generation is a full ad.
明确测试内容：
  • 钩子效果复刻
  • 镜头真实度
  • 角色一致性
  • 卖点验证
  • CTA可读性
不要将请求撰写成每一次生成都是完整广告的形式。

2. Write the provider-agnostic blocks

2. 撰写与服务商无关的模块

Use these blocks in order:
  1. role
  2. goal and hook logic
  3. reference contract
  4. output spec
  5. look and tone
  6. timecoded beat sheet
  7. camera
  8. sound intent
  9. product policy
按以下顺序使用这些模块：
  1. 角色定位
  2. 目标与钩子逻辑
  3. 参考协议
  4. 输出规范
  5. 视觉风格与基调
  6. 带时间码的节拍表
  7. 镜头设置
  8. 音效意图
  9. 产品政策

3. Print the request skeleton before the final request

3. 在最终请求前输出请求框架

text
Test goal:
Segment type:
Hook logic:
Viewer question:
Reference policy:
Duration:
Camera grammar:
Product policy:
Main risks:
This is a required checkpoint for debugging.
text
Test goal:
Segment type:
Hook logic:
Viewer question:
Reference policy:
Duration:
Camera grammar:
Product policy:
Main risks:
这是调试过程中必须的检查点。

4. Map to provider

4. 对接服务商

Only after the architecture is approved should you map to:
  • model name
  • duration field
  • aspect ratio field
  • reference media fields
  • optional resolution and quality fields
只有在架构获批后，才能将其映射到：
  • 模型名称
  • 时长字段
  • 宽高比字段
  • 参考媒体字段
  • 可选的分辨率和画质字段

Minimal-Variable Rule

最小变量规则

For first-pass testing, prefer the smallest sufficient variable set.
Examples:
  • short duration before full ad length
  • one reference type before many mixed references
  • no product images when testing hook rhythm only
Add more constraints only after you know what the first run missed.
首次测试时，优先使用最小的必要变量集。
示例：
  • 先测试短时长，再测试完整广告长度
  • 先测试单一参考类型，再测试多种混合参考
  • 仅测试钩子节奏时，不添加产品图片
只有在了解首次测试的遗漏点后，再添加更多约束。

Failure Mode

失败模式

Stop and say the request is under-specified if:
  • the hook logic is unclear
  • the reference policy is unclear
  • timecoded actions are missing
  • product policy is not explicit
Do not let the provider request silently invent the strategy.
如果出现以下情况，请停止并说明请求规格不明确：
  • 钩子逻辑不清晰
  • 参考协议不明确
  • 带时间码的动作缺失
  • 产品政策未明确说明
不要让服务商请求自行默认生成策略。