direct

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

stardust:direct

Resolve the user's freeform redesign intent into a complete target specification: project-root

PRODUCT.md

and

DESIGN.md

(impeccable format), a

DESIGN.json

sidecar with the divergence audit trail, and a

stardust/direction.md

with the full reasoning trace.

direct

produces the spec against which

prototype

and

migrate

operate. It never writes prototypes or migrates pages — those are downstream sub-commands.

将用户的自由格式重设计意图转化为完整的目标规范：项目根目录下的

PRODUCT.md

和

DESIGN.md

（格式严谨）、包含差异审计轨迹的

DESIGN.json

附属文件，以及记录完整推理轨迹的

stardust/direction.md

。

direct

生成的规范是

prototype

和

migrate

子命令的执行依据。它不会生成原型或迁移页面——这些是下游子命令的职责。

Inputs

输入参数

```
<phrase>
```
— optional positional. The user's freeform intent ("make it better", "more Linear less Salesforce", "feel more premium on a small screen"). If omitted, ask the user for one.
```
--re-direct
```
— optional. Replace the current direction with a new one. Triggers stale-flagging on prototyped / approved / migrated pages per
```
skills/stardust/reference/state-machine.md
```
. Default behaviour without the flag is additive: if a direction already exists, the agent asks before replacing.
```
--rebrand
```
— optional. Force rebrand mode (full divergence-seed roll, no Mode A inheritance). Without it the default is brand-faithful whenever the captured signal is
```
signal-strong
```
(§ Mode-detection precedence).
```
--prep
```
— optional. Run in migrate-prep mode: confirm the type catalog, finalize the module catalog, capture color reservations and brand-level metadata defaults, re-evaluate direction against the wider crawl. See § Prep mode below. Typically invoked via the
```
prepare-migration
```
orchestrator.
```
--add-variant <name>
```
— optional. Add a new variant against the existing direction without re-running intent reasoning or mode detection. Writes
```
DESIGN-<name>.{md,json}
```
at the project root and appends a per-variant section to
```
stardust/direction.md
```
; existing prototypes are not stale-flagged. See § Add-variant mode below.

```
<phrase>
```
— 可选位置参数。用户的自由格式意图（如“优化体验”“更贴近Linear风格而非Salesforce”“在小屏幕上更显高端”）。若省略，需询问用户补充。
```
--re-direct
```
— 可选参数。用新方向替换当前方向。根据
```
skills/stardust/reference/state-machine.md
```
，会对已生成原型、已批准或已迁移的页面标记为过时。未添加该标志时的默认行为是增量式：若已存在方向，会先询问用户是否替换。
```
--rebrand
```
— 可选参数。强制启用品牌重塑模式（完全生成差异种子，不继承Mode A）。未添加该标志时，默认在捕获到
```
signal-strong
```
信号时保持品牌一致性（参见模式检测优先级章节）。
```
--prep
```
— 可选参数。以迁移准备模式运行：确认类型目录、最终确定模块目录、记录颜色预留信息和品牌级元数据默认值、结合更广泛的爬取结果重新评估方向。详情见下文“准备模式”章节。通常通过
```
prepare-migration
```
编排器调用。
```
--add-variant <name>
```
— 可选参数。在现有方向基础上添加新变体，无需重新执行意图推理或模式检测。在项目根目录生成
```
DESIGN-<name>.{md,json}
```
文件，并在
```
stardust/direction.md
```
中添加对应变体的章节；已有的原型不会被标记为过时。详情见下文“添加变体模式”章节。

Setup

前置步骤

Run the master skill's setup (
```
skills/stardust/SKILL.md
```
§ Setup) — hard impeccable dep check, context loader, state read.
Verify
```
stardust/state.json
```
exists and contains at least one
```
extracted
```
page. If not, stop and recommend
```
$stardust extract <url>
```
first.
Read
```
stardust/current/_brand-extraction.json
```
. If absent, stop — extract did not complete brand-surface extraction; re-run extract. 3b. Cross-site brand inputs (when present).
```
state.json.designSource
```
(design-donor mode: Mode A pins bind to the donor's derived system) and
```
_brand-extraction.json.origins[]
```
(sibling-property evidence: widens what can be amplified, not what is pinned). Read
```
reference/cross-site-brand-inputs.md
```
for the pin and evidence rules; surface the active mode in the plan.
Read
```
stardust/direction.md
```
if present. If a prior direction exists and
```
--re-direct
```
was not passed, ask whether the user wants to refine the existing direction or replace it.
Validate provenance (prep mode only). When
```
--prep
```
is active, run the provenance validation per
```
reference/prep-mode.md
```
before typing or module detection.
Classify the captured brand signal. Read
```
_brand-extraction.json
```
and stamp one of:
- ```
signal-strong
```
  — palette has ≥ 3 distinct colors (after near-duplicate clustering and excluding pure black/white if they are the only entries) AND at least one captured type family is named in
```
type.headingFamily.name
```
  or
```
type.bodyFamily.name
```
  . This is the common case for any extracted commercial site.
- ```
signal-thin
```
  — palette has 2 colors OR no captured type family OR
```
type.scaleAudit.kind === "ad-hoc"
```
  with fewer than 3 distinct heading sizes. The brand exists but cannot fully anchor a refresh.
- ```
signal-absent
```
  — palette has 1 color or 0, or
```
_brand-extraction.json._provenance.notes
```
  flags the extraction as failed / login-walled / iframe-dominated. The classification feeds the Mode-detection precedence in Phase 2. Surface the classification in the plan when it would change the default mode.

运行主技能的设置流程（
```
skills/stardust/SKILL.md
```
的“设置”章节）——严格的依赖检查、上下文加载、状态读取。
验证
```
stardust/state.json
```
存在且至少包含一个
```
extracted
```
状态的页面。若不存在，停止操作并建议先执行
```
$stardust extract <url>
```
。
读取
```
stardust/current/_brand-extraction.json
```
。若该文件不存在，停止操作——提取流程未完成品牌表层信息提取；需重新执行extract。 3b. 跨站点品牌输入（若存在）。
```
state.json.designSource
```
（设计捐赠模式：Mode A绑定到捐赠方的衍生系统）和
```
_brand-extraction.json.origins[]
```
（兄弟属性证据：扩展可强化的内容范围，但不改变绑定规则）。阅读
```
reference/cross-site-brand-inputs.md
```
了解绑定和证据规则，并在计划中展示当前激活的模式。
若存在
```
stardust/direction.md
```
则读取该文件。若已存在历史方向且未传入
```
--re-direct
```
参数，需询问用户是优化现有方向还是替换它。
验证来源（仅准备模式）。当启用
```
--prep
```
时，在类型或模块检测前，根据
```
reference/prep-mode.md
```
执行来源验证。
分类捕获到的品牌信号。读取
```
_brand-extraction.json
```
并标记为以下类型之一：
- ```
signal-strong
```
  — 配色方案包含≥3种不同颜色（经过近重复聚类后，且排除仅有的纯黑/纯白）且至少有一种捕获到的字体族在
```
type.headingFamily.name
```
  或
```
type.bodyFamily.name
```
  中命名。这是所有已提取的商业网站的常见情况。
- ```
signal-thin
```
  — 配色方案仅含2种颜色，或未捕获到字体族，或
```
type.scaleAudit.kind === "ad-hoc"
```
  且标题尺寸少于3种。品牌存在，但无法完全支撑一次视觉更新。
- ```
signal-absent
```
  — 配色方案仅含1种或0种颜色，或
```
_brand-extraction.json._provenance.notes
```
  标记提取失败/需登录/被iframe主导。分类结果会影响第二阶段的模式检测优先级。当分类结果会改变默认模式时，需在计划中展示。

Procedure

执行流程

Phase 1 — Reasoning

第一阶段 — 意图推理

Run the full intent-reasoning procedure from

skills/stardust/reference/intent-reasoning.md

. Steps 1-6: restate the phrase in dimensional vocabulary, identify movement, identify gaps, ask at most two clarifying questions, map to an impeccable command sequence, show the plan to the user.

Worked examples in

skills/stardust/reference/intent-examples.md

calibrate the style. Hard ceiling on questions: two per turn, no exceptions.

Hands-off mode (per

skills/stardust/SKILL.md

§ Hands-off mode,

state.json.handsOff: true

): ask nothing and wait for nothing. Derive every answer the questions would have collected from the captured evidence — density and ia-fidelity from their documented defaults and trigger conditions, audience and register from the captured surface — and record each as a named assumption in

direction.md

§ Movements (e.g.

density: balanced (hands-off default — multi-audience floor fired)

). The plan is still written; execution proceeds without the confirmation gate. Question budgets and gates below that say "ask the user" resolve the same way: derive, stamp the assumption, proceed.

执行

skills/stardust/reference/intent-reasoning.md

中的完整意图推理流程。步骤1-6：用维度词汇重述用户意图、识别调整方向、识别缺口、最多提出两个澄清问题、映射为严谨的命令序列、向用户展示计划。

skills/stardust/reference/intent-examples.md

中的示例可作为风格校准参考。问题数量严格限制为每次最多两个，无例外。

自动执行模式（根据

skills/stardust/SKILL.md

的“自动执行模式”章节，

state.json.handsOff: true

）：不询问任何问题，也不等待用户回复。从捕获的证据中推导所有原本需要通过问题收集的答案——密度和IA保真度从文档化的默认值和触发条件获取，受众和风格从捕获的表层信息获取——并将每个推导结果作为命名假设记录在

direction.md

的“调整方向”章节（例如

density: balanced (自动执行默认值——多受众触发条件生效)

）。仍需生成计划；执行流程无需确认环节。所有要求“询问用户”的问题都按此方式处理：推导答案、标记假设、继续执行。

Density tuning (one-shot, only when unmoved)

密度调优（仅当未指定时执行一次）

When the user's phrase does not move the

density

axis (per

reference/intent-dimensions.md

§ 4), and the resolved register is

brand

, ask one short follow-up — count it within the two-question ceiling:

Density tuning — (a) airy (NYT-Opinion-tier breathing, ~96px section padding), (b) balanced (calm but compact, ~64–72px), (c) packed (data-dense, ~40–48px). Default for brand-register sites with multi-audience IA is (b) balanced; pick (a) only when the page is editorial-led with deep per-section density.

If the user answers, stamp the chosen tier in

direction.md

§ Movements as

density: <tier>

. If unanswered, default to balanced (not airy) for brand register and stamp

density: balanced (default)

Skip this question entirely when:

The user's phrase already moved
```
density
```
(any of "make it denser", "more breathing room", "compact", "tight", "spacious" count as movement).
The register is
```
product
```
(default
```
packed
```
per § 4).
The register is
```
ambiguous
```
and resolving it earlier in the reasoning is the higher-value question — defer density to the next turn rather than burning a question slot.

Phase 4 reads the stamped tier to set

spacing.sectionPadding

; it never re-asks.

当用户的意图未涉及

density

维度调整（参考

reference/intent-dimensions.md

第4节），且确定的风格为

brand

时，可提出一个简短的后续问题——计入最多两个问题的限额：

密度调优 — (a) 宽松（纽约时报评论级留白，段落内边距约96px），(b) 均衡（简洁紧凑，约64–72px），(c) 紧凑（数据密集，约40–48px）。面向多受众IA的品牌风格网站默认选择**(b) 均衡**；仅当页面以编辑内容为主且段落内密度较高时选择(a)。

若用户回复，将所选层级标记在

direction.md

的“调整方向”章节中，格式为

density: <层级>

。若未回复，品牌风格默认选择均衡，并标记为

density: balanced (默认值)

。

以下情况跳过此问题：

用户的意图已涉及
```
density
```
调整（任何类似“更紧凑”“增加留白”“密集”“宽松”的表述均视为调整）。
风格为
```
product
```
（默认选择
```
紧凑
```
，参考第4节）。
风格模糊，且优先需要解决风格识别问题——将密度调优推迟到下一回合，避免占用问题名额。

第四阶段会读取标记的层级来设置

spacing.sectionPadding

；不会再次询问。

IA-fidelity tuning (one-shot, only when unmoved)

IA保真度调优（仅当未指定时执行一次）

When the user's phrase does not auto-pin

ia-fidelity

(per

reference/intent-dimensions.md

§ 9 — i.e. none of "verbatim", "same IA", "keep the structure", "swap the surface", "don't rethink the IA" and none of "reimagine", "rethink", "deeper redesign", "what if" appear), ask one short follow-up — count it within the two-question ceiling:

IA fidelity — (a) verbatim (same section sequence, same content beats; variants explore surface only: color, type, density, motion), or (b) reimagined (variants may demote / promote / drop sections, move IA priorities, take "what if" positions on the spine of the page). Default (b) for the typical refresh; pick (a) when the customer asked to keep their site structurally identical and only swap the surface.

If the user answers, stamp the chosen tier in

direction.md

§ Movements as

ia-fidelity: <tier>

. If unanswered, default to reimagined and stamp

ia-fidelity: reimagined (default)

Skip this question entirely when:

The user's phrase already auto-pinned the axis (any trigger phrase in § 9 — "same IA, swap the surface" → verbatim; "what if we rethought the home page" → reimagined).
An existing
```
direction.md
```
is being refined (the active tier holds unless the user explicitly re-pins).

Phase 4 stamps the tier into

iaPriorities[].mutability

; downstream

prototype

reads it.

Pair this question with the density-tuning question when both are unmoved — "two things to pin before we resolve: (1) density …, (2) IA fidelity …" — to stay within the two-question ceiling. If resolving register (brand vs product) is also outstanding, prioritise register first; defer one of density / ia-fidelity to the next turn.

Wait for the user's confirmation (

"go"

, or a correction to the plan) before moving on.

