using-superpowers

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Superpowers Workflow

超级能力工作流

When to use this skill

何时使用该Skill

  • Always-on: This is the master orchestrator for all development work.
  • Before writing any code (Planning & Design).
  • During implementation (TDD & Logic).
  • After completion (Verification & Review).
  • 全程适用:这是所有开发工作的核心编排工具。
  • 编写任何代码之前(规划与设计阶段)。
  • 实现过程中(测试驱动开发与逻辑编写)。
  • 完成开发之后(验证与评审阶段)。

Workflow (The "Superpowers" Way)

工作流(“超级能力”模式)

1. Brainstorming & Design

1. 头脑风暴与设计

  • Socratic Refinement: Don't jump into code. Ask questions to tease out a full spec.
  • Chunked Validation: Present the design in digestible parts for feedback.
  • Plan First: Output a detailed implementation plan before touching source files.
  • 苏格拉底式细化:不要急于写代码,先通过提问梳理出完整的需求规格。
  • 分块验证:将设计拆分为易于理解的模块以获取反馈。
  • 先规划再动手:在接触源文件之前,输出详细的实现计划。

2. Implementation Loop (RED-GREEN-REFACTOR)

2. 实现循环(红-绿-重构)

  • Red: Write a failing test for the next bite-sized task.
  • Green: Write the minimal code needed to pass the test.
  • Refactor: Clean up the code while keeping it functional.
  • Commit early: Small, meaningful commits for every task.
  • :为下一个小型任务编写一个会失败的测试用例。
  • 绿:编写刚好能通过测试的最简代码。
  • 重构:在保持功能正常的前提下优化代码。
  • 尽早提交:为每个任务提交小型且有意义的代码版本。

3. Verification & Review

3. 验证与评审

  • Evidence over Claims: Prove it works with logs, screenshots, or test results.
  • Systematic Debugging: Use root-cause analysis if something fails.
  • Final Walkthrough: Summarize what was accomplished and how it's verified.
  • 用证据说话:通过日志、截图或测试结果证明功能可用。
  • 系统化调试:如果出现问题,使用根本原因分析方法排查。
  • 最终走查:总结已完成的工作以及验证方式。

Core Philosophies

核心理念

  • TDD (Test-Driven Development): Tests are not an afterthought; they are the blueprint.
  • YAGNI (You Aren't Gonna Need It): Do not over-engineer. Focus on the spec.
  • DRY (Don't Repeat Yourself): Keep the codebase clean and maintainable.
  • Composable Skills: Always check
    .agent/skills/
    for relevant tools (e.g.,
    handling-errors
    ,
    deployment-guard
    ).
  • TDD(测试驱动开发):测试不是事后补充,而是开发的蓝图。
  • YAGNI(你不会需要它):不要过度设计,专注于需求规格。
  • DRY(不要重复自己):保持代码库整洁且易于维护。
  • 可组合Skill:始终查看
    .agent/skills/
    目录以获取相关工具(例如
    handling-errors
    deployment-guard
    )。

Instructions for the Agent

给Agent的指令

  1. Check Skills FIRST: Before executing ANY plan, scan
    .agent/skills/
    for tools that can automate or safeguard your work.
  2. Explicit Verification: Never report a task as "done" without running a verification command (e.g.,
    npm test
    ,
    grep
    , or a custom script).
  3. Proactive planning: If a task is complex, update
    task.md
    and
    implementation_plan.md
    IMMEDIATELY.
  1. 先检查Skill:在执行任何计划之前,扫描
    .agent/skills/
    目录,寻找可以自动化或保障工作的工具。
  2. 明确验证:在未运行验证命令(例如
    npm test
    grep
    或自定义脚本)的情况下,绝不要报告任务“已完成”。
  3. 主动规划:如果任务复杂,请立即更新
    task.md
    implementation_plan.md
    文件。

Resources

资源

  • See BRAINSTORMING.md
  • See TDD-GUIDE.md
  • 查看BRAINSTORMING.md
  • 查看TDD-GUIDE.md