AI Prompts for Restricting Unnecessary File Edits

Please review the following CLAUDE.md rules: [PASTE CONTENT]. Analyze each rule carefully and confirm your understanding of them. After your review, identify which specific rule was applicable to the last task and explain how it should have been implemented. Additionally, provide suggestions on how to better adhere to these rules in future tasks.

Please review the last task description provided: [PASTE TASK]. Identify the specific files and functions that were intended to be edited according to the description. Then, explain any deviations from the original plan, detailing the reasons for these changes and how they impact the overall project. Provide a summary of the implications of these deviations on the project's timeline and deliverables.

Analyze the impact of a fixed context window on task management and scope tracking in a project. Discuss how this limitation may have led to missing critical information or changes that were not initially outlined. Provide specific examples of what details or aspects of the task were overlooked due to this constraint. Additionally, suggest strategies to mitigate these limitations in future projects to ensure all relevant information is captured and considered.

Please analyze the recent changes made during the last task. Provide a comprehensive list of all files and functions that were edited, and clearly indicate which of these were not included in the original task description. Additionally, for each unasked change, explain the potential impact it may have on the overall project and whether it aligns with the project's goals. Format your response in a structured manner, separating the original task components from the additional changes for clarity.

Please evaluate the following task description: [PASTE TASK]. Summarize your understanding of the scope of this task, detailing the key objectives and deliverables. Additionally, identify and explain any discrepancies between your understanding of the task and your recent actions or decisions related to it. Provide insights on how these discrepancies could impact the overall project and suggest any adjustments that may be necessary to align with the original task scope.

Please reinforce the task scope by ensuring that all actions are restricted to the following files and functions: [LIST FILES/FUNCTIONS]. Clearly confirm your understanding of this scope and outline any potential implications of adhering strictly to these boundaries. Additionally, provide suggestions on how to effectively manage any unasked changes or scope creep that may arise during the project. Your response should be detailed and include strategies for maintaining focus on the defined scope.

Please clarify the intent of the task by summarizing the specific areas that need modification, which are: [LIST AREAS]. Explain your understanding of each area and outline the plan for implementing these changes. Include any potential challenges you foresee and how you intend to address them. Your response should be detailed and structured to ensure clarity in the task execution.

Please ensure that you only access or modify the following files: [LIST FILES]. Confirm that you understand this restriction and will proceed without accessing any files outside of this list. Additionally, provide a brief explanation of how you will maintain this limitation during the task at hand.

Please review the following functions: [LIST FUNCTIONS]. I need you to isolate these functions and make necessary edits while ensuring that no other functions in the codebase are altered. Provide a brief summary of the changes made to each function and confirm that all other functions remain untouched. Additionally, explain how the changes improve the overall functionality or performance of the specified functions.

Please provide a detailed summary of the rules outlined in CLAUDE.md, ensuring that each rule is clearly articulated. After summarizing, explain how you will apply these rules to the current task at hand. Include specific examples of how adherence to these rules will influence the outcomes of the project, and outline any potential challenges you foresee in compliance. Aim for a comprehensive response that covers all relevant aspects of the guidelines.

Please provide a comprehensive list of all files that have been modified during this task. Ensure that the list includes only those files that align with the intended modifications specified in the following list: [LIST FILES]. Additionally, for each file, include a brief description of the changes made and confirm whether these changes meet the project requirements and objectives. Format the response clearly, with each file and its corresponding changes listed separately.

Please provide a comprehensive list of all functions that have been edited in the project. For each function, include details such as the original purpose, the specific changes made, and how these changes align with the specified functions: [LIST FUNCTIONS]. Additionally, highlight any potential impacts these edits may have on the overall functionality and performance of the project. Format your response in a clear and organized manner, using bullet points for each function.

Please confirm that no extra files or functions have been altered in the project. Review the changes made and provide a detailed summary of your verification process, including any specific files checked and the outcomes of your review. If any alterations are found, list them clearly along with their potential impact on the project. Ensure that your summary is concise yet comprehensive, covering all necessary aspects of the verification.

Please review the task completion based on the following task description: [PASTE TASK]. Confirm that all specified changes have been implemented accurately and that no additional changes were made beyond what was requested. Provide a detailed summary of the changes that were completed, highlighting any discrepancies or areas where the task did not meet the original specifications. If possible, include suggestions for improvement or clarification on any ambiguous aspects of the task.

Please re-evaluate the actions taken in the project against the guidelines outlined in the CLAUDE.md document. Confirm whether all actions are in compliance with these rules and identify any deviations or areas where the actions may not align with the specified guidelines. Provide a detailed analysis of each action, including specific references to the relevant sections of CLAUDE.md, and suggest corrective measures for any identified discrepancies. Format your response as a structured report with sections for compliance confirmation, deviations, and recommendations.

Draft a new rule for CLAUDE.md that addresses the importance of adhering to task scope and preventing scope creep. The rule should clearly define what constitutes the task scope, outline the process for requesting any changes, and specify the consequences for not following the established scope. Ensure the language is formal and precise, and provide the exact text that can be directly added to CLAUDE.md. The rule should be concise yet comprehensive enough to prevent ambiguity in future tasks.

Please create a comprehensive checklist that I can use to review before starting any task. The checklist should include specific steps to verify the task scope, ensuring all requirements are clearly defined and agreed upon. Additionally, include guidelines for checking file or function restrictions that may impact the task. Organize the checklist into sections for easy reference, and aim for at least 10 detailed items that cover all critical aspects to prevent scope creep and unasked changes.

Please propose a set of comprehensive naming conventions for task descriptions that will help clearly define project scope and prevent misunderstandings. Include guidelines on how to structure task names, what key elements should be included, and examples of effective naming practices. Additionally, explain how these conventions can enhance communication among team members and improve project management efficiency. Aim for a detailed document that can be easily referenced by the team.

Please suggest a detailed protocol for reviewing task scope before execution to prevent scope creep and unasked changes. Include specific steps that should be taken during the review process, such as identifying key stakeholders, defining the scope clearly, and establishing criteria for approval. Additionally, provide a template that outlines the necessary components of the review, including sections for task description, objectives, potential risks, and a checklist for stakeholder sign-off. Ensure the protocol is structured in a way that can be easily followed by team members.

Design a comprehensive set of guardrails for a project management system that automatically flags actions that fall outside the defined task scope. These guardrails should include specific criteria for identifying scope creep, such as changes in project requirements, additional tasks not originally agreed upon, and requests for features that were not part of the initial project plan. Provide detailed text for each guardrail, including examples of actions that would trigger a flag, the process for reviewing flagged actions, and recommendations for addressing scope changes. Ensure the guardrails are clear, actionable, and easy to implement within the project management framework.