lifestyle-ad

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Lifestyle Ad

生活方式广告

Purpose

创作目标

Create state-led lifestyle ad concepts and shot scripts. The product should feel like part of a person's taste, rhythm, and composure, not a feature demo.
Use this skill to turn product facts, brand docs, reference ads, or rough feature ideas into:
  1. A
    Camera Grammar Plan
    .
  2. A shot-by-shot script.
  3. A user approval checkpoint.
  4. Direct handoff to the right production skill after approval.
打造以状态为主导的生活方式广告概念及分镜脚本。产品应融入人物的品味、节奏与从容气质,而非单纯展示功能。
借助该技能,可将产品信息、品牌文档、参考广告或初步功能创意转化为:
  1. Camera Grammar Plan
    (镜头语法方案)
  2. 分镜脚本
  3. 用户审核节点
  4. 审核通过后直接对接合适的制作技能

Workflow

工作流程

1. Ground The Brief

1. 明确需求基准

Read the smallest useful source context first:
  • brand, product, claim-boundary, persona, script, or reference files supplied by the user
  • prior ad-analysis files or benchmark notes when explicitly relevant
  • product reference, creator reference, audio reference, duration, model, or resolution preferences if provided
Lock these before writing:
  • product capability
  • desired visible user state
  • audience
  • proof available
  • claim boundaries
  • visual world
  • output format and duration target when supplied
优先阅读最具价值的核心上下文:
  • 用户提供的品牌、产品、声明边界、目标人群、脚本或参考文件
  • 明确相关的过往广告分析文件或基准笔记
  • 若有提供,需参考产品资料、创作者参考、音频参考、时长、模特或分辨率偏好
撰写前需锁定以下内容:
  • 产品功能
  • 期望呈现的用户状态
  • 目标受众
  • 可提供的佐证素材
  • 声明边界
  • 视觉风格
  • 若有指定,需明确输出格式及时长目标

2. Design The Camera Grammar

2. 设计镜头语法

Read
references/camera-grammar.md
.
Produce a
Camera Grammar Plan
with these fields:
  • status_to_make_visible
  • body_product_relationship
  • dominant_framing
  • motion_ratio
  • pressure_carrier
  • product_gesture
  • proof_style
  • sound_world
  • text_restraint
  • final_identity_line
Do not force a fixed shot order, scene type, phrase, product category, or ending formula. Choose grammar that fits the current brand and product.
阅读
references/camera-grammar.md
文件。
生成包含以下字段的
Camera Grammar Plan
  • status_to_make_visible
    (需呈现的状态)
  • body_product_relationship
    (人物与产品的关系)
  • dominant_framing
    (主导构图)
  • motion_ratio
    (镜头动效比例)
  • pressure_carrier
    (场景压力载体)
  • product_gesture
    (产品互动动作)
  • proof_style
    (佐证呈现风格)
  • sound_world
    (音效风格)
  • text_restraint
    (文字克制原则)
  • final_identity_line
    (最终品牌标识语)
无需强制固定镜头顺序、场景类型、话术、产品类别或结尾公式,选择契合当前品牌与产品的镜头语法即可。

3. Write The Shot Script

3. 撰写分镜脚本

Read
references/shot-script-rubric.md
.
Return a shot table with exactly these columns:
time | visual | framing/composition | action | sound | subtitle/text | purpose
Keep each row concrete enough for filming or video-generation prompting. Use restrained text and make the product action socially natural.
After the shot script, ask the user whether this script direction is OK.
阅读
references/shot-script-rubric.md
文件。
返回包含以下固定列的分镜表格:
时间 | 视觉画面 | 构图/取景 | 动作 | 音效 | 字幕/文字 | 创作目的
每一行内容需足够具体,可直接用于拍摄或视频生成提示。文字表达需克制,产品互动动作需符合社交场景的自然状态。
分镜脚本完成后,询问用户是否认可该脚本方向。

4. On Approval, Handoff Directly

4. 审核通过后直接对接

If the user approves the script, read
references/workflow-handoff.md
and immediately hand off to the right production runner.
Use
$video-batch-runner
by default: it turns the approved shot script into hosted video renders. This is the standard path when the user simply says to continue after approving the script.
Use
$image-batch-runner
first when the approved script needs still assets before video: persona images, product lifestyle stills, first-frame candidates, scene images, or light consistency edits. Those stills then feed the video renders.
Use
$workflow-creation
when the user wants the approved script to become a reusable production line instead of a one-off render batch: it builds a quotable, human-launched workflow on the PostPlus workflow platform from the locked script and references.
Pass the approved shot script, Camera Grammar Plan, brand constraints, product facts, claim boundaries, and any provided references as locked creative context. Do not output a separate production brief and do not ask a second "generate?" confirmation.
Let the downstream production runner handle missing product, creator, audio, model, resolution, route validation, and asset validation.
若用户认可脚本,阅读
references/workflow-handoff.md
文件,并立即对接合适的制作执行工具。
默认使用
$video-batch-runner
:它可将获批的分镜脚本转化为托管式视频渲染内容。当用户仅表示“继续”时,这是标准流程。
若获批脚本需先生成静态素材(如目标人群形象、产品生活场景静态图、首帧候选图、场景图或光影一致性调整图),则优先使用
$image-batch-runner
,生成的静态素材将用于后续视频渲染。
若用户希望将获批脚本转化为可复用的生产线而非一次性渲染任务,使用
$workflow-creation
:它会基于锁定的脚本及参考资料,在PostPlus工作流平台上构建一个可引用、人工触发的工作流。
需传递获批的分镜脚本、Camera Grammar Plan、品牌约束、产品信息、声明边界及所有提供的参考资料作为锁定的创意上下文。无需输出单独的制作简报,也无需二次确认“是否生成”。
后续的制作执行工具将负责处理缺失的产品、创作者、音频、模特、分辨率、路径验证及素材验证工作。

Quality Bar

质量标准

  • Start from human state and tension, not from a product announcement.
  • Let the viewer infer capability from composure, behavior, and light proof.
  • Use specific environment pressure instead of broad pain-point copy.
  • Make product gestures ordinary: touch, adjust, lift, place, glance, close, carry.
  • Treat UI, results, labels, and text as proof glimpses, not tutorials.
  • Prefer identity-style endings over hard CTAs unless the user asks for direct response.
  • 从人物状态与场景张力切入,而非直接发布产品信息
  • 让观众从人物的从容举止、行为及光影细节中推断产品功能
  • 使用具体的场景压力,而非宽泛的痛点文案
  • 产品互动动作需日常化:触摸、调整、拿起、放置、瞥视、闭合、携带
  • 将UI界面、使用结果、标签及文字视为佐证片段,而非教程内容
  • 优先选择品牌标识式结尾,除非用户要求直接行动指令(CTA)