更新英文提示詞

src/prompts/templates_en/analyzeTask/index.md

@@ -1,51 +1,57 @@
-**Please strictly follow the guidelines below**
-
 ## Codebase Analysis
 
-### Task Summary
+After receiving the initial solution, complete the following checks and optimizations in sequence, and call the `reflect_task` tool at the end:
 
-{summary}
+1. **Structural Integrity Check**
 
-### Solution Concept
+   - Does it cover all requirements and constraints?
+   - Are module boundaries and interface definitions clear?
+   - Is the dependency graph reasonable and maintainable?
+   - Does the design conform to the project's core architectural patterns?
+   - Does it maintain the project's existing hierarchy and component divisions?
 
-{initialConcept}
+2. **Duplicate Functionality Detection and Sharing Assessment**
 
-## Technical Review Points
+   - Use precise search strategies:
+     - Use `codebase_search`, `read_file` or similar tools to search for similar functionality implementations
+     - Analyze the purpose and responsibilities of key components and utility classes
+   - Check if functionalities in the solution overlap with existing code or other modules
+   - If overlapping, determine:
+     - Whether to directly **reuse** existing components (evaluate applicability, extensibility)
+     - Or need to **refactor/abstract** into shared components (consider reuse costs and benefits)
+   - Clearly indicate the reasons for reuse decisions and their scope of impact
 
-Pay attention to opportunities for code reuse, avoid reimplementing existing functionality, and mitigate technical debt risks.
+3. **Performance and Scalability Assessment**
 
-### 1. Codebase Analysis
+   - Are there potential performance bottlenecks?
+   - How scalable is the design for future requirements?
+   - Have resource usage and system load been considered?
+   - Does the expansion strategy conform to existing project patterns?
 
-- Look for reusable components and similar implementations
-- Determine the appropriate location for the new functionality
-- Evaluate integration methods with existing modules
+4. **Consistency and Style Validation**
 
-### 2. Technical Strategy Evaluation
+   - Does it conform to the project's existing code style, naming, and architectural conventions
+     - Check naming convention consistency (camelCase, snake_case, etc.)
+     - Confirm method/function parameter and return value styles
+     - Check comment and documentation formats
+   - Does it follow project-specific design patterns and architectural decisions
+   - Are there violations of team best practices
+   - Does the UI/UX design match the current screen style
 
-- Consider modularity and scalability in the design
-- Assess the future compatibility of the proposal
-- Plan testing strategies and coverage
+5. **Architectural Integration Assessment**
 
-### 3. Risk and Quality Analysis
+   - How new features seamlessly integrate with the existing architecture
+   - Evaluate impact on existing modules and services
+   - Confirm backward compatibility is maintained
+   - Check if system boundaries and module encapsulation are protected
 
-- Identify technical debt and performance bottlenecks
-- Evaluate security and data integrity
-- Check error handling mechanisms
+6. **Optimization Suggestions**
+   - Based on the above checks, organize optimized answers
+   - Ensure suggestions are consistent with the existing architecture
+   - Provide specific code organization and integration strategies
+   - Call tool:
+     ```
+     reflect_task({ summary: 'Analysis Summary', analysis: <Analysis Results> })
+     ```
 
-### 4. Implementation Recommendations
-
-- Follow project architectural style
-- Recommend implementation methods and technology choices
-- Propose clear development steps
-
-{previousAnalysis}
-
-## Next Actions
-
-After completing the analysis, use the "reflect_task" tool to submit the final analysis, including:
-
-1. **Original Task Summary** - Keep consistent with the first stage
-2. **Complete Analysis Results** - Technical details, interface dependencies, implementation strategy, acceptance criteria
-
-Your analysis will determine the quality of the solution. Please comprehensively consider various technical factors and business constraints.
-**Using tools is strictly required.**
+**Now call `reflect_task`, strictly forbidden not to call the tool**

src/prompts/templates_en/analyzeTask/iteration.md

@@ -1,12 +1,12 @@
-## Iterative Analysis
+## Iteration Analysis
 
-Please compare with the previous analysis results:
+Please compare with previous analysis results:
 
 {previousAnalysis}
 
 Please identify:
 
-1. Resolved issues and the effectiveness of the solutions
-2. Remaining issues and their priorities
-3. How the new plan addresses unresolved issues
-4. New insights gained during the iteration
+1. Problems that have been resolved and the effectiveness of solutions
+2. Problems that still exist and their priorities
+3. How the new solution addresses unresolved issues
+4. New insights gained during the iteration process

src/prompts/templates_en/clearAllTasks/backupInfo.md

@@ -1 +1 @@
-A backup has been automatically created: `{{backupFile}}`
+Backup automatically created: `{{backupFile}}`

src/prompts/templates_en/clearAllTasks/cancel.md

@@ -1,7 +1,7 @@
 # Clear All Tasks Result
 
-## Operation Canceled
+## Operation Cancelled
 
-Clear operation not confirmed. To clear all tasks, set the confirm parameter to true.
+The clearing operation was not confirmed. To clear all tasks, please set the confirm parameter to true.
 
-⚠️ This action will delete all unfinished tasks and cannot be undone.
+⚠️ This operation will delete all incomplete tasks and cannot be undone.

src/prompts/templates_en/clearAllTasks/empty.md

@@ -1,5 +1,5 @@
 # Clear All Tasks Result
 
-## Operation Hint
+## Operation Notice
 
-There are no tasks in the system to clear.
+There are no tasks in the system that need to be cleared.

src/prompts/templates_en/clearAllTasks/success.md

@@ -2,4 +2,4 @@
 
 ## Operation Successful
 
-All unfinished tasks have been cleared.{backupInfo}
+All incomplete tasks have been cleared.{backupInfo}

src/prompts/templates_en/completeTask/index.md

@@ -1,17 +0,0 @@
-**Please strictly follow the guidelines below**
-
-## Task Completion Confirmation
-
-Task "{name}" (ID: `{id}`) was successfully marked as completed at {completionTime}.
-
-## Task Summary Requirement
-
-Please provide a summary for this completed task, including the following key points:
-
-1. Task goals and main achievements
-2. Key points of the implemented solution
-3. Main challenges encountered and their solutions
-
-**Important Note:**
-Please provide the task summary in the current response. After completing this task summary, please wait for explicit user instructions before proceeding with other tasks. Do not automatically start the next task.
-If the user requests continuous execution of tasks, please use the "execute_task" tool to start the next task.

