Skip to content

Some useful prompt for this project

SDGLBL edited this page Mar 28, 2025 · 1 revision

Summarizing history for continued next conversation.

Please provide a detailed yet concise summary of our conversation, focusing on key information for continuity. Include what we've done, what we're currently working on, which files are involved, and the next steps. Since previous tool-related memory will be lost in the next session, summarize the solutions provided so far. Additionally, specify which files should be read at the start of our next discussion to maintain context. Finally, outline the remaining tasks with clear instructions on how to complete them and include relevant examples as references.

Automation Research Summary

Now you need to research one or more of the following functionalities, focusing on their design concepts, dependent components, and implementation methods. The ultimate goal of this research is to produce a detailed yet accurate description that includes which functionalities were studied and which files are relevant. This summary will be used at the start of other new conversations to provide Claude with quick and precise understanding of key focus areas for seamless onboarding and immediate work initiation. Therefore, make sure to list all related files at the end of the summary with instructions for Claude to read them in one go for efficiency.

Directly reply with a summary without writing to any files.

The topics you need to investigate include:

- 

Draw Drawio Diagrams

Please clearly recreate this diagram using the mxGraph XML format of drawio

Multiple edits

I noticed that you cannot complete all the code in a single tool call. Therefore, you should break down the task into multiple steps. Create an editing plan, with the current optimal number being {{two}} times.

Submit code written by Claude.

please use git diff --color=never confirm your edition and use git commit your change remember follow my pre git style
you do not need dive into this project. just read git diff and write git commit

Submit the code I wrote.

please use git diff confirm your edition and use git commit your change rember follow my pre git style. 

Relase a new version

Then review all commits from the last release version up to now and use them as the changelog for the new release. Help me publish the new version.

Resume interrupted conversation.

git diff --staged --no-color | clp
You have actually already completed part of the code writing and folder creation, but because the execution was interrupted, please continue to complete the code you were working on. To help you continue, I've provided the git diff --staged --no-color information from the code you just wrote.

Directly paste the code into Artifact.

give me the code in a artifact i will past it in editor and run test then past the test result to you. you do not need call tool to write content anymore.

Fix test errors

You need to fix these test errors. You can run the test code using {test cmd} to confirm your fixes. I need you to first analyze the errors and tell me how to fix each one, then we'll fix them one by one. After fixing each error, you should pause to explain what the problem was and how you fixed it, then wait for my confirmation before continuing to the next fix.