ixlab-orchestrator

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

IxLab Orchestrator

IxLab 编排器

This is the main IxLab workflow skill.

Use it for design work that should result in persisted artifacts under

design/

这是IxLab核心工作流技能。

适用于需要将产出物持久化存储在

design/

目录下的设计工作。

Read These Files

需读取的文件

```
config/ixlab.config.md
```
```
agents/ux-researcher.md
```
```
agents/ui-designer.md
```
```
agents/design-critic.md
```
```
templates/entity-ux-analysis.md
```
```
templates/entity-ui-spec.md
```
```
templates/critic-review.md
```

templates/design-system.md

when

design/system.md

must be created or updated

relevant files under
```
references/
```
when the current phase needs them

Read files selectively, but keep the workflow order intact.

```
config/ixlab.config.md
```
```
agents/ux-researcher.md
```
```
agents/ui-designer.md
```
```
agents/design-critic.md
```
```
templates/entity-ux-analysis.md
```
```
templates/entity-ui-spec.md
```
```
templates/critic-review.md
```

当需要创建或更新

design/system.md

时，读取

templates/design-system.md

当前阶段需要时，读取
```
references/
```
目录下的相关文件

可选择性读取文件，但需保证工作流顺序不变。

Responsibilities

职责

identify the correct design entity
choose the execution mode
run the phases in the right order
persist the right artifacts
avoid unnecessary work when the brief is narrow or the mode is lighter
preserve a usable fallback path when native subagents are unavailable

识别正确的设计实体
选择执行模式
按正确顺序执行各阶段
持久化对应产出物
当需求brief范围较窄或模式较轻量时，避免不必要的工作
当原生子Agent不可用时，保留可用的降级路径

Execution Modes

执行模式

Resolve the mode from

config/ixlab.config.md

unless the user explicitly overrides it.

config/ixlab.config.md

is missing, default to:

```
mode: standard
```
```
critic_between_phases: true
```
```
critic_model: sonnet
```

full

mode, always force critic gates on even if the config says otherwise.

执行模式从

config/ixlab.config.md

中读取，除非用户显式覆盖配置。

若

config/ixlab.config.md

不存在，默认使用以下配置：

```
mode: standard
```
```
critic_between_phases: true
```
```
critic_model: sonnet
```

在

full

模式下，即便配置另有说明，也始终强制开启评审关卡。

quick

quick

Use when speed matters more than review depth.

resolve the design entity
produce a lean but complete UX artifact
create the UI artifact
skip critic passes unless the user asks for them or quality is obviously unsafe

适用于速度优先级高于评审深度的场景。

确定设计实体
生成精简但完整的UX产出物
创建UI产出物
跳过评审环节，除非用户要求或质量明显不达标

standard

standard

Default working mode.

run UX Researcher
run Design Critic when
```
critic_between_phases: true
```
run UI Designer
run Design Critic again when the config still enables it

默认工作模式。

运行UX Researcher
当
```
critic_between_phases: true
```
时运行Design Critic
运行UI Designer
若配置仍启用评审，则再次运行Design Critic

full

full

Use for complex, high-stakes, or ambiguous work.

run UX Researcher
run Design Critic with a mandatory gate
fix blocking issues before continuing
run UI Designer
run Design Critic with a mandatory gate
do not finish with a failed review unresolved

适用于复杂、高风险或需求不明确的工作。

运行UX Researcher
运行带强制关卡的Design Critic
继续推进前先修复阻塞性问题
运行UI Designer
运行带强制关卡的Design Critic
未解决评审失败的问题前不得结束工作

Workflow

工作流

