Back to Details

ixlab-engineer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

IxLab Engineer

IxLab工程师

Use this skill when implementation should follow IxLab artifacts instead of improvising directly from the prompt.
当实现需要遵循IxLab产出物，而非直接根据提示词即兴创作时使用此技能。

Read These Files

读取以下文件

  • design/system.md
    when present
  • design/entities/{entity}/ux.md
  • design/entities/{entity}/ui.md
  • relevant component specs under 
    design/components/
If docs MCP or equivalent documentation context is available, use it only when the implementation depends on framework, component-library, or accessibility API specifics.
Read the repository codebase before changing UI code.
  • design/system.md
    存在时读取
  • design/entities/{entity}/ux.md
  • design/entities/{entity}/ui.md
  • design/components/
    目录下的相关组件规范
如果有docs MCP或等效文档上下文，仅当实现依赖于框架、组件库或可访问性API的具体细节时使用。
修改UI代码前请先阅读仓库代码库。

Responsibilities

职责

  • translate artifacts into working code
  • preserve interaction intent and state coverage
  • align implementation with the design system
  • avoid generic visual drift during implementation
  • 将产出物转化为可运行代码
  • 保留交互意图和状态覆盖范围
  • 使实现与设计系统对齐
  • 避免实现过程中出现通用的视觉偏差

Workflow

工作流

  1. Inspect the existing codebase and identify the target files.
  2. Read the relevant IxLab artifacts before changing code.
  3. Decide whether the design entity covers a single surface, multiple pages, or a multi-step flow.
  4. Implement the interface and behavior described in the artifacts.
  5. If the entity spans multiple pages or steps, preserve the shared structure, naming, and state model from the unified artifact instead of re-scoping it page by page.
  6. Cover states explicitly:
    • default
    • empty
    • loading
    • error
    • success
    • disabled or permission-gated when relevant
  7. Reuse existing components when they fit the spec.
  8. If implementation details depend on framework or library behavior, consult docs MCP or equivalent official documentation context when available.
  9. If the artifacts are incomplete, call out the gap and make the narrowest reasonable assumption.
  10. If the user asks for only one slice of a multi-surface entity, state the partial scope clearly instead of silently rewriting the artifact boundary.
  1. 检查现有代码库，确定目标文件。
  2. 修改代码前阅读相关的IxLab产出物。
  3. 确定设计实体覆盖的是单一场景、多个页面还是多步骤流程。
  4. 实现产出物中描述的界面和行为。
  5. 如果实体跨多个页面或步骤，保留统一产出物中的共享结构、命名和状态模型，不要逐页重新界定范围。
  6. 明确覆盖所有状态：
    • 默认
    • 空状态
    • 加载中
    • 错误
    • 成功
    • 相关场景下的禁用或权限限制
  7. 符合规范时优先复用现有组件。
  8. 如果实现细节依赖于框架或库的行为，可查阅可用的docs MCP或等效官方文档上下文。
  9. 如果产出物不完整，指出差距并做出最窄范围的合理假设。
  10. 如果用户只需要多场景实体的某一部分，明确说明部分范围，不要静默改写产出物边界。

Quality Rules

质量规则

  • Do not treat the design artifact as optional.
  • Do not silently discard states or interaction rules.
  • Preserve consistency with the rest of the codebase.
  • Prefer small, reviewable changes over broad rewrites.
  • If the codebase and the artifact conflict, explain the conflict and resolve it deliberately.
  • Do not collapse a multi-page entity into an isolated page implementation without saying so.
  • Do not rename or fragment the entity model unless there is a deliberate reason.
  • Prefer official documentation over memory when using docs MCP for concrete implementation details.
  • 不要将设计产出物视为可选项。
  • 不要静默丢弃状态或交互规则。
  • 保持与代码库其余部分的一致性。
  • 优先选择小的、可评审的变更，而非大范围重写。
  • 如果代码库和产出物存在冲突，说明冲突并慎重解决。
  • 不要未经说明就将多页面实体压缩为独立页面实现。
  • 除非有合理理由，不要重命名或拆分实体模型。
  • 使用docs MCP查询具体实现细节时，优先参考官方文档而非记忆。

Finish Condition

完成条件

The implementation should feel traceable back to the IxLab artifacts instead of looking like a generic approximation.
实现应该可追溯到IxLab产出物，而非看起来像通用的近似实现。