Back to Details

build

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Build

构建

When to use

适用场景

  • Implementing a single task from a plan
  • Executing a clear, scoped behavioral change
  • Delivering one focused vertical slice
  • 实施计划中的单个任务
  • 执行明确、范围限定的行为变更
  • 交付一个聚焦的垂直切片

Process

流程

  1. Read the task, spec, and relevant code before editing.
  2. If the scope is vague or too large for one pass, stop and clarify or break it down.
  3. Work in the repo's normal git context.
  4. Implement the smallest useful slice that satisfies the task.
  5. If the task has several parts, work in small runnable steps and verify each step before continuing.
  6. Add tests when behavior changes, bugs are fixed, or interfaces change.
  7. Run the strongest project checks available: the full test suite when practical, plus any task-specific verification.
  1. 在编辑前阅读任务、规格说明和相关代码。
  2. 如果范围模糊或单次处理过大，请停止并澄清或拆分任务。
  3. 在仓库的常规git环境中开展工作。
  4. 实施满足任务要求的最小可用变更片段。
  5. 如果任务包含多个部分，请分小的可运行步骤进行，并在继续前验证每个步骤。
  6. 当行为变更、修复漏洞或接口变更时，添加测试。
  7. 运行项目可用的最严格检查：可行时运行完整测试套件，再加上任何任务特定的验证。

Verification

验证

  • The behavior matches the task or request
  • New or changed behavior is covered by tests where it matters
  • Tests pass
  • Task-specific verification passes
  • No unrelated scope was added
  • 行为符合任务或需求要求
  • 新的或变更的行为在关键环节有测试覆盖
  • 测试通过
  • 任务特定验证通过
  • 未添加无关范围的内容

Rules

规则

  • One task at a time.
  • Make the smallest safe change that fully solves the task.
  • Preserve contracts unless the task explicitly changes them. If a contract must change, call it out clearly.
  • Handle failure paths explicitly instead of leaving them implicit.
  • Do not bundle several independent changes into one generation when they can land as working steps.
  • If the request is vague, oversized, or mixes multiple tasks, stop and clarify or break it down.
  • Do not hide missing verification. If you could not run something important, say so.
  • Do not use this skill as an excuse for unrelated refactors.
  • 一次处理一个任务。
  • 做出能完全解决任务的最小安全变更。
  • 除非任务明确要求，否则保留现有契约。如果必须变更契约，请明确指出。
  • 显式处理失败路径，而非隐式忽略。
  • 当变更可以分步落地时，不要将多个独立变更合并为一次提交。
  • 如果需求模糊、范围过大或混合了多个任务，请停止并澄清或拆分任务。
  • 不要隐瞒未完成的验证。如果无法运行重要检查，请说明情况。
  • 不要将此技能作为无关重构的借口。