Read
```
config/ixlab.config.md
```
when present.
Classify the request:
- page
- flow
- feature
- component
- cross-cutting system
Resolve the design entity slug.
Reuse existing artifacts if they already cover the entity.
Run the UX Researcher and write
```
design/entities/{entity}/ux.md
```
, or stop early if the inline feedback gate marks the brief as blocked.
If the mode requires critique, run the Design Critic before UI work and honor the configured
```
critic_model
```
when the runtime supports it.
If visual work requires a design system and
```
design/system.md
```
is missing or stale, create or update it first with the IxLab design-system skill.
Run the UI Designer and write
```
design/entities/{entity}/ui.md
```
, or stop early if its dependency check is blocked.
If the mode requires critique, review the UI artifact before finishing and do not continue past a
```
fail
```
verdict in
```
full
```
mode.
If the user also wants implementation, hand off to
```
skills/ixlab-engineer/SKILL.md
```
.

若存在
```
config/ixlab.config.md
```
则读取该文件。
对需求进行分类：
- page
- flow
- feature
- component
- cross-cutting system
确定设计实体的slug。
若现有产出物已覆盖该实体，可复用已有内容。
运行UX Researcher并写入
```
design/entities/{entity}/ux.md
```
，若inline反馈关卡判定需求被阻塞，则提前终止。
若模式要求评审，在UI工作开始前运行Design Critic，运行时支持的情况下遵循配置的
```
critic_model
```
。
若视觉设计需要设计系统，且
```
design/system.md
```
缺失或过时，优先使用IxLab design-system技能创建或更新该文件。
运行UI Designer并写入
```
design/entities/{entity}/ui.md
```
，若依赖检查被阻塞则提前终止。
若模式要求评审，结束前对UI产出物进行评审，
```
full
```
模式下出现
```
fail
```
判定时不得继续推进。
若用户同时需要实现，移交到
```
skills/ixlab-engineer/SKILL.md
```
。

Entity Resolution Rules

实体解析规则

Prefer one coherent design entity over several fragmented ones.
If the request naturally spans multiple entities, propose the split explicitly.
Do not force everything into a page-level artifact.
Use hyphenated slugs for artifact paths.
If the entity spans multiple screens or steps, keep one shared artifact unless there is a strong reason to split it.

优先选择一个连贯的设计实体，而非多个碎片化的实体
若需求天然覆盖多个实体，需明确提出拆分方案
不要强制将所有内容都归入页面级产出物
产出物路径使用连字符分隔的slug
若实体覆盖多个屏幕或步骤，除非有强拆分理由，否则保留一个共享产出物

Research Rules

调研规则

If optional research tools are disabled or unavailable, continue without them.
If external research is used, keep it tightly scoped and directly relevant.
Do not block the flow on optional integrations.
Load reference files progressively instead of dumping the whole
```
references/
```
directory into context.
If web search is used, prefer trusted sources and bring back only the insight needed for the current phase.
If Figma MCP is available, use it only when the design file materially clarifies the entity being designed.
If docs MCP is available, reserve it for implementation-facing questions or component-library constraints.

若可选调研工具被禁用或不可用，无需依赖工具继续推进
若使用外部调研内容，需严格限定范围，且与需求直接相关
不要因可选集成阻塞工作流
逐步加载参考文件，不要将整个
```
references/
```
目录都放入上下文
若使用网页搜索，优先选择可信来源，仅带回当前阶段所需的信息
若可用Figma MCP，仅当设计文件能实质性明确所设计的实体时使用
若可用docs MCP，仅用于面向实现的问题或组件库约束相关的查询

Output Contract

输出约定

Do not skip the UX artifact when UI work is requested.
Do not skip the design-system artifact when the UI work depends on missing system decisions.
Do not skip critic gates in
```
full
```
mode.
Do not finish with hidden assumptions that the next phase cannot see.

当用户要求UI工作时，不得跳过UX产出物
当UI工作依赖缺失的系统决策时，不得跳过设计系统产出物
```
full
```
模式下不得跳过评审关卡
不要携带下一阶段无法感知的隐藏假设结束工作

Finish Condition

完成条件

The orchestration is complete when the user has the artifacts needed for the requested phase, and the output is coherent enough for the next role to consume without guessing.

当用户已获得所请求阶段所需的全部产出物，且输出内容足够连贯，下一角色无需猜测即可使用时，编排工作即完成。