src/prompts/templates_en/deleteTask/completed.md

@@ -1,5 +1,5 @@
 # Task Deletion Result
 
-## Operation Rejected
+## Operation Denied
 
-Task "{taskName}" (ID: `{taskId}`) is completed and cannot be deleted. Deleting completed tasks is not allowed.
+Task "{taskName}" (ID: `{taskId}`) has been completed. Deleting completed tasks is not allowed.

src/prompts/templates_en/deleteTask/notFound.md

@@ -2,4 +2,4 @@
 
 ## System Error
 
-Task with ID `{taskId}` not found. Please use the "list_tasks" tool to confirm a valid task ID before trying again.
+Task with ID `{taskId}` could not be found. Please use the "list_tasks" tool to confirm valid task IDs and try again.

src/prompts/templates_en/executeTask/complexity.md

@@ -10,6 +10,6 @@
 
 - Number of Dependencies: {dependenciesCount}
 
-### Handling Recommendations
+### Processing Recommendations
 
 {recommendation}

src/prompts/templates_en/executeTask/dependencyTasks.md

@@ -1,3 +1,3 @@
-## Dependency Task Completion Summaries
+## Dependency Tasks Completion Summary
 
 {{ dependencyTasks }}

src/prompts/templates_en/executeTask/index.md

@@ -27,12 +27,12 @@
 1. **Analyze Requirements** - Understand task requirements and constraints
 2. **Design Solution** - Develop implementation plan and testing strategy
 3. **Implement Solution** - Execute according to plan, handle edge cases
-4. **Test and Verify** - Ensure functional correctness and robustness
+4. **Test and Verify** - Ensure functionality correctness and robustness
 
 ## Quality Requirements
 
 - **Scope Management** - Only modify relevant code, avoid feature creep
 - **Code Quality** - Comply with coding standards, handle exceptions
-- **Performance Consideration** - Pay attention to algorithm efficiency and resource usage
+- **Performance Considerations** - Pay attention to algorithm efficiency and resource usage
 
-Start executing the task according to instructions. After execution, please directly use the "verify_task" tool for verification.
+Begin executing the task according to instructions, and use the "verify_task" tool for verification after completion.

src/prompts/templates_en/executeTask/relatedFilesSummary.md

@@ -1,5 +1,5 @@
 ## Related Files
 
-You can use the `update_task` tool to add related files to provide context during task execution.
+You can use the `update_task` tool to add related files to provide context when executing the task.
 
 {relatedFilesSummary}

src/prompts/templates_en/getTaskDetail/complatedSummary.md

@@ -1,4 +1,4 @@
-**Completed At:** {completedTime}
+**Completion Time:** {completedTime}
 
 **Completion Summary:**
 

src/prompts/templates_en/getTaskDetail/index.md

@@ -1,4 +1,4 @@
-## Full Task Details
+## Complete Task Details
 
 ### {name}
 
@@ -18,8 +18,8 @@
 
 {relatedFilesTemplate}
 
-**Created At:** {createdTime}
+**Creation Time:** {createdTime}
 
-**Updated At:** {updatedTime}
+**Update Time:** {updatedTime}
 
 {complatedSummaryTemplate}

src/prompts/templates_en/getTaskDetail/notFound.md

@@ -1,3 +1,3 @@
 ## Error
 
-Task with ID `{taskId}` not found. Please verify the task ID is correct.
+Task with ID `{taskId}` not found. Please verify that the task ID is correct.

src/prompts/templates_en/initProjectRules/index.md

@@ -1,81 +1,81 @@
-Please use the "process_thought" tool to consider the following questions
+Please use the "process_thought" tool to consider the following issues
 
-# Project Rules Initialization Guide
+# Project Standards Initialization Guide
 
 ## Purpose
 
-**This document is designed specifically for the AI Agent, not general developer documentation.**
-**A project specification file (rules.md) specifically for AI Agent operations MUST be generated.**
+**This document is specifically designed for AI Agents, not for general developer documentation.**
+**Must generate a project standards document (rules.md) exclusively for AI Agent operational use.**
 
 **Must focus on the following key objectives:**
 
-- Clearly define project-specific rules and limitations, prohibiting general development knowledge
-- Provide project-specific information required by the AI for task execution
-- Offer clear guidance for the AI's decision-making process
+- Clearly define project-specific rules and limitations, prohibit inclusion of general development knowledge
+- Provide project-specific information needed for AI to execute tasks
+- Provide clear guidance for AI decision-making processes
 
-**Mandatory Requirements:**
+**Mandatory requirements:**
 
-- The completed specification must enable the AI Agent to immediately understand which files must be referenced or modified
-- Clearly indicate multi-file 联动 modification requirements (e.g., modifying README.md requires simultaneous modification of /docs/zh/README.md)
-- Use imperative language to define rules, avoiding explanatory content
-- Do not explain project functionality, but rather how to modify or add features
-- Provide examples of what can and cannot be done
+- Completed standards must enable AI Agents to immediately understand which files must be referenced or modified
+- Clearly indicate multi-file coordination requirements (e.g., when modifying README.md, /docs/zh/README.md must be updated simultaneously)
+- Use imperative language to define rules, avoid explanatory content
+- Do not explain project functionality, but rather how to modify or add functionality
+- Please provide examples of what can be done and what cannot be done
 - Must **recursively** check all folders and files
 
-**Strictly Prohibited:**
+**Strictly prohibited:**
 
 - Including general development knowledge
-- Including general development knowledge already known to the LLM
+- Including general development knowledge already known to LLMs
 - Explaining project functionality
 
 ## Suggested Structure
 
-Please use the following structure to create the specification file:
+Please use the following structure to create the standards document:
 
 ```markdown
 # Development Guidelines
 
-## Heading
+## Title
 
-### Subheading
+### Subtitle
 
 - Rule one
 - Rule two
 ```
 
-## Content Guide
+## Content Guidelines
 
-The specification file should include, but is not limited to, the following content:
+The standards document should include but not be limited to the following:
 
