AI Prompts for Resolving Incorrect Edit Locations

Please review the following .cursorrules file: [PASTE CONTENT]. Identify any rules that may not be followed correctly and explain the potential impact of these misunderstandings on file edits. Additionally, provide suggestions on how to correct these issues to ensure proper adherence to the rules. Your response should be detailed, covering specific rules and their implications for project structure and file management.

Please provide a detailed list of all currently open files in the project. For each file, explain its role and purpose within the overall project structure. Additionally, identify any potential issues or areas of confusion regarding how these files interact with one another and contribute to the project's functionality. This information will help clarify the project's organization and ensure that all components are understood correctly.

Please analyze the recent changes made in the project and provide a detailed list of the last five modifications. For each change, include the file name, the nature of the change, and the date it was made. Additionally, identify any changes that appear to have been applied to the wrong file, and explain why they might be incorrect. Format your response in a clear table with columns for 'Change Description', 'File Name', 'Date', and 'Potential Issues'.

Please evaluate the current project tree structure for [PROJECT NAME]. Describe the hierarchy of the project components, including key folders and files, and explain how they relate to each other. Identify any specific areas where you feel there may be a loss of context or clarity, and suggest potential improvements to enhance understanding and navigation within the project. Your response should be detailed and structured to provide a comprehensive overview.

Please review the task we just completed and identify the specific rules that should have been applied from the .cursorrules file. Provide a detailed analysis of each relevant rule, explaining how it relates to the task and whether it was followed correctly. If any rules were not adhered to, outline the implications of this oversight and suggest how to improve adherence in future tasks. Format your response as a structured report with headings for each rule discussed.

Identify the incorrect change made in [FILE NAME] and provide a detailed explanation of why this error occurred. After that, revert the change in [FILE NAME] to restore it to its original state. Next, apply the correct change to the intended file, [INTENDED FILE NAME], ensuring that the modifications align with the project's overall structure and requirements. Finally, summarize the steps taken to correct the error and prevent similar issues in the future.

Please clarify the role of each open file in the project. For each file, provide a brief description of its purpose, how it contributes to the overall structure, and any specific responsibilities it has within the project. Additionally, indicate which files should be modified based on their intended roles and explain why those changes are necessary. Format your response as a list, with each file clearly labeled and its role detailed.

Please analyze the contents of the .cursorrules file and the project tree structure. Confirm your understanding of the project organization by identifying where each type of change should be applied. Provide a detailed summary that outlines the purpose of each section within the project tree and how it relates to the rules defined in the .cursorrules file. Include any recommendations for improving clarity or organization based on your analysis.

Please reapply the last change made to the project, ensuring it is applied to the correct file this time. Provide a detailed explanation of your reasoning for selecting that specific file, including any relevant context about the project's structure and how this change impacts the overall functionality. Additionally, outline any potential implications or considerations that should be kept in mind when making this change. Format your response as a clear step-by-step guide that I can follow.

Please reset your context and reload the project tree for the current project. After doing so, confirm your understanding of the project layout by providing a detailed overview of the structure, including the main components, their relationships, and any key files or directories that are essential for the project's functionality. Additionally, highlight any potential areas of confusion or complexity within the structure that may need further clarification.

Please provide a detailed summary of all the files edited during the last session. For each file, confirm whether the edits were applied correctly and provide an explanation for each confirmation. Include the file names, specific changes made, and the rationale behind why those changes were necessary. Additionally, highlight any potential impacts these edits may have on the overall project structure and functionality.

Please execute all relevant tests for the project to verify that the recent changes have not introduced any errors. Provide a detailed summary of the test results, including which tests were run, any errors or failures encountered, and recommendations for addressing any issues. Additionally, include the overall status of the project after the tests have been completed, highlighting any areas that may require further attention or review.

Please simulate the scenario that led to the original incorrect edit in the project structure. Describe the steps taken during the simulation and provide a detailed account of the results observed. Confirm whether the issue still occurs or if it has been resolved, and include any relevant data or output that demonstrates the current state of the project structure. Ensure that your response is clear and structured, allowing for easy understanding of the resolution process.

Please validate the compliance of all recent changes against the .cursorrules file. Identify and list any deviations you find, providing specific details about each one. For each deviation, confirm whether it has been resolved or if further action is needed. Additionally, summarize the overall compliance status and any recommendations for ensuring adherence to the rules in future updates.

Please provide a comprehensive change log that details all modifications made during this session. For each change, confirm that it aligns with the intended project structure and explain how it contributes to the overall goals of the project. Include specific examples of changes, the rationale behind them, and any potential impacts on the project's functionality or organization. Format the log in a clear and organized manner, with headings for each change and a summary at the end.

Draft a new rule for the .cursorrules file that clarifies the roles of different files within the project structure and specifies the locations where edits should be made. The rule should include definitions for each file type, such as [FILE TYPE 1], [FILE TYPE 2], and [FILE TYPE 3], and outline the responsibilities associated with each. Additionally, provide guidance on how to handle edits, including which files should be modified for specific changes and any best practices to follow. Ensure the final text is clear, concise, and formatted for easy implementation.

Create a comprehensive session checklist to ensure a clear understanding of the project structure before starting any work. The checklist should include specific steps such as reviewing the project hierarchy, confirming the purpose of each component, and identifying key dependencies. Additionally, include preventive measures to avoid incorrect edits, such as verifying the latest changes with version control and consulting documentation or team members for clarification. Format the checklist in a clear, actionable way with bullet points for easy reference.

Please add a descriptive comment at the header of each file in the project. Each comment should clearly outline the role of the file, its purpose within the overall project structure, and any specific constraints or guidelines for making edits to that file. Ensure that the comments are concise yet informative, ideally one to two sentences long. Format the comments consistently across all files, and provide the exact text for each comment that should be inserted.

Please create a comprehensive guideline document for the specific tasks related to [PROJECT NAME]. The document should outline which files need to be edited for each task, including the purpose of each file and any specific instructions for modifications. Additionally, include examples of the type of changes that should be made and any best practices to follow. Format the guidelines in a clear, organized manner with headings and bullet points for easy reference.

Create a detailed protocol for refreshing context during long project sessions. The protocol should outline specific steps to take at regular intervals, such as every [TIME INTERVAL], to ensure that the project structure remains clear and organized. Include methods for verifying the project structure, such as checking for consistency in file naming conventions, ensuring all necessary files are present, and confirming that the directory hierarchy is logical. Additionally, suggest ways to document any changes made during these refresh intervals to maintain clarity throughout the project lifecycle.