AI Prompts for Clarifying Project Structure for Changes

Please provide a list of all the files that have been modified recently in the project. For each file, explain its intended role and functionality within the overall project structure. Additionally, identify any discrepancies or misunderstandings you have regarding how these files fit into the project, and suggest how they should be organized or clarified to align with the actual project structure.

Please analyze the most recent changes made to the project. Provide a detailed list of the changes, including the specific files or directories that were modified. For each change, explain whether it was applied to the correct location and, if not, clarify the reasoning behind the choice of location. Additionally, assess the potential impact of these changes on the overall project structure and functionality.

Please review the following project structure: [PASTE STRUCTURE]. Analyze it in detail and identify any potential mismatches or inconsistencies that could lead to errors in the project. Provide a summary of your findings, including specific areas that may need adjustment or clarification, and suggest improvements to ensure the structure aligns with best practices. Additionally, outline any potential risks associated with the current structure and how they might impact the project's success.

Please provide a comprehensive list of all components that have been created or modified in the project. For each component, include its intended location and the actual file path where it is currently located. Additionally, highlight any discrepancies between the intended and actual locations, and suggest steps to resolve any mismatches. This information will help ensure that the project structure is organized and that all components are correctly placed.

Please review the configuration files for my project and explain how they contribute to your understanding of the overall project layout. Identify any potential misinterpretations or inconsistencies within these files that could lead to confusion about the project's structure. Additionally, provide suggestions on how to clarify or improve these configuration files to better reflect the intended project organization. Format your response in a structured manner, highlighting key areas of concern and recommendations for each file.

Identify the misplaced changes in my project files. Provide a detailed list of the changes, specifying their current locations and the correct files or directories where they should be moved. For each change, explain why the new location is appropriate based on the project's structure and organization principles. Include any relevant best practices for file management in this context.

Please review the project structure and identify any components that are mislocated. For each mislocated component, update the paths to reflect their correct locations within the project. After making the updates, provide a summary of the changes made, including the original and new paths for each component, and confirm that the project structure is now accurate and organized.

Please help me align the configuration settings for my project to accurately reflect its structure. I need a detailed explanation of the specific changes that should be made, including what each setting controls and how it relates to the overall project organization. Additionally, outline how these adjustments will help prevent future misplacements and improve the project's efficiency. Provide examples of common misconfigurations and how the new settings will address these issues.

Identify any sections of code that may have been developed due to a misunderstanding of the project structure in [PROJECT NAME]. Analyze the codebase to pinpoint specific areas where the structure is not being followed correctly. Refactor these sections to ensure they align with the intended project architecture, maintaining functionality while improving clarity and organization. Provide a summary of the changes made, explaining how each adjustment enhances the overall structure and adheres to best practices.

Please clarify the role of each directory within the project structure. For each directory, provide a brief description of its purpose, the types of files it should contain, and any specific guidelines that should be followed when making changes to it. Additionally, summarize how these roles contribute to the overall organization and functionality of the project. This information will help ensure that all future modifications align with the intended structure and purpose of each directory.

Please provide a detailed list of all changes made to correct the project structure for [PROJECT NAME]. For each change, explain what the original issue was and how the change addresses it. Additionally, verify each change against the intended project structure and confirm whether it aligns correctly. Include any relevant notes on potential impacts or further adjustments needed, and format this as a structured report with headings for each change.

Please execute the full suite of tests for the project to verify that it functions correctly with the updated structure. Provide a detailed report of the test results, including any errors or failures encountered during the testing process. Additionally, summarize the overall success rate of the tests and highlight any areas that may require further attention or debugging. Format the results in a clear and organized manner, making it easy to identify which tests passed and which did not.

Please recreate the original scenario that caused the issue with the project structure. Detail the steps taken to reproduce the problem, including any specific inputs or configurations used. After reproducing the scenario, verify whether the problem still occurs and provide a summary of the results, including any error messages or unexpected behavior observed. Format your findings in a clear report that outlines the steps, results, and any recommendations for further action.

Please validate the locations of all components within the project structure. List each component along with its expected location and current location, noting any discrepancies. For any components that are incorrectly placed, provide a brief explanation of the issue and suggest the correct location. Additionally, confirm whether each component is functional and highlight any that are not, along with potential reasons for their malfunction.

Please analyze the updated configuration of the project and evaluate its impact on the overall structure. Confirm whether it aligns with the intended project framework and resolves any previous issues that were identified. Provide a detailed report that includes specific examples of changes made, how these changes affect project functionality, and any potential risks or benefits associated with the new configuration. Additionally, suggest any further adjustments that may be necessary to optimize the project structure.

Draft a comprehensive set of guidelines for understanding the project structure that can be included in the CLAUDE.md file. The guidelines should cover key components such as the overall architecture, folder organization, naming conventions, and the purpose of each major directory and file. Additionally, provide examples to illustrate how the structure supports project goals and workflows. Ensure the document is clear and accessible for both new and existing team members, and aim for a length of at least 500 words to cover all necessary details.

Please add comments at the top of each directory file in my project. Each comment should clearly explain the purpose and role of that directory within the overall project structure. Make sure the comments are concise yet informative, providing enough context for someone unfamiliar with the project to understand the significance of each directory. Format the comments in a consistent style and ensure they are easily readable. Include examples of what types of files or resources might be found in each directory.

Create a detailed session checklist to ensure a thorough understanding of the project structure before making any changes. The checklist should include steps such as reviewing the current project documentation, confirming the roles and responsibilities of team members, assessing the existing project architecture, and identifying any dependencies or potential impacts of changes. Additionally, include a section for noting any questions or clarifications needed from team members. Format the checklist in a clear, organized manner with bullet points for easy reference during each session.

Help me establish clear naming conventions for files and directories in my project. The conventions should indicate the roles of each file and directory, making it easy for team members to understand their purpose at a glance. Please provide examples of naming formats for different types of files, such as scripts, documentation, and assets, and explain how these conventions can enhance project organization and collaboration. Additionally, create a section for the project guidelines that outlines these conventions in a structured manner, ensuring consistency throughout the project.

Please create a high-level overview of the project structure for [PROJECT NAME]. This overview should include a breakdown of the main components, their purposes, and how they interact with each other. Additionally, outline any key conventions or best practices that should be followed during development. Format this overview as a clear and concise document that can be easily referenced by future developers, ensuring it is comprehensive enough to guide them through the project effectively.