AI Prompts for Clarifying Project Structure for Claude Code

Please review the following CLAUDE.md file content: [PASTE CONTENT]. Analyze the rules outlined within the document and confirm your understanding of each one. After your review, identify which specific rule applies to the task we were just working on, and provide a brief explanation of how it relates to that task. Additionally, suggest any improvements or adjustments that could enhance compliance with the rules.

Please provide a comprehensive list of all directories in the current project. For each directory, explain its intended purpose and the types of files that should logically reside within it. Additionally, clarify any potential misunderstandings regarding the structure or naming conventions used in these directories. Aim for a detailed analysis that helps in understanding the overall organization of the project.

Please review the last three changes made to the project. For each change, provide a detailed explanation of why that specific location was chosen within the project structure. Additionally, discuss how each change aligns with the overall goals and architecture of the project. Include any potential impacts these changes may have on future development and maintenance. Format your response clearly, with each change numbered and explained in separate sections.

Please analyze the current file layout of my project and provide a detailed overview of its structure. Include information on the purpose of each main directory and file, as well as how they relate to one another. Identify any assumptions you believe may be incorrect or misleading, and suggest potential improvements or clarifications that could enhance the overall organization. Your response should be comprehensive, covering all relevant aspects of the file layout to ensure a clear understanding.

Given the project we are currently working on, please evaluate the task context by explaining the criteria you use to determine which files and directories are relevant to the task. Discuss the factors you consider, such as the project structure, naming conventions, and any specific dependencies that may influence relevance. Additionally, identify any gaps in your understanding of the project structure that could hinder your ability to effectively assess the files and directories. Provide a detailed analysis that can help clarify the task context and improve overall project comprehension.

Please review the following directory structure for my project: [PASTE LAYOUT]. Identify any misunderstandings or misinterpretations you may have regarding this layout. After analyzing the structure, confirm that you have updated your context accordingly and provide a brief summary of the key components and their relationships within the project. Additionally, suggest any improvements or clarifications that could enhance the organization of the directory.

Please revert the incorrect changes that were made in the wrong location and apply them to the correct files according to the following structure: [PASTE STRUCTURE]. Ensure that the changes are accurately reflected in the designated files without introducing any new errors. Provide a summary of the changes made, including the specific files that were affected and the nature of the corrections applied. Additionally, confirm that the project structure remains intact after these adjustments.

Please clarify the roles of the following files in my project: [PASTE LIST]. For each file, provide a brief description of its purpose, how it interacts with other files, and any important dependencies or functions it serves within the overall project structure. Additionally, confirm your understanding of each file's role and suggest any adjustments needed to optimize the project organization.

Please review the contents of the CLAUDE.md file and summarize the key rules that are relevant to the current task. Identify which specific rules apply and explain how they should influence the actions taken moving forward. Additionally, provide examples of how each applicable rule can be implemented in practice to ensure compliance with the guidelines outlined in the document.

Please reassess the task context for the project with a focus on the correct file layout. Describe the specific file structure that should be in place and how it impacts the overall approach to the task. Include details on how the organization of files can affect code readability, maintainability, and collaboration among team members. Additionally, provide recommendations for best practices in structuring the project files to enhance efficiency and clarity.

Please provide a detailed list of the files that were changed after the recent fix. For each file, explain why the change is now in the correct location within the project structure, including any relevant context about the project's organization. Additionally, outline the tests you ran to verify the functionality of these changes, including the expected outcomes and any issues encountered during testing. Ensure that your response is thorough enough for someone unfamiliar with the project to understand the rationale behind the changes and their impact.

Please describe your interpretation of the project structure for [PROJECT NAME]. Include details about the key components and their relationships, as well as how this understanding has evolved since the beginning of the project. Explain specific examples of previous errors that occurred due to misunderstandings of the structure and how your current interpretation helps to prevent these issues moving forward. Aim for a comprehensive overview that highlights the importance of clarity in project organization and its impact on successful outcomes.

Please execute tests to validate that the recent changes to the project align with the correct file structure. Provide a detailed report of the test results, including any discrepancies or errors found during the validation process. If there are no errors, confirm that the file structure is correct and provide a summary of the validation checks performed. Ensure the report is clear and easy to understand, highlighting any areas that may need attention.

Please reproduce the original scenario that caused the issue with the project structure. Describe the specific steps taken to recreate the problem, including any relevant code snippets or configurations. Confirm whether the issue still occurs after implementing the proposed resolution, and provide a detailed comparison of the situation before and after the fix. Include any observations or changes in behavior that demonstrate the resolution's effectiveness.

Please verify compliance with the CLAUDE.md file for my project. Review the actions taken and confirm that all rules outlined in the document are being followed. For each rule, provide evidence of compliance, including specific examples from the project that demonstrate adherence. Additionally, highlight any areas where there may be discrepancies or where further clarification is needed. Format your response in a structured manner, listing each rule, the corresponding evidence, and any recommendations for improvement.

Based on the issues encountered in the previous project, please draft a new rule for CLAUDE.md that addresses these problems and outlines clear guidelines to prevent similar misunderstandings in future sessions. The rule should include specific examples of what went wrong, the rationale behind the new guidelines, and how they will improve project structure and communication. Format the rule in a clear and concise manner, suitable for direct inclusion in the CLAUDE.md document.

Create a comprehensive checklist to follow at the beginning of any session where file modifications are requested. The checklist should include steps such as reviewing the current project structure, confirming the specific files to be modified, and ensuring that backup copies of original files are created. Additionally, include a step for verifying the understanding of the requested changes and a reminder to document any modifications made. Format the checklist in a clear, bullet-point style for easy reference during the session.

Please provide a code comment that should be placed above the function I just fixed. The comment should clearly warn any AI assistant about the specific constraint that must not be violated in this context. Include details about the constraint, its implications, and why it is important to adhere to it. The comment should be concise yet informative, ideally no more than three sentences long, and formatted in a way that is easy to understand for anyone reviewing the code.

Draft a comprehensive project convention document that clearly outlines the correct file structure and usage guidelines for a project. Include sections that detail the purpose of each directory, naming conventions for files, and any specific rules for organizing code, assets, and documentation. Additionally, provide examples of how to structure a typical project, including any best practices that should be followed to ensure consistency and clarity. The final document should be formatted for easy reference and understanding by all team members involved in the project.

Please create a comprehensive guide for understanding the project file layout for a software development project. Include detailed descriptions of key directories such as [DIRECTORY 1], [DIRECTORY 2], and [DIRECTORY 3], explaining their specific purposes and the types of files typically found within each. Additionally, outline best practices for organizing files within these directories to enhance clarity and maintainability. The guide should be structured in a way that allows new team members to quickly grasp the project's organization and should be formatted as a clear, easy-to-follow document.