w-build

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Use an existing plan or a sufficiently clear implementation request. Read repository instructions, affected README/scripts, matching rules and skills, and technical docs. Resolve consequential decisions from

PRODUCT.md

and matching docs; ask a human for product scope, secrets, or destructive operations. Do not commit.

Inspect the working tree and identify the files owned by this task. State the acceptance conditions; preserve unrelated changes.
Implement one complete slice using existing packages and patterns. Change owning schemas and run documented generators instead of editing generated clients or migrations.
Run the smallest existing check for this change. A reproducible logic defect should have a regression check; use TDD when requested or required by the repository, not as a ritual for prose edits. Never the full pre-push suite (
```
/w-ship
```
owns that).
Investigate failed checks before building dependent work. Separate regressions caused here from pre-existing or environmental failures; never weaken checks to obtain a pass.
If behavior, commands, or conventions changed, update matching MDX and nearest README (
```
PRODUCT.md
```
only if product facts changed); otherwise one line why not.

使用已有计划或足够明确的实施需求。阅读仓库说明、受影响的 README/scripts、对应的规则和 skill，以及技术文档。根据

PRODUCT.md

和对应文档解决关键决策；涉及产品范围、secrets 或破坏性操作时向人工确认。不要执行 commit。

检查工作区，识别本任务负责的文件。明确验收条件；保留无关改动。
使用现有 packages 和模式实现一个完整切片。应修改源头 schema 并运行文档中规定的生成器，而不是直接编辑生成的客户端或 migration。
运行此次改动对应的最小现有检查。可复现的逻辑缺陷应有回归检查；仅在用户要求或仓库规则明确要求时使用 TDD，不要将其机械地应用于文档编辑。绝不运行完整的 pre-push 检查套件（该流程由
```
/w-ship
```
负责）。
在构建依赖此改动的工作之前调查失败的检查。区分由此处改动引起的回归与已有或环境导致的失败；绝不能通过削弱检查来通过验证。
如果行为、命令或约定发生变化，更新对应的 MDX 和最近的 README（仅当产品事实发生变化时才更新
```
PRODUCT.md
```
）；否则用一行说明无需更新的原因。