-1. **Project Overview** - Briefly describe the project's purpose, tech stack, and core features
-2. **Project Architecture** - Explain the main directory structure and module division
-3. **Coding Standards** - Including naming conventions, formatting requirements, commenting rules, etc.
-4. **Feature Implementation Standards** - Mainly explain how to implement features and what to pay attention to
-5. **Framework/Plugin/Third-Party Library Usage Standards** - Usage rules for external dependencies
-6. **Workflow Standards** - Workflow guide, including workflow diagrams or data flows
-7. **Key File Interaction Standards** - Interaction rules for key files, specifying which file modifications require synchronization
-8. **AI Decision Standards** - Provide decision trees and priority judgment criteria for handling ambiguous situations
-9. **Prohibitions** - Clearly list practices that are forbidden
+1. **Project Overview** - Brief description of the project's purpose, technology stack, and core functionality
+2. **Project Architecture** - Description of main directory structure and module divisions
+3. **Code Standards** - Including naming conventions, formatting requirements, comment rules, etc.
+4. **Functionality Implementation Standards** - Mainly explaining how to implement functionality and points to note
+5. **Framework/Plugin/Third-party Library Usage Standards** - Usage standards for external dependencies
+6. **Workflow Standards** - Workflow guidelines, including workflow diagrams or data flow
+7. **Key File Interaction Standards** - Interaction standards for key files, which files need to be modified simultaneously
+8. **AI Decision-making Standards** - Provide decision trees and priority judgment criteria for handling ambiguous situations
+9. **Prohibited Actions** - Clearly list practices that are prohibited
 
-## Important Notes
+## Notes
 
 1. **AI Optimization** - The document will be provided as a prompt to the Coding Agent AI and should be optimized for prompts
-2. **Focus on Development Guidance** - Provide rules for ongoing development, not usage instructions
-3. **Specific Examples** - Provide concrete examples of "what should be done" and "what should not be done" whenever possible
-4. **Use Imperative Language** - Must use direct commands rather than descriptive language, reducing explanatory content
-5. **Structured Presentation** - All content must be presented in structured formats like lists, tables, etc., for easy AI parsing
-6. **Highlight Key Markers** - Use bold, warning markers, etc., to emphasize crucial rules and prohibitions
-7. **Remove General Knowledge** - Prohibit including general development knowledge known to the LLM, only include project-specific rules
+2. **Focus on Development Guidance** - Provide rules for ongoing development, not usage tutorials
+3. **Specific Examples** - Provide specific examples of "what should be done" and "what should not be done" whenever possible
+4. **Use Imperative Language** - Must use direct instructions rather than descriptive language, reduce explanatory content
+5. **Structured Presentation** - All content must be presented in structured formats such as lists, tables, etc., for easy AI parsing
+6. **Highlight Key Markings** - Use bold, warning markers, etc. to highlight key rules and taboos
+7. **Remove General Knowledge** - Prohibit including general development knowledge already known to LLMs, only include project-specific rules
 
-## Update Mode Guide
+## Update Mode Guidelines
 
-1. **Minimal Change** - When the user requests an update to the project rules, you should maintain existing rules unless necessary, modifying with the principle of minimal change.
-2. **Timeliness** - You should check if existing rules are still effective or outdated, as the user may have modified or removed relevant code. You must correct or remove corresponding rules.
-3. **Completeness** - You should check all folders and file contents of the existing project, as the user may have added or modified relevant code. You must supplement corresponding rules.
-4. **Autonomous Handling of Vague Requests**: When receiving a vague instruction like "update rules" without specific details, the AI **MUST** first attempt to autonomously analyze the current codebase, recent changes (if available), and existing `rules.md` content to infer potential update points. List these inferred points and their rationale during the `process_thought` stage before proposing specific changes. **Strictly prohibit** asking the user for clarification on vague update requests before performing this autonomous analysis.
+1. **Minimal Changes** - When users request updates to project rules, you should maintain existing rules unless necessary, with the principle of minimal changes
+2. **Timeliness** - You should check if existing rules are still beneficial or outdated, as users may have modified or removed relevant code, you must correct or remove corresponding rules
+3. **Completeness** - You should check all folders and file contents in the existing project, as users may have added or modified relevant code, you must supplement corresponding rules
+4. **Autonomous Handling of Ambiguous Requests**: When receiving ambiguous instructions such as "update rules" without specifying concrete content, the AI **must** first attempt to independently analyze the current codebase, recent changes (if available), and existing `rules.md` content to infer possible update points. List these inferred points and their rationale during the `process_thought` phase, then propose specific modification suggestions. **Strictly prohibited** from seeking clarification from users on ambiguous update requests before performing this autonomous analysis.
 
-Please create a file named rules.md based on the guidelines above and store it at: {rulesPath}
+Based on the above guidelines, create a file named rules.md and store it at: {rulesPath}
 
-**[AI Agent Action]** Now start calling the "process_thought" tool to think about how to write the specification file to guide the Coding Agent
-**[AI Agent Action]** After thinking, immediately edit the rules.md file. Calling the "analyze_task" tool is prohibited
-**[AI Agent Action]** Strictly prohibit not calling tools. The AI must autonomously complete the entire process from instruction receipt to execution unless encountering technical errors or unsolvable dependency conflicts. Do not interrupt the flow to seek user input unnecessarily.
+**[AI Agent Action]** Now start calling the "process_thought" tool to think about how to write standards document that guides the Coding Agent
+**[AI Agent Action]** After completing the thought process, immediately edit the rules.md file, prohibited from calling the "analyze_task" tool
+**[AI Agent Action]** Strictly forbidden not to call tools. The AI must independently complete the entire process from receiving instructions to implementing modifications, and should not interrupt the process to seek user input unless encountering technical errors or unresolvable dependency conflicts.

src/prompts/templates_en/listTasks/notFound.md

@@ -1,3 +1,3 @@
 # System Notification
 
-Currently, there are no {statusText} tasks in the system. Please query tasks with other statuses or first use the "split_tasks" tool to create the task structure before proceeding.
+There are currently no {statusText} tasks in the system. Please query other status tasks or first use the "split_tasks" tool to create task structures before proceeding with subsequent operations.

