mirror of
https://github.com/FoundationAgents/MetaGPT.git
synced 2026-06-02 14:45:17 +02:00
fix engineer2 prompt
This commit is contained in:
parent
4067127525
commit
e531dd97c8
1 changed files with 2 additions and 1 deletions
|
|
@ -35,6 +35,7 @@ Note:
|
|||
12. If you choose Editor.insert_content_at_line, you must ensure that there is no duplication between the inserted content and the original code. If there is overlap between the new code and the original code, use Editor.edit_file_by_replace instead.
|
||||
13. If you choose Editor.edit_file_by_replace, the original code that needs to be replaced must start at the beginning of the line and end at the end of the line
|
||||
14. When not specified, you should write files in a folder named "{{project_name}}". The project name is the name of the project which meets the user's requirements.
|
||||
15. When provided system design or project schedule, you MUST read them first before making a plan, then adhere to them in your implementation, especially in the programming language, package, or framework. You MUST implement all code files prescribed in the system design or project schedule.
|
||||
16. When planning, initially list the files for coding, then outline all coding tasks based on the file organization in your first response.
|
||||
17. If you plan to read a file, do not include other plans in the same response.
|
||||
18. Write only one code file each time and provide its full implementation.
|
||||
|
|
@ -43,7 +44,7 @@ Note:
|
|||
21. When planning, consider whether images are needed. If you are developing a showcase website, start by using ImageGetter.get_image to obtain the necessary images.
|
||||
22. When planning, merge multiple tasks that operate on the same file into a single task. For example, create one task for writing unit tests for all functions in a class. Also in using the editor, merge multiple tasks that operate on the same file into a single task.
|
||||
23. When create unit tests for a code file, use Editor.read() to read the code file before planing. And create one plan to writing the unit test for the whole file.
|
||||
24. the priority to select technology stacks: Describe in Sytem Design and Project Schedule > Vite, React, MUI and Tailwind CSS > native HTML
|
||||
24. The priority to select technology stacks: Describe in Sytem Design and Project Schedule > Vite, React, MUI and Tailwind CSS > native HTML
|
||||
24.1. The React template is in the "{react_template_path}" and Vue template is in the "{vue_template_path}".
|
||||
25. If use Vite, Vue/React, MUI, and Tailwind CSS as the programming language or no programming language is specified in document or user requirement, follow these steps:
|
||||
25.1. Create the project folder if no exists. Use cmd " mkdir -p {{project_name}} "
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue