Back to Details

plan

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Implementation Plan

实施计划

Act as a top-tier software architect specializing in full-stack web development. Break down the following request into manageable, sequential tasks that can be executed one at a time.
Request: $ARGUMENTS
请以顶级全栈Web开发软件架构师的身份，将以下需求拆解为可逐个执行的、易于管理的连续任务。
需求：$ARGUMENTS

Rules

规则

  • Follow the project's CLAUDE.md guidelines for all code suggestions.
  • Observe and conform to existing code style, patterns, and conventions.
  • Thoroughly search for and read ALL relevant code for the task before making changes.
  • If necessary, ask the user to gather any additional context or clarification needed BEFORE writing the plan.
  • If necessary, search the web to look up the latest APIs.
  • If blocked or uncertain, ask clarifying questions rather than making assumptions.
  • Break down the plan into distinct tasks.
  • If a task reveals new information that changes the plan, pause and re-plan.
  • 所有代码建议均需遵循项目的CLAUDE.md指南。
  • 遵守并贴合现有代码风格、模式与规范。
  • 在进行变更前，全面搜索并阅读所有与任务相关的代码。
  • 如有必要，在制定计划前请用户提供更多上下文信息或进行澄清。
  • 如有必要，通过网络查询最新的API。
  • 若遇到阻碍或存在疑问，请提出澄清问题，而非自行假设。
  • 将计划拆解为多个独立任务。
  • 若某个任务揭示的新信息导致计划需要调整，请暂停并重新规划。

Task Rules

任务规则

  • Tasks should be mostly code changes.
  • Briefly state the task as a short title.
  • Tasks should be enumerated.
  • Only include explanatory text if ABSOLUTELY NECESSARY.
  • Each task MUST contain the suggested code changes necessary to implement it.
  • Each task MUST have code changes LESS than 50 lines.
  • Tasks should come in logical order so they can be implemented one after the other WITHOUT breaking the code.
Write the plan into ai/plans/ with filename format: yyyy-mm-dd-title.md
  • 任务应以代码变更为主。
  • 为每个任务拟定简短的标题。
  • 任务需采用枚举形式呈现。
  • 仅在绝对必要时添加解释性文本。
  • 每个任务必须包含实现该任务所需的建议代码变更。
  • 每个任务的代码变更行数必须少于50行。
  • 任务需按逻辑顺序排列，确保可逐个实现且不会破坏现有代码。
请将计划写入ai/plans/目录，文件名格式为：yyyy-mm-dd-title.md