src/prompts/templates_en/listTasks/taskDetails.md

@@ -8,6 +8,6 @@
 
 **Dependencies:** {dependencies}
 
-**Created At:** {createAt}
+**Creation Time:** {createAt}
 
 {complatedAt}

src/prompts/templates_en/planTask/hasThought.md

@@ -1,4 +1,4 @@
-**Step 2: Must use "process_thought" to think through the answer (Directly using analyze_task is prohibited)**
+**Step Two: Must forcibly use "process_thought" to think about the answer (prohibited from directly using analyze_task)**
 
-1. **Mandatory Thought Process** - Must demonstrate a step-by-step reasoning process, including assumptions, validation, and adjustments
-2. Warning: You must first use the "process_thought" tool to think. Directly using analyze_task or providing a direct answer is strictly prohibited
+1. **Mandatory Thinking Process** - Must demonstrate step-by-step reasoning process, including assumptions, verification, and adjustments
+2. Warning: Must first use the "process_thought" tool to think, strictly prohibited from directly using analyze_task or answering directly

src/prompts/templates_en/planTask/index.md

@@ -1,62 +1,93 @@
-**Please strictly follow the guidelines below**
-
 ## Task Analysis
 
-{description}
+You must complete the following sub-steps in sequence, and at the end call the `analyze_task` tool to pass the preliminary design solution to the next stage.
 
-## Requirements and Constraints
+1. **Analysis Purpose**
 
-{requirements}
+   - Read and understand:
+     ```
+     Task Description: {description}
+     Task Requirements and Constraints: {requirements}
+     {tasksTemplate}
+     ```
+   - Confirm:
+     - Task objectives and expected outcomes
+     - Technical challenges and key decision points
+     - Integration requirements with existing systems/architecture
 
-{tasksTemplate}
+2. **Identify Project Architecture**
 
-## Analysis Guidelines
+   - View key configuration files and structures:
+     - Examine root directory structure and important configuration files (package.json, tsconfig.json, etc.)
+     - Analyze main directory organization and module divisions
+   - Identify architectural patterns:
+     - Identify core design patterns and architectural styles (MVC, MVVM, microservices, etc.)
+     - Determine the project's layered structure and module boundaries
+   - Analyze core components:
+     - Research main class/interface designs and dependencies
+     - Mark key services/utility classes and their responsibilities and uses
+   - Document existing patterns:
+     - Document discovered code organization methods and architectural regularities
+     - Establish deep understanding of the project's technology stack and architectural characteristics
 
-1. Determine the task's goals and expected outcomes
-2. Identify technical challenges and key decision points
-3. Consider potential solutions and alternatives
-4. Evaluate the pros and cons of each solution
-5. Determine if the task needs to be broken down into subtasks
-6. Consider integration requirements with existing systems
+3. **Collect Information**  
+   If there is any uncertainty or lack of confidence, **must do one of the following**:
 
-## Task Memory Retrieval
+   - Ask the user for clarification
+   - Use `query_task`, `read_file`, `codebase_search` or other similar tools to query existing programs/architecture
+   - Use `web_search` or other web search tools to query unfamiliar concepts or technologies  
+     Speculation is prohibited; all information must have traceable sources.
 
-Past task records are stored in **{memoryDir}**.
+4. **Check Existing Programs and Structures**
 
-When using the query tool, judge based on the following scenarios:
+   - Use precise search strategies:
+     - Use `read_file`, `codebase_search` or other similar tools to query existing implementation methods related to the task
+     - Look for existing code with functionality similar to the current task
+     - Analyze directory structure to find similar functional modules
+   - Analyze code style and conventions:
+     - Check naming conventions of existing components (camelCase, snake_case, etc.)
+     - Confirm comment styles and format conventions
+     - Analyze error handling patterns and logging methods
+   - Record and follow discovered patterns:
+     - Document code patterns and organizational structures in detail
+     - Plan how to extend these patterns in the design
+   - Determine if there is overlap with existing functionality, and decide whether to "reuse" or "abstract and refactor"
+   - **Do not** generate designs before checking existing code; must "check first, then design"
 
-- **Must Query (High Priority)**:
+5. **Task Type-Specific Guidelines**
 
-  - Involves modifying or extending existing functionality, requiring understanding of the original implementation
-  - Task description mentions referencing past work or existing implementation experience
-  - Involves internal system technical implementation or key components
-  - User requires memory query
+   Based on task characteristics, additionally consider the following specific guidelines:
 
-- **Can Query (Medium Priority)**:
+   - **Frontend/UI Tasks**:
 
-  - New functionality has integration needs with the existing system, but implementation is partially independent
-  - Functionality is standardized and needs to conform to system conventions
-  - Unsure if similar implementations already exist
+     - Prioritize examining existing UI component libraries and design systems
+     - Analyze page layout structures and component composition patterns
+     - Confirm style management methods (CSS modules, Styled Components, etc.)
+     - Understand state management and data flow patterns
 
-- **Can Skip (Low Priority)**:
-  - Completely new, independent functionality
-  - Basic setup or simple standard tasks
-  - User explicitly instructs not to reference past records
+   - **Backend API Tasks**:
 
-> ※ Querying memory helps understand past solutions, learn from successful experiences, and avoid repeating mistakes.
+     - Check API route structures and naming conventions
+     - Analyze request handling and middleware patterns
+     - Confirm error handling and response format standards
+     - Understand authorization/authentication implementation methods
 
-## Information Gathering Guide
+   - **Database Operations**:
+     - Analyze existing data access patterns and abstraction layers
+     - Confirm query building and transaction processing methods
+     - Understand relationship handling and data validation methods
+     - Check caching strategies and performance optimization techniques
 
-1. **Ask the User** - When you have questions about task requirements, ask the user directly
-2. **Query Memory** - Use the "query_task" tool to check if there are relevant tasks in past memory
-3. **Web Search** - When encountering terms or concepts you don't understand, use a web search tool to find answers
+6. **Preliminary Solution Output**
+   - Based on the above, write a "Preliminary Design Solution":
+     - Clearly mark **facts** (sources) vs **inferences** (selection basis)
+     - Prohibit vague statements; must be final deliverable content
+     - Ensure the solution is consistent with the project's existing architectural patterns
+     - Explain how to reuse existing components or follow existing patterns
+   - The process must be thought through step by step and organize thoughts; if the problem is too complex, utilize `process_thought` to think
+   - Call tool:
+     ```
+     analyze_task({ summary: <Task Summary>, initialConcept: <Initial Concept> })
+     ```
 