当用户的意图未自动锁定

ia-fidelity

（参考

reference/intent-dimensions.md

第9节——即未出现“完全一致”“保持相同IA”“保留结构”“仅替换表层”“不重新设计IA”，也未出现“重新构想”“重新思考”深度重设计“假设”等表述）时，可提出一个简短的后续问题——计入最多两个问题的限额：

IA保真度 — (a) 完全一致（保持相同的章节顺序、内容模块；变体仅探索表层：颜色、字体、密度、动效），或(b) 重新构想（变体可降级/升级/移除章节、调整IA优先级、对页面核心结构提出“假设”式调整）。典型更新默认选择(b)；当客户要求保持网站结构完全一致仅替换表层时选择(a)。

若用户回复，将所选层级标记在

direction.md

的“调整方向”章节中，格式为

ia-fidelity: <层级>

。若未回复，默认选择重新构想，并标记为

ia-fidelity: reimagined (默认值)

。

以下情况跳过此问题：

用户的意图已自动锁定该维度（第9节中的任何触发表述——如“保持相同IA，仅替换表层”→完全一致；“如果我们重新设计首页会怎样”→重新构想）。
正在优化已有的
```
direction.md
```
（现有层级保持不变，除非用户明确重新锁定）。

第四阶段会将层级标记到

iaPriorities[].mutability

；下游的

prototype

命令会读取该值。

当密度和IA保真度均未指定时，可将两个问题合并提出——“有两个事项需要确认：(1) 密度…，(2) IA保真度…”——以控制在最多两个问题的限额内。若同时需要解决风格识别（品牌vs产品）问题，优先处理风格识别；将密度或IA保真度的问题推迟到下一回合。

等待用户确认（回复“开始”或修正计划）后再进入下一阶段。

Phase 2 — Resolve the divergence inputs

第二阶段 — 确定差异输入参数

Once the plan is confirmed, resolve the divergence-toolkit inputs from

skills/stardust/reference/divergence-toolkit.md

. Before rolling the seed, run the mode-detection precedence below to decide whether the seed needs rolling at all.

计划确认后，根据

skills/stardust/reference/divergence-toolkit.md

确定差异工具包的输入参数。在生成种子前，先执行以下模式检测优先级判断，确定是否需要生成种子。

Mode-detection precedence (run first)

模式检测优先级（先执行）

The default mode for

direct

is determined by whether an extracted brand surface exists with usable signal — not by the user's freeform phrase alone. Ambiguous refresh phrases ("make it modern", "stunning new version", "design fatigue cure") are migration-shaped asks, not rebrand triggers. The precedence is asymmetric on purpose: the safer mode (Mode A — brand-faithful) catches ambiguous phrases; the riskier rebrand mode requires the user to name it.

Site migration / refresh — DEFAULT. When the captured brand signal stamped in § Setup step 6 is
```
signal-strong
```
, Mode A is active by default. The user's phrase moves expressive, distinctiveness, tone, and density axes inside Mode A — but palette and type are pinned to the captured surface, and the image-reuse contract (below) holds. Signature preservation also holds: a captured signature hero medium (background video / canvas / Lottie / scroll-motion, elevated as
```
_brand-extraction.json#voice.heroMedium
```
) or a site-wide motif is reproduced, not flattened — per
```
skills/stardust/reference/ intent-dimensions.md
```
§ 8b, and exempt from the
```
surprise
```
budget. Surface in the plan: "Brand-faithful mode active — palette and type pinned to the captured brand surface. Pass
--rebrand
to override."
Rebrand — explicit opt-in. Mode A is overridden when any of the following triggers fire:
- The user's phrase contains an explicit rebrand signal: any of
```
rebrand
```
  ,
```
new brand
```
  ,
```
clean slate
```
  ,
```
start over
```
  ,
```
from scratch
```
  ,
```
replace the brand
```
  ,
```
not brand-faithful
```
  ,
```
editorial reimagination
```
  ,
```
completely new
```
  ,
```
redo the brand
```
  .
- The
```
--rebrand
```
  flag is passed.
- Captured signal is
```
signal-absent
```
  (no usable inheritance). Surface this case as an automatic switch with reason; the user can correct.
In rebrand mode, run the standard divergence-seed roll per "Default mode (no constraints)" below. Surface in the plan: "Rebrand mode active — full divergence-seed roll. Mode A bypassed because <reason>."
Brand-faithful + targeted exploration. When the user requests N variants (e.g. "3 variants", "4 directions") and Mode A is active, the variant role contract in
```
reference/multi-variant.md
```
applies (trigger: § Phase 2.6). Variant A is locked to strict Mode A (palette and type pinned, IA preserved, every improvements-list item applied). Variants B+ may amplify one captured trait (a motif, a photo treatment, an IA priority the current site underplays) but cannot:
- introduce a font outside the captured surface,
- introduce a color outside the captured palette,
- shift the register from PRODUCT.md.
Signal-thin fallback. When captured signal is
```
signal-thin
```
, Mode A activates but warns: "Captured brand surface is thin — {reason}. Variants will inherit what is available; some dimensions will need to be filled by the divergence toolkit." The user may either re-run extract with a wider crawl (
```
--cap 25
```
) or proceed with reduced fidelity.

After mode-detection completes, run the existing mode definitions below (Mode A procedure, Mode B anchor-reference precedence, Mode C ground-family override) as applicable.

direct

的默认模式由是否存在可提取的、带有可用信号的品牌表层信息决定——而非仅由用户的自由格式意图决定。模糊的更新表述（如“现代化”“全新惊艳版本”“解决审美疲劳”）属于迁移类需求，而非品牌重塑触发条件。优先级设置故意不对称：更安全的模式（Mode A——保持品牌一致性）会覆盖模糊表述；风险更高的品牌重塑模式需要用户明确指定。

网站迁移/更新 — 默认模式。当第6步设置阶段标记的品牌信号为
```
signal-strong
```
时，默认激活Mode A。用户的意图在Mode A内调整
```
expressive
```
（表现力）、
```
distinctiveness
```
（独特性）、
```
tone
```
（风格）和
```
density
```
（密度）维度——但配色方案和字体绑定到捕获的表层信息，且需遵循以下图片复用约定。品牌特征保留规则同样生效：捕获到的标志性 hero 媒介（背景视频/画布/Lottie/滚动动效，标记为
```
_brand-extraction.json#voice.heroMedium
```
）或全站主题元素需保留，而非扁平化——参考
```
skills/stardust/reference/intent-dimensions.md
```
第8b节，且不受“惊喜”预算限制。需在计划中展示： “已激活品牌一致性模式——配色方案和字体绑定到捕获的品牌表层信息。传入
--rebrand
参数可覆盖此模式。”
品牌重塑 — 显式启用。当以下任一触发条件满足时，Mode A会被覆盖：
- 用户的意图包含明确的品牌重塑信号：任何类似
```
rebrand
```
  、
```
new brand
```
  、
```
clean slate
```
  、
```
start over
```
  、
```
from scratch
```
  、
```
replace the brand
```
  、
```
not brand-faithful
```
  、
```
editorial reimagination
```
  、
```
completely new
```
  、
```
redo the brand
```
  的表述。
- 传入了
```
--rebrand
```
  参数。
- 捕获到的信号为
```
signal-absent
```
  （无可用继承信息）。需在此情况下展示自动切换的原因；用户可修正。
在品牌重塑模式下，按照下文“默认模式（无约束）”执行标准的差异种子生成流程。需在计划中展示： “已激活品牌重塑模式——完全生成差异种子。因<reason>跳过Mode A。”
品牌一致性+定向探索。当用户要求生成N个变体（如“3个变体”“4个方向”）且Mode A激活时，需遵循
```
reference/multi-variant.md
```
中的变体角色约定（触发条件：第二阶段第6节）。变体A锁定为严格Mode A（配色和字体绑定、IA保留、应用所有改进列表项）。变体B及以后可强化一个已捕获的特征（主题、图片处理方式、现有网站未充分利用的IA优先级），但不得：
- 引入捕获表层之外的字体，
- 引入捕获配色方案之外的颜色，
- 改变PRODUCT.md中定义的风格。
弱信号 fallback。当捕获到的信号为
```
signal-thin
```
时，激活Mode A但给出警告：*“捕获的品牌表层信息不足——{原因}。变体将继承可用信息；部分维度需通过差异工具包补充。”*用户可选择扩大爬取范围重新执行extract（
```
--cap 25
```
），或继续执行但降低保真度。

模式检测完成后，根据适用情况执行现有的模式定义（Mode A流程、Mode B锚点参考优先级、Mode C品牌一致性底色覆盖规则）。

Mode A — Brand-faithful mode

Mode A — 品牌一致性模式

Triggered automatically when the captured brand signal is

signal-strong

and no rebrand-mode override fired (see § Mode-detection precedence above), OR when the user pinned both type and palette (via explicit phrase: "keep typography and palette", "preserve the existing brand", "brand-faithful redesign"; or via constraints listing both as anchors).

In this mode, direct does not roll the type or palette dimensions of the seed — they are already locked.

The mode procedure:

Record

font_deck.name = "brand-inherited"

and

font_deck.picked_by = "user-constraint"

. Do not invoke

reference/palette-picker.md

Record
```
palette.source = "inherited from _brand-extraction.json"
```
and
```
palette.picked_by = "user-constraint"
```
. Apply role-renaming per toolkit § 4 if the inherited names violate the brand-native rule (this is still useful — role renaming is presentational, not a divergence choice).
Still roll the seed for the non-locked dimensions (decade, register, ground-family-as-applicable per Mode C below). These dimensions still drive divergence — the visual register and the era can shift even when type and palette are pinned.
Auto-emit the
```
brand_faithful_inversions[]
```
block in
```
extensions.divergence
```
per
```
reference/direction-format.md
```
§ Brand-faithful inversions. The list is mostly mechanical (see § Brand-faithful inversions in direction-format.md for the canonical patterns).

Surface in the user report which dimensions had teeth and which were inert:

Divergence (brand-faithful mode):
  decade           ✓ rolled    → 2025-now
  craft            ✓ rolled    → Riso print
  register         ✓ rolled    → Memoir-adjacent
  ground-family    inherited   → stark-white (brand-native)
  font deck        inherited   → existing site stack
  palette          inherited   → existing 5-color set

Image-reuse contract. Captured images are reused via their public URLs (or the local copies in
```
stardust/current/assets/media/
```
written by extract Phase 2) at the same semantic position as on the source site. Hero stays hero. Story-tile portrait stays story-tile portrait. Program-card image stays program-card image. Background-motif image stays background motif.
This is part of brand-faithful inheritance: swapping a captured portrait for a placeholder, or demoting the hero photo to a thumbnail, erases the brand's most load-bearing trust signal.

The only legitimate ways to deviate from semantic position-preservation under Mode A:
- The captured image is broken (404, blocked by
```
referrer-policy
```
  , CORS-walled, or recorded with
```
localPath: null
```
  and a
```
downloadError
```
  ).
- The brand-review surfaced the image as a tension (e.g.
```
T-stock-photography
```
  when added — flagging the captured image as obviously templated stock that the brand team would replace anyway).
- The improvements list (Phase 2.5) explicitly notes a crop or positioning fix for that image — in which case the same image is reused at the corrected crop or position.
Synthesised placeholders are forbidden under Mode A. When a captured image cannot be reused, the prototype shape brief declares the gap explicitly and the rendered prototype shows a placeholder-with-signature element so reviewers see the gap rather than a fabricated photo.

The user can correct the mode at the plan-confirmation gate (e.g. "actually let me move the palette" or "actually rebrand it") before it locks.

当捕获到的品牌信号为

signal-strong

且未触发品牌重塑模式覆盖（参考上文模式检测优先级），或用户明确锁定字体和配色方案（通过明确表述：“保留字体和配色”“保留现有品牌”“品牌一致性重设计”；或通过约束列表同时指定两者为锚点）时，自动触发此模式。

在此模式下，direct不会生成种子的字体或配色维度——它们已被锁定。

模式执行流程：

记录

font_deck.name = "brand-inherited"

和

font_deck.picked_by = "user-constraint"

。无需调用

reference/palette-picker.md

。

记录
```
palette.source = "inherited from _brand-extraction.json"
```
和
```
palette.picked_by = "user-constraint"
```
。若继承的名称违反品牌原生规则，根据工具包第4节重命名角色（这仍有意义——角色重命名仅用于展示，而非差异选择）。
仍需生成种子的未锁定维度（年代、风格、根据Mode C适用的底色家族）。这些维度仍会驱动差异——即使字体和配色被锁定，视觉风格和年代仍可调整。
根据
```
reference/direction-format.md
```
的“品牌一致性反转”章节，在
```
extensions.divergence
```
中自动生成
```
brand_faithful_inversions[]
```
块。列表内容大多为机械生成（参考direction-format.md中的“品牌一致性反转”章节获取标准模式）。

在用户报告中展示哪些维度生效、哪些维度无效：

差异（品牌一致性模式）：
  decade           ✓ 已生成    → 2025-至今
  craft            ✓ 已生成    →  Risograph印刷风格
  register         ✓ 已生成    →  接近回忆录风格
  ground-family    继承自品牌   →  stark-white（品牌原生）
  font deck        继承自品牌   →  现有网站字体栈
  palette          继承自品牌   →  现有5色配色方案

图片复用约定。捕获的图片通过其公共URL（或extract第二阶段生成的
```
stardust/current/assets/media/
```
本地副本）复用，且保持与源网站相同的语义位置。Hero图仍作为Hero图。故事瓷砖肖像仍作为故事瓷砖肖像。程序卡片图片仍作为程序卡片图片。背景主题图片仍作为背景主题。
这是品牌一致性继承的一部分：将捕获的肖像替换为占位符，或把Hero图降级为缩略图，会抹去品牌最核心的信任信号。

在Mode A下，偏离语义位置保留规则的唯一合法情况：
- 捕获的图片已损坏（404、被
```
referrer-policy
```
  阻止、跨域问题，或记录为
```
localPath: null
```
  且带有
```
downloadError
```
  ）。
- 品牌评审标记该图片为问题点（例如添加时标记为
```
T-stock-photography
```
  ——表示捕获的图片为明显的模板化素材，品牌团队会替换它）。
- 改进列表（第二阶段第5节）明确指出该图片需要裁剪或调整位置——此时复用同一张图片，但应用修正后的裁剪或位置。
Mode A下禁止使用合成占位符。当捕获的图片无法复用时，原型形状 brief 会明确声明缺口，渲染的原型会展示带有特征的占位符元素，以便评审人员看到缺口而非伪造的图片。

用户可在计划确认环节修正模式（例如“实际上我想调整配色”或“实际上要进行品牌重塑”），之后模式将锁定。

Mode A+ — Brand-adjacent refinement (bounded, evidence-gated)

Mode A+ — 品牌相关优化（有限制、基于证据）

The middle tier between Mode A's hard pins and

--rebrand

: when the improvements list (Phase 2.5) names a captured type or color weakness with evidence, bounded same-classification upgrades are permitted — each audited in

extensions.divergence. brand_adjacent_refinements[]

, never active by default. Read

reference/mode-a-plus.md

before applying any refinement.

介于Mode A的严格绑定和

--rebrand

之间的中间层级：当改进列表（第二阶段第5节）指出已捕获的字体或颜色存在缺陷且有证据支持时，允许进行有限的同类别升级——每个升级需记录在

extensions.divergence.brand_adjacent_refinements[]

中，默认不生效。应用任何优化前需阅读

reference/mode-a-plus.md

。

Mode B — Anchor-reference precedence

Mode B — 锚点参考优先级

When the user provides anchor references (Q1/Q2 answers like "Pentagram nonprofits, This American Life, NYT Opinion longform"), those references already imply seed dimensions (Pentagram → decade

2025-now

editorial; This American Life → register

Memoir

-adjacent). Do not roll dimensions the references already imply.

Agent-sourced anchors (default when the user provides none). Mode B no longer waits for the user to name references: run the reference-research procedure (

skills/stardust/reference/reference-research.md

) to source 3–5 real-world anchors matched to the brand's category, register, and the resolved direction movement. Researched anchors carry the same implied-dimension weight as user-provided ones and are recorded as

picked_by: "reasoned: <anchor>"

with the full citation in

extensions.divergence.references_used[]

. User-provided references always outrank researched ones on conflict. When research is unavailable (ladder exhausted per reference-research.md § 1), Mode B degrades to the deterministic roll for the un-implied dimensions.

Precedence rule:

If anchor references are present, extract their implied dimensions:
- Decade from era of the references (Pentagram → 2025-now; vintage Penguin → 1960s).
- Craft from medium of the references (TAL → audio editorial ≠ a craft per se, but Bandcamp → web-print hybrid; Riso-print anthology → Riso).
- Register from cultural reference set (Memoir, Tabloid, Catalogue, etc.).
- Ground-family from typical ground of those references (NYT Opinion → cream/parchment; Pentagram nonprofit → stark-white or monochrome-tint).

Mark each implied dimension as

picked_by = "anchor-reference: <ref-name>"

Roll the seed only for un-implied dimensions.
Record the anchor → dimension mapping in
```
extensions.divergence.seed.anchors[]
```
.

Mode B can compose with Mode A: anchor-references narrow the seed, brand-faithful constraints lock type/palette, the remaining roll is whatever the anchors didn't already imply.

当用户提供锚点参考（如Q1/Q2回复“Pentagram非营利组织、This American Life、纽约时报评论长文”）时，这些参考已隐含种子维度（Pentagram→年代

2025-至今

编辑风格；This American Life→风格接近

Memoir

）。无需生成参考已隐含的维度。

Agent自动获取锚点（用户未提供时默认执行）。Mode B不再等待用户指定参考：执行参考研究流程（

skills/stardust/reference/reference-research.md

），根据品牌类别、风格和已确定的方向调整，获取3–5个真实世界锚点。研究得到的锚点与用户提供的锚点具有相同的隐含维度权重，记录为

picked_by: "reasoned: <anchor>"

，并在

extensions.divergence.references_used[]

中记录完整引用。用户提供的参考在冲突时优先级高于研究得到的参考。当无法获取研究结果（参考reference-research.md第1节的层级耗尽）时，Mode B会对未隐含的维度执行确定性生成。

优先级规则：

若存在锚点参考，提取其隐含的维度：
- 年代：参考的时代（Pentagram→2025-至今；复古Penguin→1960年代）。
- 工艺风格：参考的媒介（TAL→音频编辑本身不属于工艺风格，但Bandcamp→网页-印刷混合风格；Risograph印刷选集→Risograph风格）。
- 风格：文化参考集（回忆录、小报、目录等）。
- 底色家族：参考的典型底色（纽约时报评论→米黄色/羊皮纸色；Pentagram非营利组织→纯白色或单色色调）。

将每个隐含维度标记为

picked_by = "anchor-reference: <ref-name>"

。

仅为未隐含的维度生成种子。
在
```
extensions.divergence.seed.anchors[]
```
中记录锚点→维度的映射关系。

Mode B可与Mode A组合：锚点参考缩小种子范围，品牌一致性约束锁定字体/配色，剩余生成部分为锚点未隐含的维度。

Mode C — Brand-faithful ground-family override

Mode C — 品牌一致性底色覆盖规则

When Mode A is active and the seed's

ground_family

roll disagrees with the brand's existing ground (e.g. seed rolled

monochrome-tint

but the brand's captured background is

#ffffff

stark-white), the brand's ground wins. The seed roll is not discarded — it informs the alt-section surface instead (per

divergence-toolkit.md

§ 4 Color roles). Record the override in

extensions.divergence.seed.ground_family.override

with one of three reasons:

```
brand-faithful
```
— Mode A active and brand has a fixed ground.
```
print-paper
```
— manual override for print/paper categories (existing toolkit rule).
```
direction-driven
```
— seed wins (default; no override).

The three reasons are mutually exclusive; surface the chosen one in the user report.

当Mode A激活且种子生成的

ground_family

与品牌现有底色不一致（例如种子生成

monochrome-tint

但品牌捕获的背景为

#ffffff

纯白色）时，品牌现有底色优先。种子生成结果不会被丢弃——而是用于替代章节表层（参考

divergence-toolkit.md

第4节颜色角色）。在

extensions.divergence.seed.ground_family.override

中记录覆盖原因，原因分为三种：

```
brand-faithful
```
— Mode A激活且品牌有固定底色。
```
print-paper
```
— 针对印刷/纸张类别的手动覆盖（现有工具包规则）。
```
direction-driven
```
— 种子生成结果优先（默认；无覆盖）。

三个原因互斥；需在用户报告中展示所选原因。

Default mode (no constraints)

默认模式（无约束）

When neither Mode A nor Mode B applies (rebrand or thin-signal runs with no user anchors), the procedure is research-first, roll as fallback:

Reference research first. Run
```
skills/stardust/reference/reference-research.md
```
to source anchors for the brand's category and the resolved direction, and derive the dimensions they imply (
```
picked_by: "reasoned: <basis>"
```
). This is Mode B's machinery applied to agent-sourced anchors — see § Mode B above.
Seed as fallback + tiebreaker. Roll the 4-dimension seed (decade × craft × register × ground-family) per § 2 of the toolkit only for dimensions research left un-implied, or entirely when research is unavailable. The roll also remains available as a deliberate convergence-breaker when the self-audit catches the model reproducing its defaults despite research. Record
```
picked_by
```
per dimension.
Font deck. Pick from the 10 named decks per § 3, letting the researched anchors inform the pick the same way a seed implication would (e.g. an editorial-serif anchor set →
```
serif-luxury
```
). When neither research nor seed implies a deck, pick deterministically from the hash.
Palette. If the resolved direction moves the color-energy axis or names the existing palette as part of the problem: derive a full role-ramped palette (text, grounds, borders, accents, states) from the primary researched anchor or a library candidate — the library (
```
skills/direct/reference/palette-picker.md
```
) is an anchor bank, not a closed menu; the model designs the ramp and validates every text-on-ground pair for WCAG AA before it lands in tokens (deterministic where it matters — math — not where it hurts — taste). Record the derivation basis in
```
extensions.divergence.palette_source
```
. Otherwise inherit the existing palette from
```
stardust/current/_brand-extraction.json
```
, applying role-renaming per toolkit § 4 if the inherited names violate the brand-native rule.

当Mode A和Mode B均不适用（品牌重塑或弱信号运行且无用户锚点）时，执行先研究、后生成的流程：

优先参考研究。执行
```
skills/stardust/reference/reference-research.md
```
，根据品牌类别和已确定的方向获取锚点，并推导其隐含的维度（
```
picked_by: "reasoned: <basis>"
```
）。这是Mode B机制应用于Agent自动获取的锚点——参考上文Mode B章节。
种子生成作为 fallback + 平局决胜。仅为研究未隐含的维度，或在无法获取研究结果时为所有维度，根据工具包第2节生成4维度种子（年代×工艺风格×风格×底色家族）。当自我审核发现模型重复使用默认值而非参考研究结果时，生成流程仍可作为刻意打破趋同的手段。记录每个维度的
```
picked_by
```
。
字体栈。从第3节的10个命名字体栈中选择，让研究得到的锚点像种子隐含维度一样影响选择（例如编辑衬线锚点集→
```
serif-luxury
```
）。当研究和种子均未隐含字体栈时，根据哈希值确定性选择。
配色方案。若已确定的方向调整了颜色活力维度，或指出现有配色方案存在问题：从主要研究锚点或库候选中推导完整的角色分层配色方案（文本、底色、边框、强调色、状态色）——库（
```
skills/direct/reference/palette-picker.md
```
）是锚点库，而非封闭菜单；模型设计分层，并在写入令牌前验证所有文本-底色组合符合WCAG AA标准（关键部分为确定性数学计算，而非主观审美）。在
```
extensions.divergence.palette_source
```
中记录推导依据。否则继承
```
stardust/current/_brand-extraction.json
```
中的现有配色方案，若继承的名称违反品牌原生规则，根据工具包第4节重命名角色。

Always run

必执行步骤

Anti-toolbox audit. Regardless of mode, run the self-audit (toolkit § 1 Enforcement + Self-audit) on the resolved direction. Each anti-toolbox hit needs a brand-specific justification or it is removed.

Record every resolution in

DESIGN.json.extensions.divergence

per the v2 storage shape at the bottom of

divergence-toolkit.md

反工具箱审核。无论何种模式，都需对已确定的方向执行自我审核（工具包第1节“强制执行+自我审核”）。每个反工具箱问题都需要品牌特定的理由，否则需移除相关调整。

根据

divergence-toolkit.md

底部的v2存储格式，将所有决策记录在

DESIGN.json.extensions.divergence

中。

Phase 2.5 — Improvements list (Mode A only)

第二阶段第5节 — 改进列表（仅Mode A）

Before any variant is rendered downstream, write

stardust/prototypes/<slug>-improvements.md

listing 3–5 specific weaknesses observed in the captured site. It is the brief variant A renders against: not prescriptive (no visual targets), but descriptive of the gap between the existing site and a competent 2026 execution of the same brand. Variants B+ honor the list as a floor (they may go further but not contradict it).

Skip this phase when the resolved mode is rebrand — the improvements list assumes brand-faithful inheritance, and a rebrand replaces the site rather than fixing it.

Audit reuse. When

stardust/audit/<domain-slug>/audit.json

exists for this origin (written by

stardust:audit

), consume its design findings as candidate improvements instead of re-deriving from scratch — carry the finding IDs into each item's evidence citation. The specificity bar below still applies to every carried item.

在下游生成任何变体前，编写

stardust/prototypes/<slug>-improvements.md

，列出3–5个具体缺陷，这些缺陷是在捕获的网站中观察到的。这是变体A的执行 brief：不指定视觉目标，而是描述现有网站与同一品牌的2026年合格版本之间的差距。变体B及以后需将该列表作为最低标准（可进一步优化，但不得违背）。

当确定的模式为品牌重塑时，跳过此阶段——改进列表基于品牌一致性继承，而品牌重塑是替换网站而非修复它。

审核复用。若该源站存在

stardust/audit/<domain-slug>/audit.json

（由

stardust:audit

生成），则使用其设计发现作为候选改进项，而非重新推导——将发现ID带入每个项的证据引用。每个复用项仍需满足下文的具体性要求。

What goes in the list

列表内容

The list draws from five categories. Items should be specific enough that a downstream

prototype

shape brief can cite them by number.

Dated patterns the design world has moved past — name the pattern and its era, not a feeling.
Cluttered IA — unclear hierarchy, weak or redundant CTAs, fragmented conversion funnels.
Contrast failures, accessibility gaps, density issues — pull from
```
brand-review.html
```
Tensions when present (
```
T-color-imbalance
```
,
```
T-img-alt-empty
```
, etc.).
Cliché conventions the brand could move past while staying recognisably itself.
Missed opportunities the existing site doesn't capitalise on.

Worked examples per category:

reference/improvements-list.md

列表内容来自五个类别。每个项需足够具体，以便下游

prototype

的形状 brief 可通过编号引用。

过时模式：设计领域已淘汰的模式——需命名模式及其所属年代，而非主观感受。
混乱的IA：层级不清晰、CTA薄弱或冗余、转化漏斗碎片化。
对比度不足、可访问性缺口、密度问题：从
```
brand-review.html
```
的问题点中获取（如
```
T-color-imbalance
```
、
```
T-img-alt-empty
```
等）。
陈规俗套：品牌可在保持辨识度的前提下摒弃的惯例。
错失的机会：现有网站未充分利用的潜力。

每个类别的示例见

reference/improvements-list.md

。

Specificity bar

具体性要求

A weakness is specific enough when it cites:

a measurable observation (size, ratio, contrast value, count, or named tension ID) drawn from the per-page JSON, the brand-review, or the brand-extraction;
the design pattern at fault (named, e.g. "centered hero + dual CTA");
one concrete fix the variant A brief will apply.

"The hero needs work" fails all three. "Hero photo is cropped to 280×180 in a 1440-wide viewport when the captured source supports 16:9 full-bleed at 1440×810; variant A fix: render at full-bleed and move the headline to a left-anchored two-column overlay" passes all three.

缺陷需满足以下条件才算足够具体：

包含可测量的观察结果（尺寸、比例、对比度值、数量或命名的问题点ID），来自单页JSON、品牌评审或品牌提取结果；
指出有问题的设计模式（命名，如“居中Hero+双CTA”）；
列出变体A brief 将应用的一个具体修复方案。

*“Hero需要优化”不符合所有三个条件。“Hero图片在1440宽视口中被裁剪为280×180，但捕获的源图支持1440×810的16:9全屏显示；变体A修复方案：全屏渲染，并将标题移至左对齐的两列叠加层”*符合所有三个条件。

Format

格式

Markdown, with a

_provenance

frontmatter block per the artifact-map convention. Each item is a numbered list entry with a category tag, a weakness statement, and a one-line fix. Full worked example in

reference/improvements-list.md

§ Format example.

使用Markdown格式，根据工件映射约定添加

_provenance

前置块。每个项为编号列表条目，包含类别标签、缺陷说明和一行修复方案。完整示例见

reference/improvements-list.md

的“格式示例”章节。

Stopping condition

终止条件

If after reading the brand-review, the per-page JSON, and the brand-extraction the agent cannot name 3 specific weaknesses that meet the specificity bar, stop. Variant A has no brief; the "better" claim fails. See § Failure modes (d).

The agent should not rationalise — "the hero is dated" is not an item, "the typography could be more modern" is not an item. Genuine empty-list cases occur when the captured site is already at a high execution level on observable dimensions. In that case the honest answer is to surface the empty list and propose reduced scope (density-and-contrast adjustments only, or pivot to a single exploratory variant rather than three).

若读取品牌评审、单页JSON和品牌提取结果后，Agent无法列出3个符合具体性要求的缺陷，则停止操作。变体A无执行 brief；“优化”的主张不成立。参见失败模式(d)。

Agent不得合理化——*“Hero过时了”不算一个项，“字体可以更现代”*不算一个项。当捕获的网站在可观察维度已达到较高执行水平时，会出现真正的空列表情况。此时需如实告知用户空列表情况，并建议缩小范围（仅调整密度和对比度，或转为单个探索性变体而非三个）。

Phase 2.6 — Multi-variant fork (when N > 1)

第二阶段第6节 — 多变体分支（当N > 1时）

When the user requests N variants (phrase contains "3 variants", "4 directions", or equivalent), variant slots are role-differentiated, not seed-differentiated. Branch on the

ia-fidelity

tier stamped in Phase 1: surface-tuning forks A1/A2/A3 under

verbatim

; role-differentiated A + B + C (faithful

improvements / one captured trait amplified / a different captured trait amplified) under
```
reimagined
```
. Read
```
reference/multi-variant.md
```
and follow its variant role contract, differentiation contract (each variant pair differs by ≥ 2 substantive changes), surface-fork rules, and render-refusal conditions before resolving any variant.

当用户要求生成N个变体（意图包含“3个变体”“4个方向”或类似表述）时，变体插槽是角色差异化的，而非种子差异化。根据第一阶段标记的

ia-fidelity

层级分支：

verbatim

（完全一致）下生成表层调优分支A1/A2/A3；

reimagined

（重新构想）下生成角色差异化的A + B + C（一致性+改进/强化一个已捕获特征/强化另一个已捕获特征）。在确定任何变体前，需阅读

reference/multi-variant.md

并遵循其变体角色约定、差异化约定（每个变体对需有≥2个实质性差异）、表层分支规则和渲染拒绝条件。

Phase 3 — Author target PRODUCT.md

第三阶段 — 撰写目标PRODUCT.md

Write

PRODUCT.md

at the project root using impeccable's

reference/teach.md

as the format spec (not as a runtime command to invoke). Direct authoring is intentional: by the time

direct

runs, every answer impeccable's interview would surface has already been resolved through stardust's intent-reasoning + divergence resolution above.

Sections to populate:

Register — from the resolved direction's
```
register
```
axis.
Users — from the resolved audience tuple plus tone signals from the extracted brand surface.
Product Purpose — from the user's phrase + extracted hero copy
- resolved tone, written as a one-line value statement followed by one-line scope.
Brand Personality — derived from resolved expressive axis + tone + reference set. Weight axes the user explicitly moved over inherited values.
Anti-references — the user's stated anti-refs plus any anti-toolbox guardrails relevant to the resolved direction (e.g. "modernise" triggers the Generic-2026-SaaS silhouette guardrail; list it explicitly so prototype and polish enforce it).
Design Principles — 3-5, each mapping to a specific axis movement. Format: one verb-led principle, one-line elaboration.
Accessibility & Inclusion — populated when the constraint set includes
```
a11y-first
```
,
```
RTL-required
```
, or similar. Otherwise inherit impeccable's defaults.

Where a section cannot be populated with confidence from inputs, mark it

<!-- _provenance: inferred -->

with a one-line basis sentence. Never invent strategy.

使用impeccable的

reference/teach.md

作为格式规范（而非运行时命令），在项目根目录编写

PRODUCT.md

。直接撰写是有意为之：当

direct

运行时，impeccable访谈会涉及的所有问题已通过stardust的意图推理+差异决策流程解决。

需填充的章节：

风格：来自已确定方向的
```
register
```
维度。
用户：来自已确定的受众组合，加上从提取的品牌表层信息中获取的风格信号。
产品目标：来自用户意图+提取的Hero文案+已确定的风格，以一行价值声明加一行范围说明的形式撰写。
品牌个性：从已确定的表现力维度+风格+参考集推导而来。用户明确调整的维度权重高于继承值。
反参考：用户指定的反参考加上与已确定方向相关的反工具箱规则（例如“现代化”触发Generic-2026-SaaS轮廓规则；需明确列出，以便prototype和polish命令强制执行）。
设计原则：3-5条，每条对应一个具体的维度调整。格式：动词开头的原则，加一行说明。
可访问性与包容性：当约束集包含
```
a11y-first
```
、
```
RTL-required
```
等时填充。否则继承impeccable的默认值。

若无法从输入中自信地填充某个章节，标记为

<!-- _provenance: inferred -->

并添加一行依据说明。不得编造策略。

Phase 4 — Author target DESIGN.md and DESIGN.json (site-level only)

第四阶段 — 撰写目标DESIGN.md和DESIGN.json（仅站点级）

Write

DESIGN.md

at the project root using impeccable's

reference/document.md

as the format spec — Stitch YAML frontmatter plus the 6 canonical sections in fixed order.

Site-level only.

direct

authors the design system, not page-level deployments. Page-specific composition decisions live in

stardust/prototypes/<slug>-shape.md

written by

prototype

Phase 1 — see

skills/prototype/reference/page-shape-brief.md

The boundary is abstract role vs literal deployment:

In DESIGN.md / DESIGN.json (site system)	In `<slug>-shape.md` (page deployment)
Token vocabulary (colors, typography, spacing, radii)	Per-page section list and order
Voice rules ("Mixed-Case-Headlines"), anti-refs	Literal copy per section (sourced from current/pages/<slug>.json)
Anti-toolbox audit, divergence trace	Page-specific layout decisions ("hero is 5/3 split on home")
Abstract component vocabulary: `button-primary` , `button-secondary` , `card` , `input` , `badge` , `link` (default treatment, density, sizing — NO page-specific dimensions or content)	Section-level component dimensions ( `the211Panel` at 320×260 with dock points per viewport)
Named system-component roles (a `header` exists, a `footer` exists, a `cta-band` pattern exists)	System-component deployment (literal tile labels in fixed order, link targets, copy variants)
Default visual treatment for each abstract component	Per-page composition (statRow with literal "100 YEARS · 18,400 PEOPLE HOUSED · …")
Voice samples (do/don't, tone exemplars)	Per-page interaction model and key states

Concrete examples of items that must not appear in DESIGN.md / DESIGN.json:

Literal tile labels for any system-component pattern.
Section-level pixel dimensions, dock points, breakpoint-specific widths.
Stat numbers, addresses, quotes, named-person references.
"On home, the hero is X" — that's a home-page deployment.
Per-page copy variants ("on the donate page the CTA reads Y").

If a redesign demands a section-level dimension or a literal label that feels site-wide ("every page has a 211 panel docked at the bottom-right"), encode it as an abstract role in DESIGN.json (e.g.

extensions.systemComponentRoles.persistent-help

with purpose / position-class but no literal copy or dimensions) and let each page's shape brief specify the deployment.

Token sources:

colors
— from the picked palette (palette-picker.md output) or the inherited palette with role-renaming. Role names must satisfy toolkit § 4 (brand-native, no
```
Primary
```
/
```
Secondary
```
/
```
Alarm
```
etc. as sole role names).
typography
— from the chosen font deck. Sizes scaled by the resolved expressive axis (drenched → ratio ≥ 1.333; committed → ratio 1.25; restrained → ratio 1.125-1.2). Heading vs body assignments inherit from the deck.
rounded
— derived from extracted brand-surface
```
borderRadius.primary
```
mode, unless the direction moves distinctiveness toward
```
singular
```
(in which case re-derive from the font deck's tonal cousins).
spacing
— 4pt base scale;
```
sectionPadding
```
propagated from the density tier stamped in Phase 1 (
```
reference/intent-dimensions.md
```
§ 4):
- ```
airy
```
  →
```
sectionPadding.desktop: 96px
```
  ,
```
tablet: 72px
```
  ,
```
mobile: 48px
```
- ```
balanced
```
  →
```
sectionPadding.desktop: 64px
```
  ,
```
tablet: 48px
```
  ,
```
mobile: 32px
```
  ← brand-register default
- ```
packed
```
  →
```
sectionPadding.desktop: 48px
```
  ,
```
tablet: 36px
```
  ,
```
mobile: 24px
```
  ← product-register default
The agent does not re-ask the density question here — the tier was resolved in Phase 1 (asked once when the phrase didn't move the axis, defaulted to balanced for brand register if unanswered). Pick the value deterministically from the stamp.

Hard floor enforcement. When the captured page inventory shows
5 sections OR >2 audience tracks (per
```
reference/intent-dimensions.md
```
§ 4 → "Hard floor for brand-register multi-audience sites"), the resolved
```
sectionPadding.desktop
```
is bounded at ≤ 64px and ≥ 40px on every variant including the highest-divergence one. If Phase 1 stamped
```
airy
```
despite the trigger conditions firing, surface the conflict before writing tokens — "density tier
airy
was selected but the captured inventory triggers the multi-audience hard floor; pick (a) override floor (
density: airy (user-pinned)
in direction.md) or (b) accept the floor (sectionPadding capped at 64px)." Default to (b) when the user does not respond.
components
— 4-6 canonical components (
```
button-primary
```
,
```
button-secondary
```
,
```
card
```
,
```
input
```
,
```
badge
```
,
```
link
```
) populated from extracted brand-surface
```
componentStyle
```
, with values adjusted for direction movements.

Write

DESIGN.json

(schemaVersion 2) with:

extensions.colorMeta

typographyMeta

shadows

motion

breakpoints

— filled from the same sources as DESIGN.md. The

motion

block carries the register selection (when cinematic motion may be applied at prototype time):

json

"motion": {
  "register": "arrival | kinetic-display | live-systems | editorial | kinetic-grid",
  "registerRationale": "<one-line citation back to PRODUCT.md Brand Personality trait that selected this register>",
  "easings":   { "entrance": "...", "transition": "...", "expo": "..." },
  "durations": { "enter": <ms>, "stagger": <ms> },
  "parallax":  { "translate": <vh>, "fade": <0-1>, "rangeStart": <%>, "range": <%> }
}

Picked per the register selection heuristic in

skills/prototype/reference/motion-registers.md

§ Selection heuristic, reading the resolved

PRODUCT.md

§ Brand Personality:

Personality traits (any match)	Register
`civic-formal` + ( `institutional` OR `place-led` )	`arrival`
`signage-led` OR `wayfinding-first` OR `display-typography-signature`	`kinetic-display`
`operationally-transparent` OR `data-led` OR `dashboard-register`	`live-systems`
`editorial` OR `slow-paced` OR `publication-register`	`editorial`
`product` OR `SaaS` OR `transactional` OR `modular-catalogue`	`kinetic-grid`
(ambiguous / no clear match)	`arrival`

Token defaults per register are sourced from

skills/prototype/reference/motion-registers.md

§ The five registers;

direct

copies them verbatim into the

motion

block unless the user has provided overrides during intent reasoning. The

registerRationale

field records the one-line justification so reviewers can audit the choice. direct
does not apply the motion — that happens at prototype time under

--cinematic

direct

only selects the register. Pages whose redesign does not need motion can leave

register

absent; cinematic prototype will then either ask or pick from the heuristic at render time.

Per-variant placement (when N > 1 variants). The

motion

block goes into the variant-specific

DESIGN-<id>.json

files, not site-level

DESIGN.json

— variants without a

register

render static. See

reference/multi-variant.md

§ Per-variant motion placement.

When the user's intent phrase contains explicit motion direction ("make it cinematic", "feel alive", "move like signage"),

direct

picks the register and notes the source in

registerRationale

"user-phrase: <verbatim>"

```
extensions.divergence
```
— full audit trail per the v2 storage shape in
```
divergence-toolkit.md
```
. Includes the brand-faithful inversion log (per
```
reference/direction-format.md
```
§ Divergence inputs) capturing pure-color or hex-format retentions.
```
extensions.componentStyle
```
— the abstract v1 fields (
```
buttons
```
,
```
cards
```
,
```
inputs
```
,
```
dualCTAPattern
```
). Default treatment per component, no per-page dimensions or literal copy.
```
extensions.systemComponentRoles
```
— the abstract roles for named cross-page patterns (e.g.
```
persistent-help
```
,
```
cta-band
```
,
```
header
```
,
```
footer
```
). Each role carries purpose, position class, and any site-wide constraint — not literal copy, dimensions, or per-viewport dock points (those are page-deployment, in
```
<slug>-shape.md
```
).
```
extensions.voice
```
— sampled DOs and DON'Ts derived from
```
_brand-extraction.json
```
voice samples + the resolved tone.
```
narrative.northStar
```
,
```
overview
```
,
```
keyCharacteristics
```
,
```
rules
```
,
```
dos
```
,
```
donts
```
— derived from the resolved direction. Toolkit § 7 Optional House Standards land here in
```
narrative.rules[]
```
.

Every component HTML/CSS snippet in

components[]

must be self-contained, use

ds-

class prefixes, and respect impeccable's hard rules (OKLCH only, no pure black/white, no glassmorphism, no side stripes, no gradient text, ≥ 1.25 type ratio for brand register).

使用impeccable的

reference/document.md

作为格式规范，在项目根目录编写

DESIGN.md

——包含Stitch YAML前置块，加上固定顺序的6个标准章节。

仅站点级。

direct

撰写设计系统，而非页面级部署。页面特定的组合决策由

prototype

第一阶段生成的

stardust/prototypes/<slug>-shape.md

负责——参考

skills/prototype/reference/page-shape-brief.md

。

边界为抽象角色 vs 字面部署：

属于DESIGN.md / DESIGN.json（站点系统）	属于 `<slug>-shape.md` （页面部署）
令牌词汇（颜色、字体、间距、圆角）	单页章节列表和顺序
风格规则（“首字母大写标题”）、反参考	每个章节的字面文案（来自current/pages/<slug>.json）
反工具箱审核、差异轨迹	页面特定布局决策（“首页Hero为5/3分栏”）
抽象组件词汇： `button-primary` 、 `button-secondary` 、 `card` 、 `input` 、 `badge` 、 `link` （默认样式、密度、尺寸——无页面特定维度或内容）	章节级组件维度（ `the211Panel` 在不同视口下为320×260，带有停靠点）
命名系统组件角色（存在 `header` 、 `footer` 、 `cta-band` 模式）	系统组件部署（固定顺序的字面 tile 标签、链接目标、文案变体）
每个抽象组件的默认视觉样式	页面特定组合（statRow包含字面内容“100 YEARS · 18,400 PEOPLE HOUSED · …”）
风格示例（正确/错误示例、风格范例）	页面特定交互模型和关键状态

以下内容不得出现在DESIGN.md / DESIGN.json中：

任何系统组件模式的字面 tile 标签。
章节级像素维度、停靠点、断点特定宽度。
统计数字、地址、引用、特定人物参考。
“首页的Hero是X”——这是首页部署内容。
页面特定文案变体（“捐赠页面的CTA为Y”）。

若重设计要求某个章节级维度或字面标签需全站应用（如“每个页面右下角都有一个211面板”），需将其编码为DESIGN.json中的抽象角色（例如

extensions.systemComponentRoles.persistent-help

，包含用途/位置类，但无字面文案或维度），并让每个页面的形状 brief 指定部署方式。

令牌来源：

colors
：来自选定的配色方案（palette-picker.md输出）或经过角色重命名的继承配色方案。角色名称需满足工具包第4节（品牌原生，不得仅使用
```
Primary
```
/
```
Secondary
```
/
```
Alarm
```
等作为角色名称）。
typography
：来自选定的字体栈。尺寸根据已确定的表现力维度缩放（浓郁→比例≥1.333；坚定→比例1.25；克制→比例1.125-1.2）。标题与正文的分配继承自字体栈。
rounded
：从提取的品牌表层
```
borderRadius.primary
```
模式推导，除非方向将独特性调整为
```
singular
```
（此时从字体栈的风格同类中重新推导）。
spacing
：4pt基础缩放；
```
sectionPadding
```
从第一阶段标记的密度层级传播（参考
```
reference/intent-dimensions.md
```
第4节）：
- ```
airy
```
  →
```
sectionPadding.desktop: 96px
```
  ,
```
tablet: 72px
```
  ,
```
mobile: 48px
```
- ```
balanced
```
  →
```
sectionPadding.desktop: 64px
```
  ,
```
tablet: 48px
```
  ,
```
mobile: 32px
```
  ← 品牌风格默认值
- ```
packed
```
  →
```
sectionPadding.desktop: 48px
```
  ,
```
tablet: 36px
```
  ,
```
mobile: 24px
```
  ← 产品风格默认值
Agent在此阶段不会重新询问密度问题——层级已在第一阶段确定（当意图未涉及该维度时询问一次，未回复则品牌风格默认选择均衡）。根据标记确定性选择值。
硬下限强制执行。当捕获的页面清单包含>5个章节或>2个受众轨迹（参考
```
reference/intent-dimensions.md
```
第4节→“品牌风格多受众网站硬下限”）时，已确定的
```
sectionPadding.desktop
```
在所有变体中（包括差异最大的变体）需限制在≤64px且≥40px。若第一阶段标记为
```
airy
```
但触发条件已满足，需在写入令牌前展示冲突：*“已选择密度层级
```
airy
```
，但捕获的清单触发多受众硬下限；请选择(a) 覆盖下限（在direction.md中标记为
```
density: airy (用户锁定)
```
）或(b) 接受下限（sectionPadding上限为64px）。”*用户未回复时默认选择(b)。
components
：4-6个标准组件（
```
button-primary
```
、
```
button-secondary
```
、
```
card
```
、
```
input
```
、
```
badge
```
、
```
link
```
），从提取的品牌表层
```
componentStyle
```
填充，并根据方向调整值。

编写

DESIGN.json

（schemaVersion 2），包含：

extensions.colorMeta

、

typographyMeta

、

shadows

、

motion

、

breakpoints

——与DESIGN.md来源相同。

motion

块包含风格选择（原型阶段可应用电影级动效）：

json

"motion": {
  "register": "arrival | kinetic-display | live-systems | editorial | kinetic-grid",
  "registerRationale": "<一行引用PRODUCT.md品牌个性特征的说明，解释选择该风格的原因>",
  "easings":   { "entrance": "...", "transition": "...", "expo": "..." },
  "durations": { "enter": <ms>, "stagger": <ms> },
  "parallax":  { "translate": <vh>, "fade": <0-1>, "rangeStart": <%>, "range": <%> }
}

根据

skills/prototype/reference/motion-registers.md

的“选择启发式”，读取已确定的

PRODUCT.md

“品牌个性”章节进行选择：

个性特征（匹配任意一项）	风格
`civic-formal` + ( `institutional` OR `place-led` )	`arrival`
`signage-led` OR `wayfinding-first` OR `display-typography-signature`	`kinetic-display`
`operationally-transparent` OR `data-led` OR `dashboard-register`	`live-systems`
`editorial` OR `slow-paced` OR `publication-register`	`editorial`
`product` OR `SaaS` OR `transactional` OR `modular-catalogue`	`kinetic-grid`
（模糊/无明确匹配）	`arrival`

每个风格的令牌默认值来自

skills/prototype/reference/motion-registers.md

的“五种风格”章节；

direct

会将其直接复制到

motion

块中，除非用户在意图推理期间提供了覆盖值。

registerRationale

字段记录一行理由，以便评审人员审核选择。direct
不会应用动效——动效在原型阶段通过

--cinematic

参数应用。

direct

仅选择风格。无需动效的页面可省略

register

；电影级原型会在渲染时询问或根据启发式选择。

多变体放置（当N > 1时）。

motion

块放入变体特定的

DESIGN-<id>.json

文件，而非站点级的

DESIGN.json

——无

register

的变体将静态渲染。参考

reference/multi-variant.md

的“多变体动效放置”章节。

当用户的意图包含明确的动效方向（如“使其具有电影感”“更生动”“像标识一样动起来”）时，

direct

会选择对应的风格，并在

registerRationale

中记录来源为

"user-phrase: <原文>"

。

```
extensions.divergence
```
——根据
```
divergence-toolkit.md
```
的v2存储格式记录完整的审计轨迹。包含品牌一致性反转日志（参考
```
reference/direction-format.md
```
的“差异输入”章节），记录纯色或十六进制格式的保留内容。
```
extensions.componentStyle
```
——抽象v1字段（
```
buttons
```
、
```
cards
```
、
```
inputs
```
、
```
dualCTAPattern
```
）。每个组件的默认样式，无页面特定维度或字面文案。
```
extensions.systemComponentRoles
```
——跨页面命名模式的抽象角色（如
```
persistent-help
```
、
```
cta-band
```
、
```
header
```
、
```
footer
```
）。每个角色包含用途、位置类和任何全站约束——无字面文案、维度或视口特定停靠点（这些属于页面部署，在
```
<slug>-shape.md
```
中）。
```
extensions.voice
```
——从
```
_brand-extraction.json
```
风格示例+已确定的风格推导的正确/错误示例。
```
narrative.northStar
```
、
```
overview
```
、
```
keyCharacteristics
```
、
```
rules
```
、
```
dos
```
、
```
donts
```
——从已确定的方向推导而来。工具包第7节的可选内部标准记录在
```
narrative.rules[]
```
中。

components[]

中的每个组件HTML/CSS片段必须独立完整，使用

ds-

类前缀，并遵守impeccable的严格规则（仅使用OKLCH颜色、无纯黑/纯白、无玻璃态效果、无侧边条纹、无渐变文本、品牌风格字体比例≥1.25）。

IA-priority preservation audit (Mode A)

IA优先级保留审核（Mode A）

After tokens are drafted but before they land in the variant DESIGN files, run the IA-priority preservation audit per

reference/intent-dimensions.md

§ 8. For each captured signal that fires a trigger condition (commercial conversion, search-led IA, donation funnel, crisis affordance, audience routing), record an

extensions.iaPriorities[]

entry in

DESIGN.json

json

[
  {
    "signal": "crisis-affordance",
    "evidence": "pages/home.json#landmarks[hero] contains heading 'Looking for immediate shelter?' + phone 801-990-9999",
    "preserveAs": "first-viewport",
    "scope": "site-wide",
    "mutability": "movable"
  }
]

Each entry is a constraint that downstream

prototype

and

migrate

must honor — a variant whose home shape brief omits the crisis affordance from the first viewport fails the audit and is rejected. The audit is the structural enforcement of § 8; without it, IA- priority preservation is a guideline rather than a contract.

The

mutability

field reflects the

ia-fidelity

stamp from Phase 1 (per

reference/intent-dimensions.md

§ 9):

locked

under verbatim (variants may not move the priority at all — A1/A2/A3 are surface forks),

movable

under reimagined (variants may demote / promote / re-shape the priority's deployment, but the § 8 floor still fires). The field is stamped once at Phase 4 and is the source of truth prototype reads.

令牌起草完成但写入变体DESIGN文件前，根据

reference/intent-dimensions.md

第8节执行IA优先级保留审核。对于每个触发条件的捕获信号（商业转化、搜索主导IA、捐赠漏斗、危机功能、受众路由），在

DESIGN.json

中记录

extensions.iaPriorities[]

条目：

json

[
  {
    "signal": "crisis-affordance",
    "evidence": "pages/home.json#landmarks[hero]包含标题'Looking for immediate shelter?' + 电话801-990-9999",
    "preserveAs": "first-viewport",
    "scope": "site-wide",
    "mutability": "movable"
  }
]

每个条目是下游

prototype

和

migrate

必须遵守的约束——若某个变体的首页形状 brief 未在首屏包含危机功能，则审核失败并被拒绝。该审核是第8节的结构性强制执行；若无此审核，IA优先级保留只是一个指导方针而非契约。

mutability

字段反映第一阶段标记的

ia-fidelity

层级（参考

reference/intent-dimensions.md

第9节）：

verbatim

（完全一致）下为

locked

（变体不得调整优先级——A1/A2/A3为表层分支）；

reimagined

（重新构想）下为

movable

（变体可降级/升级/重塑优先级的部署方式，但第8节的下限规则仍生效）。该字段在第四阶段标记一次，是prototype读取的唯一来源。

Multi-variant DESIGN files (when N > 1)

多变体DESIGN文件（当N > 1时）

When Phase 2.6 is active, Phase 4 writes

PRODUCT.md

(shared) plus per-variant

DESIGN-{A,B,C,…}.{md,json}

instead of a single pair; every variant inherits the shared

extensions.iaPriorities[]

audit. Under rebrand mode PRODUCT.md may also vary per variant. See

reference/multi-variant.md

§ Multi-variant DESIGN files.

当第二阶段第6节激活时，第四阶段会生成共享的

PRODUCT.md

，加上每个变体的

DESIGN-{A,B,C,…}.{md,json}

文件，而非单个文件；所有变体继承共享的

extensions.iaPriorities[]

审核结果。品牌重塑模式下，每个变体的PRODUCT.md也可能不同。参考

reference/multi-variant.md

的“多变体DESIGN文件”章节。

Phase 5 — Write direction.md and update state

第五阶段 — 撰写direction.md并更新状态

Write

stardust/direction.md

per

skills/direct/reference/direction-format.md

. The full reasoning trace: phrase, restatement, movements, gaps, questions and answers, resolved axes, divergence inputs, command sequence proposed, user confirmation, every assumption that defaulted in. Re-directs append to the file as a new section; prior direction stays as history.

Update

stardust/state.json

```
direction.resolvedAt
```
= now
```
direction.phrase
```
= the user's verbatim phrase

direction.directionFile

"stardust/direction.md"

For each page in scope:
```
status
```
```
extracted
```
→
```
directed
```
On
```
--re-direct
```
, for each page already in
```
prototyped
```
/
```
approved
```
/
```
migrated
```
: set
```
stale: true
```
and
```
staleReason: "direction changed at <ts>"
```
. Do not change the status itself; the on-disk artifact is still valid, just out of step.

Print a one-screen summary report and recommend the next step:

direction resolved
==================

Phrase:    "make it more expressive for a young audience"
Audience:  Gen Z college / first-job (resolved via Q1)
Register:  brand (inherited from current/PRODUCT.md)

Movements:
  expressive axis    restrained -> committed
  distinctiveness    familiar  -> distinctive
  tone               serious   -> playful
  density            (unchanged)
  audience           (resolved: Gen Z college / first-job)

Divergence:
  seed         1970s x Riso print x zine x monochrome-tint
  font deck    zine-maximalist
  palette      "Brutalist Dawn" (picked from library)

Wrote:
  PRODUCT.md, DESIGN.md, DESIGN.json
  stardust/direction.md

State:
  25 pages: extracted -> directed
  0 stale prototypes (none exist yet)

Next: $stardust prototype  (defaults to home page)

根据

skills/direct/reference/direction-format.md

撰写

stardust/direction.md

。包含完整的推理轨迹：用户意图、重述、调整方向、缺口、问题与答案、已确定的维度、差异输入、提议的命令序列、用户确认、所有默认的假设。重新定向会在文件中添加新章节；历史方向保留为历史记录。

更新

stardust/state.json

：

```
direction.resolvedAt
```
= 当前时间
```
direction.phrase
```
= 用户的原文意图

direction.directionFile

"stardust/direction.md"

对于所有范围内的页面：
```
status
```
从
```
extracted
```
→
```
directed
```
若使用
```
--re-direct
```
，对于所有已处于
```
prototyped
```
/
```
approved
```
/
```
migrated
```
状态的页面：设置
```
stale: true
```
和
```
staleReason: "direction changed at <时间戳>"
```
。不改变状态本身；磁盘上的工件仍然有效，只是与当前方向不一致。

打印一屏摘要报告并建议下一步操作：

direction resolved
==================

意图:    "针对年轻受众提升表现力"
受众:  Z世代大学生/初入职场人群（通过Q1确定）
风格:  品牌风格（继承自current/PRODUCT.md）

调整方向:
  表现力维度    克制 -> 坚定
  独特性        熟悉 -> 鲜明
  风格          严肃 -> 活泼
  密度          （未调整）
  受众          （已确定：Z世代大学生/初入职场人群）

差异:
  种子         1970年代 x Risograph印刷 x 独立杂志 x 单色色调
  字体栈       独立杂志最大化风格
  配色方案     "Brutalist Dawn"（从库中选择）

已生成文件:
  PRODUCT.md, DESIGN.md, DESIGN.json
  stardust/direction.md

状态:
  25个页面: extracted -> directed
  0个过时原型（尚未生成）

下一步: $stardust prototype （默认生成首页）

Outputs

输出文件

Path	Purpose
`PRODUCT.md`	Target strategy (impeccable format). Shared across variants when N > 1 under Mode A.
`DESIGN.md`	Target visual system (Stitch frontmatter + 6 sections). Single-variant runs only.
`DESIGN.json`	Sidecar with extensions (divergence, componentStyle, voice, iaPriorities) and narrative. Single-variant runs only.
`DESIGN-{A,B,C,…}.md`	Per-variant DESIGN files when the user requested N > 1 variants (Phase 2.6 active).
`DESIGN-{A,B,C,…}.json`	Per-variant DESIGN sidecars matching the .md files.
`stardust/prototypes/<slug>-improvements.md`	Improvements list (Mode A only, written in Phase 2.5). The load-bearing artifact for variant A.
`stardust/direction.md`	Resolved direction + full reasoning trace + per-variant resolutions when N > 1.
`stardust/state.json`	Updated with direction + per-page status changes + `direction.variantMode` + `direction.variants[]` when N > 1.

路径	用途
`PRODUCT.md`	目标策略（impeccable格式）。Mode A下N > 1时所有变体共享。
`DESIGN.md`	目标视觉系统（Stitch前置块 + 6个章节）。仅单变体运行时生成。
`DESIGN.json`	包含扩展字段（差异、componentStyle、风格、iaPriorities）和叙事的附属文件。仅单变体运行时生成。
`DESIGN-{A,B,C,…}.md`	用户要求N > 1个变体时（第二阶段第6节激活）生成的每个变体的DESIGN文件。
`DESIGN-{A,B,C,…}.json`	对应.md文件的每个变体DESIGN附属文件。
`stardust/prototypes/<slug>-improvements.md`	改进列表（仅Mode A，第二阶段第5节生成）。是变体A的核心工件。
`stardust/direction.md`	已确定的方向 + 完整推理轨迹 + N > 1时的每个变体决策。
`stardust/state.json`	更新方向 + 每个页面的状态变化 + N > 1时的 `direction.variantMode` + `direction.variants[]` 。

Failure modes

失败模式

No extracted state. Abort and recommend
```
$stardust extract
```
.
Phrase too vague even after two questions. Persist the partial reasoning to
```
stardust/direction.md
```
under a
```
# Pending
```
section, ask the user to refine further, do not write
```
PRODUCT.md
```
/
```
DESIGN.md
```
/
```
DESIGN.json
```
from incomplete reasoning.
Re-direct with prior approved or migrated pages. Always confirm before stale-flagging. The flag is visible to the user and reversible (clearing happens automatically on successful re-run of prototype or migrate), but a re-direct invalidates work the user may have signed off on.
Anti-toolbox audit removes too many moves. If the resolved direction collapses to defaults after the audit strips unjustifiable hits, surface this to the user and re-prompt for reference anchors before writing tokens.
(b) Insufficient brand signal for N variants. Fewer than 3 distinct amplifiable traits in the captured surface (or
```
signal-thin
```
) → refuse N ≥ 3 under Mode A and propose 1–2 variants instead; full contract in
```
reference/multi-variant.md
```
§ Failure mode.
(c) Hard rule conflict. When Mode A is active and the user's phrase requires violating a Mode A pin (e.g., the user asks for "a completely different palette" while migration mode is active and
```
--rebrand
```
was not passed), stop. Name the conflict explicitly: "You asked to keep the brand and to change the palette — those are not compatible. Did you mean (a) keep the current palette and only refresh execution, (b) rebrand (
--rebrand
) and roll a new palette, or (c) Mode A with a targeted palette move (single role recolored, rest pinned)?" Wait for explicit answer.
(d) Empty improvements list. When Phase 2.5 produces fewer than 3 weaknesses meeting the specificity bar, stop before rendering any variant. Variant A's brief depends on the list; without it, the "better" claim fails. Surface honestly: "the captured site is already at a competent execution level on observable dimensions — variant A would reduce to spacing and contrast adjustments only." Ask the user whether to (a) proceed with reduced scope (density + contrast only), (b) extract additional pages (
```
extract --cap 25
```
or higher) to surface more weaknesses, or (c) pivot to rebrand mode (
```
--rebrand
```
) where the brand-fidelity floor doesn't apply.

无提取状态。终止操作并建议执行
```
$stardust extract
```
。
意图过于模糊，即使经过两个问题仍无法明确。将部分推理内容保存到
```
stardust/direction.md
```
的
```
# Pending
```
章节，要求用户进一步细化，不得基于不完整推理生成
```
PRODUCT.md
```
/
```
DESIGN.md
```
/
```
DESIGN.json
```
。
重新定向时存在已批准或已迁移的页面。标记为过时前需确认。标记对用户可见且可撤销（重新执行prototype或migrate成功时自动清除），但重新定向会使用户已签字确认的工作失效。
反工具箱审核移除过多调整。若审核移除不合理的调整后，已确定的方向退化为默认值，需告知用户并在写入令牌前重新请求参考锚点。
(b) 品牌信号不足无法生成N个变体。捕获的表层中可强化的独特特征少于3个（或
```
signal-thin
```
）→ Mode A下拒绝生成N ≥ 3个变体，建议生成1–2个变体；完整约定见
```
reference/multi-variant.md
```
的“失败模式”章节。
(c) 严格规则冲突。当Mode A激活且用户的意图要求违反Mode A绑定规则（例如用户要求“完全不同的配色方案”但处于迁移模式且未传入
```
--rebrand
```
参数）时，终止操作。明确指出冲突：*“您要求保留品牌同时更改配色方案——这两者不兼容。您的意思是(a) 保留当前配色仅优化执行，(b) 品牌重塑（
```
--rebrand
```
）并生成新配色，还是(c) Mode A下定向调整配色（仅重命名单个角色，其余绑定）？”*等待明确回复。
(d) 空改进列表。当第二阶段第5节生成的符合具体性要求的缺陷少于3个时，在生成任何变体前终止操作。变体A的brief依赖该列表；若无列表，“优化”的主张不成立。如实告知用户：*“捕获的网站在可观察维度已达到合格执行水平——变体A仅能调整间距和对比度。”*询问用户是否(a) 缩小范围继续执行（仅调整密度+对比度），(b) 提取更多页面（
```
extract --cap 25
```
或更高）以发现更多缺陷，或(c) 转为品牌重塑模式（
```
--rebrand
```
），此时品牌保真度下限不适用。

Prep mode (--prep)

准备模式（--prep）

When invoked with

--prep

, direct runs an extended pass that finalizes the inventory data structures migrate consumes: type catalog confirmation, module catalog finalization, color reservations, a wider direction re-evaluation, and site-level metadata defaults. Read

reference/prep-mode.md

and follow it on top of the standard procedure. Discovery-mode runs are unchanged.

当传入

--prep

参数时，direct会执行扩展流程，最终确定migrate命令使用的清单数据结构：类型目录确认、模块目录最终确定、颜色预留、更广泛的方向重新评估、站点级元数据默认值。在标准流程基础上，阅读并遵循

reference/prep-mode.md

。发现模式运行不变。

Add-variant mode (--add-variant)

添加变体模式（--add-variant）

When the user has already approved (or rendered) variant A and asks for B / C / etc. as alternatives,

--re-direct

is too heavy — the user is extending the existing direction, not changing it.

--add-variant <name>

skips Phases 1–2 (mode, seed, palette, and ground family are inherited from the active direction), resolves the new variant's role per the variant role contract, and writes

DESIGN-<name>.{md,json}

plus a

## Variant <name>

section in

direction.md

, without stale-flagging any page. Read

reference/add-variant.md

and follow its procedure, parentage and per-field inheritance rules, and failure modes before writing anything.

当用户已批准（或生成）变体A并要求添加B/C等替代变体时，

--re-direct

过于重量级——用户是扩展现有方向，而非更改它。

--add-variant <name>

跳过第一至第二阶段（模式、种子、配色和底色家族继承自当前激活的方向），根据变体角色约定确定新变体的角色，并生成

DESIGN-<name>.{md,json}

文件，同时在

direction.md

中添加

## Variant <name>

章节，不会标记任何页面为过时。在生成任何文件前，阅读并遵循

reference/add-variant.md

的流程、父级和字段继承规则、失败模式。

References

参考文档

```
skills/stardust/reference/intent-dimensions.md
```
— the 8 axes (the 7 axes plus § 8 IA-priority preservation, the Mode A constraint that fires on captured commercial-conversion / crisis / audience-routing signals).

skills/stardust/reference/intent-reasoning.md

— the procedure.

skills/stardust/reference/intent-examples.md

— worked examples.

```
skills/stardust/reference/impeccable-command-map.md
```
— when to reach for each impeccable command (used when building the plan).
```
skills/stardust/reference/reference-research.md
```
— the research-first anchor procedure (refero MCP → WebSearch → seed fallback) consumed by Mode B and Default mode; evidence shape and budgets.

skills/stardust/reference/divergence-toolkit.md

— anti-mediocrity inputs and the v2 storage shape for the audit trail. Contains the anti-toolbox additions for multi-variant moves (

C-cliff overshoot

Anonymous middle variant

Variant homogeneity

) and universal hardening (

Fabricated content

Hero text on photographic background without contrast scrim

Editorial-register vocabulary applied to non-editorial brands

skills/stardust/reference/artifact-map.md

— provenance shape.

reference/direction-format.md

— schema for

stardust/direction.md

```
reference/palette-picker.md
```
— palette resolution procedure.
```
reference/prep-mode.md
```
— the
```
--prep
```
extended pass (provenance validation, type/module catalogs, color reservations, metadata).
```
reference/add-variant.md
```
— the
```
--add-variant
```
flow (procedure, variant parentage, per-field inheritance, failure modes).
```
reference/multi-variant.md
```
— the N > 1 fork: variant role contract, differentiation contract, surface forks, C-cliff.
```
reference/improvements-list.md
```
— worked examples for the Phase 2.5 improvements list (categories + format).
```
reference/mode-a-plus.md
```
— bounded brand-adjacent refinements.
```
reference/cross-site-brand-inputs.md
```
— design-donor and sibling-origin evidence rules.

```
skills/stardust/reference/intent-dimensions.md
```
— 8个维度（7个维度加上第8节IA优先级保留，即Mode A对捕获的商业转化/危机/受众路由信号的约束）。

skills/stardust/reference/intent-reasoning.md

— 意图推理流程。

skills/stardust/reference/intent-examples.md

— 示例。

```
skills/stardust/reference/impeccable-command-map.md
```
— 何时使用每个impeccable命令（用于生成计划）。
```
skills/stardust/reference/reference-research.md
```
— 优先研究的锚点流程（refero MCP → WebSearch → 种子 fallback），被Mode B和默认模式使用；证据格式和预算。

skills/stardust/reference/divergence-toolkit.md

— 反平庸输入参数和审计轨迹的v2存储格式。包含多变体调整的反工具箱补充规则（

C-cliff overshoot

、

Anonymous middle variant

、

Variant homogeneity

）和通用强化规则（

Fabricated content

、

Hero text on photographic background without contrast scrim

、

Editorial-register vocabulary applied to non-editorial brands

）。

skills/stardust/reference/artifact-map.md

— 来源格式。

reference/direction-format.md

—

stardust/direction.md

的 schema。

```
reference/palette-picker.md
```
— 配色方案确定流程。
```
reference/prep-mode.md
```
—
```
--prep
```
扩展流程（来源验证、类型/模块目录、颜色预留、元数据）。
```
reference/add-variant.md
```
—
```
--add-variant
```
流程（执行步骤、变体父级、字段继承、失败模式）。
```
reference/multi-variant.md
```
— N > 1分支：变体角色约定、差异化约定、表层分支、C-cliff规则。
```
reference/improvements-list.md
```
— 第二阶段第5节改进列表的示例（类别+格式）。
```
reference/mode-a-plus.md
```
— 有限的品牌相关优化。
```
reference/cross-site-brand-inputs.md
```
— 设计捐赠和兄弟源证据规则。",