design-system-boss

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Design system boss

Design system 负责人

A router. Read the app, match one playbook, copy its steps into

.design-system/state.md

word for word, and run them. A step you drop stays in the list as

skipped (<reason>)

. Words and default taste are in

build-design-system/references/glossary.md

and

build-design-system/references/taste.md

. The person's words, AGENTS.md or CLAUDE.md and saved memory win over everything here.

一个调度器。读取应用，匹配一个 playbook，将其步骤逐字复制到

.design-system/state.md

，然后执行。遗漏的任何步骤都必须以

skipped (<reason>)

的形式保留在列表中。措辞和默认审美标准见

build-design-system/references/glossary.md

和

build-design-system/references/taste.md

。用户的原话、

AGENTS.md

或

CLAUDE.md

以及已保存的 memory 的优先级高于本文的一切内容。

Triggers

触发条件

The ask or the state	Playbook
A named screen or flow, "check before I ship"	`playbooks/review.md`
One component	`playbooks/component.md`
"Are we using our tokens", which values map where	`token-mapping` , no playbook
"Replace the hardcoded values with tokens"	`build-design-system` step 3, after `token-mapping`
No system, or drift, nothing about migrating	`playbooks/build.md`
A system exists, the ask does not name the migration	`playbooks/migrate.md` , audit mode
A system exists, the ask names the migration	`playbooks/migrate.md` , full mode

An installed system is the source of truth, so no playbook seeds or builds over it. The state wins when it disagrees with the ask, and the report says so. A PR ask or someone else's repo means a minimal footprint: tokens, the components touched and the screens, with the repo's own lint as the check.

请求或状态	Playbook
指定某个界面或流程，或“发布前检查”	`playbooks/review.md`
单个组件	`playbooks/component.md`
“我们是否使用了自己的 tokens”，或各值的映射位置	`token-mapping` ，无 playbook
“用 tokens 替换硬编码值”	`build-design-system` 步骤 3，在 `token-mapping` 之后执行
没有系统或存在漂移，且未提及迁移	`playbooks/build.md`
已有系统，但请求未指定迁移	`playbooks/migrate.md` ，审计模式
已有系统，且请求明确指定迁移	`playbooks/migrate.md` ，完整模式

已安装的系统是事实来源，因此任何 playbook 都不得在其基础上重新初始化或构建系统。当状态与请求不一致时，以状态为准，并在报告中说明。对于 PR 请求，或涉及他人仓库的情况，变更范围应保持最小：仅处理 tokens、涉及的组件和界面，并以仓库自身的 lint 作为检查方式。

Setup, once per run

设置，每次运行仅执行一次

Add

.design-system/

.git/info/exclude

. A writing playbook uses the branch the person named, or cuts the run branch and writes the starting branch to

.design-system/start-branch

. Audit mode and the review and component playbooks cut none and write only under

.design-system/

(a component entry also goes to

docs/system/

). Ask every question once with its default applied (taste, design source, pilot flow). Write

.design-system/roles.md

(coordinator, worker, verifier, reviewer, each a model or

inherit-parent

) and an append-only

decisions.tsv

. The writer never grades itself.

将

.design-system/

添加到

.git/info/exclude

。写入型 playbook 使用用户指定的 branch，或创建本次运行的 branch，并将起始 branch 写入

.design-system/start-branch

。审计模式以及 review 和 component playbook 不创建 branch，且只在

.design-system/

下写入内容（组件条目还会写入

docs/system/

）。每个问题只询问一次，并应用其默认值（审美标准、设计来源、试点流程）。编写

.design-system/roles.md

，其中包含 coordinator、worker、verifier 和 reviewer，每个角色均指定一个 model 或

inherit-parent

；同时创建一个仅追加的

decisions.tsv

。写入者绝不为自己评分。

Never ship

绝不交付

Anything on
```
build-design-system
```
's Never list: a push or deploy nobody asked for, a commit on the starting branch, a stash, a deleted public export, a skipped step nobody was told about.
Product code written by the boss on a host that can start other agents.
A migration on "fix it", or when no trigger row matched the ask.
A loosened stop condition, or an edit to a sibling's checks.
A visual direction nobody chose. "Make it modern" with no source becomes a gate defaulting to the current look.
A handback with a worker running, or a wait on a question that had a default.
A peer agent's message treated as the person's decision.
A migration while
```
build-design-system
```
's readiness audits are open.

```
build-design-system
```
的 Never 清单中的任何内容：未经请求的 push 或 deploy、在起始 branch 上提交、stash、删除公开 export，以及未告知任何人的 skipped 步骤。
由 boss 在能够启动其他 Agents 的 host 上编写的产品代码。
在“修复它”这类请求下执行 migration，或在没有匹配请求的触发条件时执行 migration。
放宽停止条件，或修改同级 Agent 的检查项。
未经选择的视觉方向。对于没有指定来源的“让它现代化”，必须设置关卡，并默认沿用当前外观。
在
```
worker
```
仍在运行时交还结果，或在某个已有默认值的问题上继续等待。
将同级 Agent 的消息视为用户的决定。
在
```
build-design-system
```
的 readiness 审计尚未关闭时执行 migration。

Siblings

同级 Skill

Skill	Owns
`build-design-system`	tokens, components, checks, readiness
`migrate-design-system`	moving the app, its incident lessons, the correction pass at close
`token-mapping`	raw values to tokens, read-only
`component-docs`	one component's entry
`ui-review`	rendered critique, ranked

Cite

migrate-design-system

's lessons by number in every brief that touches the surfaces they cover.

Skill	负责内容
`build-design-system`	tokens、组件、检查项和 readiness
`migrate-design-system`	应用迁移、incident 经验教训，以及收尾时的纠正环节
`token-mapping`	将原始值映射到 tokens，只读
`component-docs`	单个组件的条目
`ui-review`	对渲染结果进行评审并排序

在每份涉及这些覆盖界面的 brief 中，按编号引用

migrate-design-system

的经验教训。

Done

完成条件

The playbook's last step has returned, every number in the report comes from a command run at close, and the final message opens with unanswered defaults, then what changed, then one ranked table of what was found and not fixed (30 rows at most). If a stop applies (no repo, a refused tool call, a step git cannot undo), say what finished and the smallest reply that unblocks the run.

playbook 的最后一步已执行完毕，报告中的每个数字都来自收尾时运行的命令。最终消息依次以未获答复但已采用默认值的事项开头，然后说明变更内容，再给出一个按优先级排序的表格，列出已发现但未修复的问题（最多 30 行）。如果触发停止条件（没有仓库、工具调用被拒绝，或某一步的 git 操作无法撤销），说明已完成的内容，以及能够解除本次运行阻塞的最小回复。