-## Next Steps
-
-⚠️ Important: Please read the rules in {rulesPath} before conducting any analysis or design ⚠️
-
-**Step 1: Decide whether to query memory based on the task description**
-
-- Determine if the task falls under a "Must Query" scenario. If so, use "query_task" to query past records first; otherwise, proceed directly to analysis.
-
-{thoughtTemplate}
+**Now start calling `analyze_task`, strictly forbidden not to call the tool**

src/prompts/templates_en/planTask/noThought.md

@@ -1,4 +1,4 @@
-**Step 2: Submit analysis results using analyze_task**
+**Step Two: Use analyze_task to submit analysis results**
 
-1. **Task Summary** - Goals, scope, challenges, and constraints
-2. **Initial Solution Concept** - Feasible technical solutions and implementation plans
+1. **Task Summary** - Objectives, scope, challenges, and constraints
+2. **Initial Solution Concept** - Viable technical solutions and implementation plans

src/prompts/templates_en/planTask/tasks.md

@@ -1,35 +1,17 @@
-## Existing Task Reference
+### Existing Task References
 
-### Completed Tasks
+#### Completed Tasks
 
 {completedTasks}
 
-### Unfinished Tasks
+#### Incomplete Tasks
 
 {unfinishedTasks}
 
-## Task Adjustment Principles
+#### Task Adjustment Principles
 
 1. **Completed Task Protection** - Completed tasks cannot be modified or deleted
-2. **Unfinished Task Adjustability** - Unfinished tasks can be modified based on new requirements
-3. **Task ID Consistency** - References to existing tasks must use the original ID
-4. **Dependency Integrity** - Avoid circular dependencies and dependencies on tasks marked for removal
+2. **Incomplete Task Adjustability** - Incomplete tasks can be modified based on new requirements
+3. **Task ID Consistency** - Must use original IDs when referencing existing tasks
+4. **Dependency Relationship Integrity** - Avoid circular dependencies, do not depend on tasks marked for removal
 5. **Task Continuity** - New tasks should form a coherent whole with existing tasks
-
-## Task Update Modes
-
-### 1. **Append Mode (append)**
-
-- Keep all existing tasks, only add new tasks
-- Applicable: Gradually expand functionality when the existing plan is still valid
-
-### 2. **Overwrite Mode (overwrite)**
-
-- Clear all existing unfinished tasks and use the new task list entirely
-- Applicable: Complete change of direction, existing unfinished tasks are no longer relevant
-
-### 3. **Selective Update Mode (selective)**
-
-- Selectively update tasks based on task name matching, retaining other existing tasks
-- Applicable: Partially adjust the task plan while retaining some unfinished tasks
-- How it works: Updates tasks with the same name, creates new tasks, retains other tasks

src/prompts/templates_en/processThought/complatedThought.md

@@ -1,6 +1,6 @@
 ## Thinking Complete
 
-Next, use "analyze_task" to submit the analysis results
+Next, use "analyze_task" to submit analysis results
 
-1. **Task Summary** - Goals, scope, challenges, and constraints
-2. **Initial Solution Concept** - Feasible technical solutions and implementation plans
+1. **Task Summary** - Objectives, scope, challenges, and constraints
+2. **Initial Solution Concept** - Viable technical solutions and implementation plans

src/prompts/templates_en/processThought/index.md

@@ -4,10 +4,10 @@
 
 **Tags:** {tags}
 
-**Axioms Used:** {axioms_used}
+**Principles Used:** {axioms_used}
 
 **Assumptions Challenged:** {assumptions_challenged}
 
-**Prohibitions:** You should prohibit all speculation. For any doubts, thoroughly review the relevant code or use web search tools to inquire.
+**Prohibitions:** You should prohibit all speculation, for any concerns please thoroughly review related code or use web search tools to query
 
 {nextThoughtNeeded}

src/prompts/templates_en/processThought/moreThought.md

@@ -1 +1 @@
-More thinking is needed, continue using the "process_thought" tool to think and find the answer
+More thinking is needed, continue using the "process_thought" tool to think and find answers

src/prompts/templates_en/queryTask/index.md

@@ -2,23 +2,23 @@
 
 ## Query Information
 
-- Query Term: {query}
+- Query term: {query}
 
 ## Task List
 
-The following tasks match the query:
+Below are tasks matching the query:
 
 {tasksContent}
 
 ## Pagination Information
 
-- Current Page: {page} / {totalPages}
-- Items Per Page: {pageSize}
-- Total Results: {totalTasks}
+- Current page: {page} / {totalPages}
+- Items per page: {pageSize}
+- Total results: {totalTasks}
 
 You can specify the page parameter to view more results.
 
-## Related Action Tips
+## Related Operation Tips
 
-- Use `get_task_detail {taskID}` to view full task details
+- Use `get_task_detail {taskID}` to view complete task details
 - Use `list_tasks` to view all tasks

src/prompts/templates_en/queryTask/notFound.md

@@ -2,14 +2,14 @@
 
 ## No Matching Results
 
-No tasks found matching "{query}".
+No tasks matching "{query}" were found.
 
 ### Possible Reasons:
 
-- The task ID you provided does not exist or is in the wrong format
+- The task ID you provided does not exist or is incorrectly formatted
 - The task may have been deleted
-- There might be a typo in the keywords
+- The keyword spelling may be incorrect
 - Try using shorter or similar keywords
-- The task list might be empty
+- The task list may be empty
 
-You can use the `list_tasks` command to view all existing tasks or search history with other keywords.
+You can use the `list_tasks` command to view all existing tasks or use other keywords to search the history.

src/prompts/templates_en/queryTask/taskDetails.md

@@ -2,4 +2,4 @@
 
 - Status: {taskStatus}
 - Description: {taskDescription}
-- Created At: {createdAt}
+- Creation Time: {createdAt}

src/prompts/templates_en/reflectTask/index.md

