implement-plan

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

implement-plan — execute plan.md phase by phase, logic untouched

implement-plan — 逐阶段执行 plan.md，逻辑保持不变

Take the existing

plan.md

and implement its 5 phases, changing only the presentation while the 5 logic-freeze instructions hold. The transformation recipes live in

TRANSFORM.md

(this folder).

读取现有的

plan.md

并实施其中 5 个阶段。在 5 条 logic-freeze 指令的约束下，仅更改 presentation（呈现层），同时保持所有逻辑和 state 不变。转换配方位于本文件夹的

TRANSFORM.md

中。

The flow

执行流程

1. Load the plan and the contract. Read

plan.md

(required — if it's missing, stop and ask the user to run

/plan-redesign

first). Extract the 5 logic-freeze instructions (Block B) and the 5 phases (Block C). Load

TRANSFORM.md

for the recipes. The 5 logic-freeze instructions are the operating rule for every edit: state, hooks, handlers, and API/mutations are frozen; only the visual layer moves. Done when: the contract and the 5 phases are loaded, and the frozen logic (from the audit's freeze matrix) is named as the boundary.

2. Run the phases in order (1 → 5). For each phase:

Pick its target components from
```
plan.md
```
.
Apply the transformations using the matching
```
TRANSFORM.md
```
recipes (tokens, typography, spatial/bento, motion, responsive) for that phase's components.
Keep every change inside the visual layer and route all class concatenation through
```
cn()
```
.
Verify the phase: the diff for the phase's components is presentation-only — no state, hook, handler, or API/mutation changed. Check against the phase's definition of done. Done when: all 5 phases are implemented and each phase's definition of done is met.

3. Final zero-regression pass. Re-check the whole app against the audit's logic-freeze matrix: every frozen hook, handler, and API call is intact; the build/typecheck passes; the visual upgrade is live across the refactored components. Report what changed (presentation) and confirm nothing logic-related moved. Done when: all 5 phases are done and the final zero-regression verification passes — presentation upgraded, logic untouched.

1. 加载计划和契约。 读取

plan.md

（必需——如果文件不存在，请停止并让用户先运行

/plan-redesign

）。提取 5 条 logic-freeze 指令（Block B）和 5 个阶段（Block C）。加载

TRANSFORM.md

以获取转换配方。这 5 条 logic-freeze 指令是每次编辑的操作规则：state、hooks、handlers 和 API/mutations 均被冻结；只有视觉层可以调整。 完成条件： 契约和 5 个阶段均已加载，并且已明确指出冻结逻辑（来自审计的冻结矩阵）的边界。

2. 按顺序运行各阶段（1 → 5）。 对于每个阶段：

从
```
plan.md
```
中选择该阶段的目标组件。
使用
```
TRANSFORM.md
```
中匹配的配方，对该阶段的组件应用 tokens、typography、spatial/bento、motion 和 responsive 等转换。
确保所有更改都仅限于视觉层，并通过
```
cn()
```
完成所有 class 拼接。
验证该阶段： 该阶段组件的 diff 仅涉及 presentation——不得更改任何 state、hook、handler 或 API/mutation。对照该阶段的完成定义进行检查。 完成条件： 5 个阶段均已实施，并且每个阶段的完成定义均已满足。

3. 最终零回归检查。 根据审计的 logic-freeze 矩阵重新检查整个应用：所有被冻结的 hook、handler 和 API 调用均保持完整；build/typecheck 通过；视觉升级已在所有重构组件中生效。报告 presentation 方面的更改，并确认没有任何逻辑相关代码被移动。 完成条件： 5 个阶段均已完成，并且最终零回归验证通过——presentation 已升级，逻辑保持不变。