AI Prompts for Ensuring Correct File Modifications

Please help me identify any misplaced changes in my project. I recently modified several files, and I need a comprehensive list of all the files I altered along with an explanation for why I chose those specific locations. Additionally, highlight any discrepancies between my modifications and the intended project file structure. Provide suggestions on how to correct any issues and ensure that the project adheres to the proper organization.

Analyze the dependencies between the following files: [LIST FILES]. Provide a detailed explanation of how changes in each file can impact the others, including specific examples of potential issues that may arise from these interactions. Additionally, identify any incorrect assumptions that may have been made regarding the relationships between these files and suggest ways to correct them. Format your response in a structured manner, with clear headings for each file and its related dependencies.

Given the following file path structure: [PASTE STRUCTURE], please analyze it and confirm your understanding of the layout. Identify any potential misinterpretations or errors in the paths. Additionally, provide a brief explanation of the purpose of each directory and file within this structure, highlighting any critical components that are essential for project functionality.

Please evaluate the last set of changes made to the project. For each edit, describe its purpose and explain how it contributes to the overall structure of the project. Additionally, confirm whether each change aligns with the project's intended goals and organization. Provide a summary of any inconsistencies or areas that may need further adjustment to ensure coherence and clarity in the project structure.

Given the following file layout: [PASTE LAYOUT], please explain how you would assess the project structure to identify where changes need to be made. Discuss the criteria you would use to evaluate the organization of the files and folders, and highlight any common misconceptions that might arise regarding the project structure. Additionally, provide examples of potential changes that could improve the clarity and functionality of the project layout.

Please review the changes made in the file [FILE NAME] and identify why these edits were misplaced. Provide a detailed explanation of the implications of editing this file instead of the intended one. Then, move the changes to the correct file, [CORRECT FILE NAME], and summarize the adjustments made. Ensure that the final structure is clear and that the code functions as intended in the correct file.

For each file in the following list: [LIST FILES], provide a detailed description of its specific role and purpose within the project. Include information on how each file interacts with others and any dependencies that may exist. Additionally, outline best practices for making future changes while respecting the established roles of these files. Format your response in a clear and organized manner, ensuring that it is easy to reference for ongoing development.

Please revert the changes made to [FILE NAME] and apply them to [CORRECT FILE NAME] instead. Explain the reasoning behind this new location and why it is more appropriate for the changes. Include details about how the structure of the project supports this decision and any potential impacts on functionality or organization. Additionally, provide a brief overview of how this adjustment aligns with best practices for project structure.

Please review my recent edits and align them with the following project structure: [PASTE STRUCTURE]. Identify any changes that are misplaced and provide a detailed explanation of where each change should be moved. Additionally, summarize the overall impact of these edits on the project organization and functionality, ensuring that everything adheres to best practices for project layout.

Please provide a detailed list of all files that will be modified for the task of [TASK NAME]. For each file, explain its role within the overall project structure and how the planned changes will enhance or maintain the functionality of the project. Additionally, outline any dependencies or relationships between these files and other components in the project. This will help ensure that all modifications are accurate and consistent with the project's architecture.

Please provide a detailed list of the files that were modified after implementing the fix for the project structure issue. For each file, confirm that the changes align with the overall project structure and explain the reasoning behind each modification. Include specific details about how these changes improve the functionality or organization of the project. Additionally, summarize any potential impacts these edits may have on the project as a whole.

Please execute structure validation tests on my project to verify that all recent changes have been made in the correct files. Provide a detailed report of the test results, highlighting any discrepancies or issues found in the project structure. Additionally, confirm whether the overall structure adheres to the expected standards and outline any areas that may require attention or correction.

Please reproduce the scenario that required changes in my project. Clearly outline the specific modifications that were made and confirm that they have been correctly applied. Provide a detailed comparison of the before and after states, highlighting the differences and improvements resulting from the changes. Include any relevant code snippets or examples to illustrate the modifications effectively.

Please verify the integrity of the dependencies within my project after implementing the recent fix. Analyze the relationships between all files and ensure that each dependency is intact and accurately reflects the overall project structure. Provide a detailed report that includes any discrepancies found, suggestions for resolving issues, and confirmation that all dependencies align with the intended architecture of the project.

Please review the project structure of my current project and identify any additional changes that may have been made. For each change, provide a detailed explanation of how it aligns with the overall project structure and why it does not lead to any further misplacements. Additionally, summarize the key principles of the project structure that were adhered to during these changes, and ensure that the final layout is organized and logical. Format your response in a clear, structured manner that highlights each change and its justification.

Draft a clear and concise rule for the CLAUDE.md file that outlines how to interpret the project structure for future reference. The rule should include specific guidelines on organizing files and directories, naming conventions, and any essential components that must be included in the project structure. Ensure that the language is straightforward and easy to understand, so that all team members can follow it effectively. Format the rule as a bullet-point list for clarity and include examples where necessary.

Create a comprehensive checklist for verifying file roles and dependencies in a project before making any changes. The checklist should include items such as confirming the purpose of each file, identifying dependencies between files, ensuring that all necessary files are included in the project structure, and checking for any outdated or unused files. Format the checklist in a clear, bulleted list and include a brief introduction that explains the importance of this verification process to maintain project integrity and avoid issues during development.

Please add detailed comments above each function in the code that explain its role, purpose, and any constraints or limitations it has. For each function, include a brief description of what the function does, the parameters it takes, and the expected output. Ensure that the comments are clear and concise, making it easy for someone else to understand the code's functionality without needing to read through the entire implementation. Format the comments consistently and provide the exact text for each function's comment.

Create a session opener that emphasizes the importance of reviewing the project structure before making any changes. The opener should include a brief explanation of why understanding the project structure is crucial for maintaining code integrity and preventing errors. Additionally, provide a checklist of key elements to consider during the review, such as file organization, dependencies, and overall architecture. Format the text in a clear and engaging manner, suitable for use at the beginning of a coding session.

Help me establish a clear naming convention for files in my project to clarify their roles and purposes. The convention should include specific rules for different types of files, such as source code, documentation, and configuration files. Please provide examples of naming formats for each type, including any prefixes or suffixes that should be used, and explain the reasoning behind these choices. Additionally, outline how this convention can improve project organization and collaboration among team members.