@@ -1,72 +1,48 @@
-**Please strictly follow the guidelines below**
+## Reflection Results
 
-## Solution Evaluation
+After receiving the solution and suggestions, conduct self-reflection and final confirmation, and submit the final results:
 
-### Task Summary
+1. **Requirements Alignment Check**
 
-{summary}
+   - Does the final solution fully satisfy user requirements and constraints?
+   - Are there any omissions or deviations from the original goals?
 
-### Analysis Results
+2. **Architectural Consistency Check**
 
-{analysis}
+   - Does the design follow the project's existing architectural patterns and design principles?
+   - Is it consistent with existing code style, naming conventions, and organizational structure?
+   - Does it appropriately utilize existing components rather than reimplementing them?
+   - Are new features properly integrated into the existing architecture?
+   - Is the clarity of module boundaries and responsibility divisions maintained?
 
-## Evaluation Points
+3. **Over-design Review**
 
-### 1. Technical Integrity
+   - Is unnecessary complexity introduced?
+   - Is there excessive feature splitting or abstraction?
 
-- Check for technical flaws and logical loopholes in the solution
-- Validate edge case and exception handling
-- Confirm data flow and control flow integrity
-- Assess the reasonableness of technology choices
+4. **Simplicity and Implementability**
 
-### 2. Performance and Scalability
+   - Is the design concise and practically implementable?
+   - Is there sufficient space for future iterations?
 
-- Analyze resource usage efficiency and optimization potential
-- Evaluate system load scalability
-- Identify potential optimization points
-- Consider future functional expansion possibilities
+5. **Feedback and Confirmation**
 
-### 3. Requirement Compliance
+   - If there are deficiencies or over-design, list "Items Needing Adjustment" and explain the reasons
+   - If everything is satisfactory, generate a "Completion Confirmation Report"
 
-- Verify the implementation status of functional requirements
-- Check compliance with non-functional requirements
-- Confirm the accuracy of requirement understanding
-- Evaluate user experience and business process integration
+6. **Task Splitting Architectural Considerations**
 
-## Decision Points
+   - Task splitting should consider existing architectural module boundaries and responsibility divisions
+   - Each subtask should clearly specify its integration points and dependencies with existing code
+   - Clearly mark which subtasks involve reusing existing code and which require new implementation
+   - Maintain task granularity consistency, avoid excessive splitting or uneven granularity
+   - Ensure that the task group after splitting still maintains overall architectural consistency
 
-Choose subsequent actions based on the evaluation results:
+7. **Submit Final Results**
+   - Adjusted final solution + reflection report
+   - Call tool:
+   ```
+   split_tasks( ... )
+   ```
 
-- **Found critical issues**: Use "analyze_task" to resubmit an improved solution
-- **Minor adjustments**: Apply these small improvements in the next execution step
-- **Solution sound**: Use "split_tasks" to decompose the solution into executable subtasks. If there are too many tasks or the content is too long, use the "split_tasks" tool multiple times, submitting only a small portion of tasks each time.
-
-## split_tasks Update Mode Selection
-
-- **append** - Keep all existing tasks and add new ones
-- **overwrite** - Clear unfinished tasks, keep completed ones
-- **selective** - Selectively update specific tasks, keep others
-- **clearAllTasks** - Clear all tasks and create a backup
-
-## Knowledge Transfer Mechanism
-
-1. **Global Analysis Result** - Link the complete analysis document
-2. **Task-Specific Implementation Guide** - Save specific implementation methods for each task
-3. **Task-Specific Verification Criteria** - Set clear verification requirements
-
-## Task Splitting Guide (Please strictly follow these rules)
-
-- **Atomicity**: Each subtask should be independently operable or testable
-- **Dependency**: If a task depends on others, mark the "dependencies" field
-- **Moderate Splitting**: Avoid over-granularity (too small) or over-consolidation (too large)
-- **Consolidate when necessary**: If the modifications are minor or not complex, integrate them appropriately with other tasks to avoid excessive tasks due to over-simplification
-- **Repeated Calls**: If too many tasks or long content prevents "split_tasks" from working correctly, use the tool multiple times, submitting only a small portion of tasks each time
-- **Simplify Tasks**: If adding only one task at a time still doesn't work, consider further splitting or simplifying the task while retaining core content
-- **JSON Format Note**:
-  - **No Comments**: JSON format itself does not support comments (e.g., `#` or `//`). Adding comments within JSON content will lead to parsing failures.
-  - **Escape Characters**: Special characters within JSON content, such as double quotes (`\"`) and backslashes (`\\\\`), must be properly escaped. Otherwise, they will be treated as illegal characters, causing parsing failures.
-
-**Serious Warning**: The parameters you pass each time you call split_tasks cannot exceed 5000 characters. If it exceeds 5000 characters, please call the tool multiple times to complete.
-
-**Now start calling the `split_tasks` or `analyze_task` tool**
-**Using tools is strictly required.**
+**Now start calling `split_tasks`, strictly forbidden not to call the tool**

src/prompts/templates_en/splitTasks/index.md

@@ -1,16 +1,16 @@
 ## Task Splitting - {updateMode} Mode
 
-## Splitting Strategies
+## Splitting Strategy
 
-1. **Decomposition by Functionality** - Independent testable sub-functions with clear inputs and outputs
-2. **Decomposition by Technical Layer** - Separate tasks along architectural layers, ensuring clear interfaces
-3. **Decomposition by Development Stage** - Core functionality first, optimization follows
-4. **Decomposition by Risk** - Isolate high-risk parts to reduce overall risk
+1. **Functional Decomposition** - Independent testable sub-functions with clear inputs and outputs
+2. **Technical Layer Decomposition** - Separate tasks along architectural layers, ensuring clear interfaces
+3. **Development Stage Decomposition** - Core functionality first, optimization features later
+4. **Risk-based Decomposition** - Isolate high-risk parts, reduce overall risk
 
 ## Task Quality Review
 
 1. **Task Atomicity** - Each task is small and specific enough to be completed independently
-2. **Dependencies** - Task dependencies form a Directed Acyclic Graph (DAG), avoiding circular dependencies
+2. **Dependencies** - Task dependencies form a directed acyclic graph, avoiding circular dependencies
 3. **Description Completeness** - Each task description is clear and accurate, including necessary context
 
 ## Task List
