pattern-router

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Pattern Router

模式路由（Pattern Router）

Follow shared release-shell rules in:

```
postplus-shared
```
release-shell rules

Use this skill at the start of prompt design.

This skill is for:

choosing the right segment pattern before writing prompts
mapping a brief into a concrete opening mechanism
reducing prompt drift when reference quality is uneven or absent
making later storyboard and video-request work more consistent

This skill is not for writing the final storyboard or provider request.

遵循以下共享发布框架规则：

```
postplus-shared
```
发布框架规则

在提示词设计的初始阶段使用本技能。

本技能适用于：

在撰写提示词前选择合适的片段模式
将brief转化为具体的开场机制
当参考资料质量参差不齐或缺失时，减少提示词偏差
让后续的故事板制作和视频需求工作更具一致性

本技能不适用于撰写最终的故事板或供应商需求。

Core Rule

核心规则

Do not begin from adjective stacks like "premium", "viral", or "cinematic".

Begin from:

segment type
viewer question
opening mechanism
product reveal timing

不要从诸如"premium"、"viral"或"cinematic"这类形容词堆砌开始。

应从以下几点入手：

片段类型
观众的疑问
开场机制
产品露出时机

Default Workflow

默认工作流程

1. Identify the segment type

1. 确定片段类型

Classify the request as one of:

```
hook
```
```
benefit
```
```
cta
```
```
creator
```
```
lifestyle
```
```
testimonial
```

If the user gives a custom segment, map it to the nearest working type and state the mapping.

将请求归类为以下类型之一：

```
hook
```
```
benefit
```
```
cta
```
```
creator
```
```
lifestyle
```
```
testimonial
```

如果用户提供自定义片段类型，将其映射到最接近的可用类型，并说明映射关系。

2. Pick the dominant pattern family

2. 选择主导模式家族

Read

references/pattern-families.md

Select one primary family, then optionally one support family.

Do not mix many families unless the timing clearly supports it.

阅读

references/pattern-families.md

。

选择一个主模式家族，然后可选择一个辅助模式家族。

除非时长明确允许，否则不要混合多个模式家族。

3. Lock the routing summary before writing prompts

3. 在撰写提示词前锁定路由摘要

Print a short routing block first:

text

Segment type:
Primary pattern:
Support pattern:
Viewer question:
Opening mechanism:
Product reveal rule:
Why this route fits:

This block is the handoff to

reference-decode

storyboard-grid-writer

, or

video-request-architect

先输出一个简短的路由块：

text

Segment type:
Primary pattern:
Support pattern:
Viewer question:
Opening mechanism:
Product reveal rule:
Why this route fits:

此块将对接给

reference-decode

、

storyboard-grid-writer

或

video-request-architect

技能。

4. Choose the next skill

4. 选择下一个技能

If references exist and need decoding, hand off to
```
reference-decode
```
If the target is a storyboard grid or beat sheet, hand off to
```
storyboard-grid-writer
```
If the target is a provider-ready request, hand off to
```
video-request-architect
```

如果存在需要解码的参考资料，对接给
```
reference-decode
```
如果目标是故事板网格或节拍表，对接给
```
storyboard-grid-writer
```
如果目标是可直接提交给供应商的需求，对接给
```
video-request-architect
```

Routing Rules

路由规则

```
hook
```
: optimize for stop-scroll and immediate legibility
```
benefit
```
: optimize for one visible proof mechanism
```
cta
```
: optimize for payoff plus next action, not a static end card
```
creator
```
: optimize for believable human delivery and social-native behavior
```
lifestyle
```
: optimize for desirability first, explanation second
```
testimonial
```
: optimize for proof plus human specificity

```
hook
```
：优化为能让用户停止滑动并快速理解内容
```
benefit
```
：优化为突出一个可见的证明机制
```
cta
```
：优化为突出回报及后续行动，而非静态结尾卡片
```
creator
```
：优化为可信的真人呈现及符合社交平台原生的行为
```
lifestyle
```
：优先优化吸引力，其次是解释说明
```
testimonial
```
：优化为突出证明及人的具体细节

Failure Mode

失败模式

Stop and say the routing is under-specified if the brief does not provide enough to answer at least:

what segment is being made
what question the viewer should ask
whether the product can appear in the opening
whether references exist

Do not let later skills guess the structure from vague taste words alone.

如果brief提供的信息不足以回答至少以下问题，需停止并说明路由信息不明确：

要制作的片段类型是什么
观众应该产生什么疑问
产品是否可以在开场出现
是否存在参考资料

不要让后续技能仅从模糊的风格词汇中猜测结构。