@@ -19,16 +19,16 @@
 
 ## Dependency Management
 
-- Use task names or task IDs to set dependencies
-- Minimize the number of dependencies, setting only direct predecessors
-- Avoid circular dependencies, ensuring the task graph is a DAG
-- Balance the critical path, optimizing potential for parallel execution
+- Dependencies can be set using task names or task IDs
+- Minimize the number of dependencies, only set direct prerequisite tasks
+- Avoid circular dependencies, ensure the task graph is directed and acyclic
+- Balance the critical path, optimize possibilities for parallel execution
 
 ## Decision Points
 
-- Found unreasonable task split: Re-call "split_tasks" to adjust
-- Confirmed task split is sound: Generate execution plan, determine priorities
+- If task splitting is found unreasonable: call "split_tasks" again to adjust
+- If task splitting is confirmed to be sound: generate execution plan, determine priorities
 
-**Serious Warning**: The parameters you pass each time you call split_tasks cannot exceed 5000 characters. If it exceeds 5000 characters, please call the tool multiple times to complete.
+**Severe Warning** Each time you call split_tasks, the parameters you pass cannot exceed 5000 characters. If it exceeds 5000 characters, please call the tool multiple times to complete
 
-**If there are remaining tasks, please continue calling "split_tasks"**
+**If there are remaining tasks, please continue to call "split_tasks"**

src/prompts/templates_en/toolsDescription/analyzeTask.md

@@ -1 +1 @@
-Deeply analyze task requirements and systematically check the codebase, evaluate technical feasibility and potential risks. If code is needed, use pseudocode format providing only high-level logic flow and key steps, avoiding complete code.
+Deeply analyze task requirements and systematically examine the codebase, assess technical feasibility and potential risks, if code needs to be provided use pseudocode format and only provide high-level logic flow and key steps avoiding complete code

src/prompts/templates_en/toolsDescription/clearAllTasks.md

@@ -1 +1 @@
-Clear unfinished tasks and reset the task list
+Clear incomplete tasks and reset the task list

src/prompts/templates_en/toolsDescription/completeTask.md

@@ -1 +0,0 @@
-Formally mark a task as completed, generate a detailed completion report, and update the dependency status of related tasks

src/prompts/templates_en/toolsDescription/deleteTask.md

@@ -1 +1 @@
-Delete unfinished tasks, but does not allow deleting completed tasks, ensuring the integrity of system records
+Delete incomplete tasks, but does not allow deleting completed tasks, ensuring the integrity of system records

src/prompts/templates_en/toolsDescription/executeTask.md

@@ -1 +1 @@
-Execute a specific task according to the predefined plan, ensuring the output of each step meets quality standards
+Execute specific tasks according to the predefined plan, ensuring the output of each step meets quality standards

src/prompts/templates_en/toolsDescription/getTaskDetail.md

@@ -1 +1 @@
-Get the complete detailed information of a task based on its ID, including unabridged implementation guides and verification criteria, etc.
+Retrieve complete detailed information of a task based on task ID, including untruncated implementation guides and verification criteria

src/prompts/templates_en/toolsDescription/initProjectRules.md

@@ -1 +1 @@
-Initialize project rules. Call this tool when the user requests to generate or initialize the project specification file, or if the user requests to change or update the project specification.
+Initialize project standards, call this tool when the user requests to generate or initialize a project standards document, also call this tool if the user requests to change or update project standards

src/prompts/templates_en/toolsDescription/listTasks.md

@@ -1 +1 @@
-Generate a structured task list, including complete status tracking, priority, and dependencies
+Generate structured task lists, including complete status tracking, priorities, and dependencies

src/prompts/templates_en/toolsDescription/planTask.md

@@ -1 +1 @@
-Initialize and detail the task flow, establish clear goals and success criteria, optionally reference existing tasks for continuation planning
+Initialize and plan task processes in detail, establish clear goals and success criteria, optionally reference existing tasks for continued planning

src/prompts/templates_en/toolsDescription/processThought.md

@@ -1 +1 @@
-Engage in a flexible and evolving thinking process by creating, questioning, validating, and refining ideas to progressively deepen understanding and generate effective solutions. When needing to gather data, analyze, or research, prioritize reviewing relevant project code; if such code doesn't exist, search the web rather than speculating. Set nextThoughtNeeded to false when thinking is sufficient, otherwise adjust total_thoughts to extend the process
+Conduct flexible and evolvable thinking processes, progressively deepen understanding and generate effective solutions through establishing, questioning, verifying, and correcting ideas. When encountering situations requiring data collection, analysis, or research, prioritize reviewing project-related code; if relevant code does not exist, query the web rather than speculate. Set nextThoughtNeeded to false when thinking is sufficient, otherwise adjust total_thoughts to extend the process

src/prompts/templates_en/toolsDescription/queryTask.md

@@ -1 +1 @@
-Search tasks by keyword or ID, displaying abbreviated task information
+Search for tasks based on keywords or ID, display abbreviated task information

src/prompts/templates_en/toolsDescription/reflectTask.md

@@ -1 +1 @@
-Critically review analysis results, evaluate solution completeness and identify optimization opportunities, ensuring the solution aligns with best practices. If code is needed, use pseudocode format providing only high-level logic flow and key steps, avoiding complete code.
+Critically review analysis results, assess solution completeness and identify optimization opportunities, ensure solutions conform to best practices, if code needs to be provided use pseudocode format and only provide high-level logic flow and key steps avoiding complete code

src/prompts/templates_en/toolsDescription/splitTasks.md

@@ -1,14 +1,14 @@
-Decompose complex tasks into independent subtasks, establishing dependencies and priorities.
+Decompose complex tasks into independent subtasks, establish dependencies and priorities.
 
 ## updateMode
 
-- **append**: Keep existing tasks and add new ones
-- **overwrite**: Delete unfinished tasks, keep completed ones
-- **selective**: Intelligently match and update existing tasks based on name
-- **clearAllTasks**: Clear all tasks and create a backup (preferred mode)
+- **append**: Retain existing tasks and add new tasks
+- **overwrite**: Delete incomplete tasks, retain completed tasks
+- **selective**: Intelligently match and update existing tasks based on task names
+- **clearAllTasks**: Clear all tasks and create a backup (preferably use this mode)
 
 ## Key Requirements
 
-- **Provide concise pseudocode**: Only provide high-level logic flow and key steps, avoid complete code
-- **Consolidate when necessary**: Simple modifications can be integrated with other tasks to avoid excessive task count
-- **Submit in batches**: If there are too many tasks, use the "split_tasks" tool with parameters not exceeding 5000 characters
+- **Provide concise pseudocode**: Only provide high-level logic flow and key steps avoiding complete code
+- **Integrate when necessary**: Simple modifications can be integrated with other tasks, avoid having too many tasks
+- **Submit in batches**: When there are too many tasks, use the "split_tasks" tool, parameters not exceeding 5000 characters

src/prompts/templates_en/toolsDescription/updateTask.md

@@ -1 +1 @@
-Update task content, including name, description and notes, dependent tasks, related files, implementation guide and verification criteria. Completed tasks only allow updating summary and related files
+Update task content, including name, description and notes, dependent tasks, related files, implementation guide, and verification criteria, completed tasks only allow updating summary and related files

src/prompts/templates_en/toolsDescription/verifyTask.md

@@ -1 +1,37 @@
-Comprehensively verify task completion, ensuring all requirements and technical standards are met without missing details
+## Verify Task
+
+Please comprehensively check and score according to the requirements in verificationCriteria,
+If you are missing or have forgotten the verificationCriteria content, please use `get_task_detail` to obtain it.
+
+Please score according to the following rules:
+
+### Verification Standards
+
+1. **Requirements Compliance(30%)** - Functionality completeness, constraint adherence, edge case handling
+2. **Technical Quality(30%)** - Architectural consistency, code robustness, implementation elegance
+3. **Integration Compatibility(20%)** - System integration, interoperability, compatibility maintenance
+4. **Performance Scalability(20%)** - Performance optimization, load adaptability, resource management
+
+### score Parameter Guidelines
+
+Provide overall score and rating, assessment of each standard, issues and suggestions, and final conclusion.
+
+**Must use the following format to provide scoring results (for system parsing):**
+
+```Scoring
+score: [number from 0-100]
+```
+
+### summary Parameter Guidelines
+
+If the score is equal to or greater than 80 points, please provide a task summary
+
+```
+summary: 'Task completion summary, concise description of implementation results and important decisions'
+```
+
+If the score is less than 80 points, please provide correction suggestions
+
+```
+summary: 'List task issues and correction suggestions'
+```

src/prompts/templates_en/updateTaskContent/emptyUpdate.md

@@ -2,4 +2,4 @@
 
 ## Operation Failed
 
-At least one field (name, description, notes, or related files) must be updated
+At least one field needs to be updated (name, description, notes, or related files)

src/prompts/templates_en/updateTaskContent/notFound.md

@@ -2,4 +2,4 @@
 
 ## System Error
 
-Task with ID `{taskId}` not found. Please use the "list_tasks" tool to confirm a valid task ID before trying again.
+Task with ID `{taskId}` not found. Please use the "list_tasks" tool to confirm valid task IDs and try again.

src/prompts/templates_en/updateTaskContent/success.md

@@ -4,6 +4,6 @@
 - **Description:** {taskDescription}
   {taskNotes}
 - **Status:** {taskStatus}
-- **Updated At:** {taskUpdatedAt}
+- **Update Time:** {taskUpdatedAt}
 
 {filesContent}

src/prompts/templates_en/verifyTask/index.md

@@ -1,44 +1,17 @@
 **Please strictly follow the guidelines below**
 
-## Task Verification
+## Task Completion Confirmation
 
-**Name:** {name}
+Task "{name}" (ID: `{id}`) has been successfully marked as completed.
 
-**ID:** `{id}`
+## Task Summary Requirements
 
-**Description:** {description}
+Please provide a summary of this completed task, including the following key points:
 
-**Notes:** {notes}
+1. Task objectives and main accomplishments
+2. Key points of the implemented solution
+3. Major challenges encountered and solutions
 
-## Verification Criteria
-
-{verificationCriteria}
-
-## Implementation Guide Summary
-
-{implementationGuideSummary}
-
-## Analysis Points
-
-{analysisSummary}
-
-## Verification Standards
-
-1. **Requirement Compliance (30%)** - Functional completeness, constraint adherence, edge case handling
-2. **Technical Quality (30%)** - Architectural consistency, code robustness, implementation elegance
-3. **Integration Compatibility (20%)** - System integration, interoperability, compatibility maintenance
-4. **Performance & Scalability (20%)** - Performance optimization, load adaptability, resource management
-
-## Reporting Requirements
-
-Provide overall score and rating, evaluation of each standard, issues and recommendations, and final conclusion.
-
-## Next Steps
-
-**Choose your next action based on the verification results:**
-
-- **Critical Errors**: Use the "plan_task" tool directly to replan the task
-- **Minor Errors**: Fix the issues directly
-- **No Errors**: Use the "complete_task" tool directly to mark as complete
-
-**Please decide your next action directly, do not ask the user**
+**Important Note:**
+Please provide the task summary in the current response. After completing this task summary, please wait for explicit instructions from the user before continuing with other tasks. Do not automatically start executing the next task.
+If the user requests continuous task execution, please use the "execute_task" tool to start executing the next task.

src/prompts/templates_en/verifyTask/noPass.md

@@ -0,0 +1,12 @@
+**Please strictly follow the guidelines below**
+
+## Verification Failed
+
+Task "{name}" (ID: `{id}`) verification failed
+
+### Correction Suggestions
+
+{summary}
+
+**Important Note:**
+Please attempt to fix the issues and call `verify_task` again to re-verify the task

src/prompts/templates_zh/planTask/index.md

@@ -41,7 +41,7 @@
 4. **檢查現有程式與結構**
 
    - 使用精確的搜索策略：
-     - 利用 `codebase_search` 查詢與任務相關的現有實現方式
+     - 利用 `read_file`、`codebase_search`或其他類似的工具查詢與任務相關的現有實現方式
      - 尋找與當前任務功能類似的現有代碼
      - 分析目錄結構尋找相似功能模組
    - 分析代碼風格與約定：