AI Prompts for Preventing Unnecessary Dependencies

Please provide a comprehensive list of all the packages added during the last development session. For each package, include a brief explanation of its purpose and how it contributes to the requested feature. Additionally, assess whether the inclusion of each package was essential for the feature's functionality or if it could be considered unnecessary. Format your response in a table with columns for the package name, purpose, necessity, and any potential alternatives that could have been used.

Generate a detailed dependency tree for the current project. Identify and highlight any packages that appear to be unrelated to the recent feature request. Provide a brief explanation for each unrelated package, including why it may not be necessary and any potential impact on the project if it were removed. Format the output in a clear and organized manner, making it easy to understand the relationships between the dependencies and the feature request.

Please review the installation logs from the last session and provide a detailed analysis. Identify any packages that were installed without a direct request from the developer, and explain why these packages may have been added. Additionally, categorize these packages based on their purpose and potential impact on the project. Summarize your findings in a clear report format, highlighting any recommendations for managing unnecessary dependencies in the future.

Given the feature request [DESCRIBE FEATURE], please provide a detailed list of the essential packages and dependencies required to implement this feature. After compiling the list, compare it to the current dependencies in the project and identify any discrepancies or additional packages that may be necessary. Additionally, explain the purpose of each essential package and how it contributes to the functionality of the feature. Format the response in a clear, organized manner, highlighting any critical dependencies that are missing.

Please examine the contents of my .cursorrules file, which I will provide below: [PASTE CONTENT]. Analyze the recent package installations and confirm whether they comply with the specified rules in the file. If there are any discrepancies or issues, please provide detailed feedback on what does not comply and suggest possible solutions or adjustments to ensure compliance. Additionally, summarize the overall compliance status in a clear and concise manner.

Please analyze the current project dependencies and identify any packages that have been added but are not necessary for the current feature. Provide a detailed list of these unnecessary packages, explaining why each one is not required. Once identified, outline the steps needed to safely remove these packages from the project, and confirm that their removal will not affect the functionality of the existing features. Finally, summarize the changes made and any potential impacts on the project.

Please review the current package.json file and identify all the dependencies listed. Determine which packages are essential for the current project requirements and which can be removed. Provide a revised version of the package.json that includes only the necessary packages, ensuring that the project will function correctly without any unnecessary dependencies. Include comments explaining why each package was retained or removed for clarity.

Please review the current dependency list for the project and identify any changes that do not align with the feature request: [DESCRIBE FEATURE]. Once identified, revert those changes to restore the dependency list to its previous state. Provide a summary of the changes that were reverted and explain how each one was misaligned with the feature request. Ensure that the final dependency list is clean and only includes necessary dependencies for the feature.

Please validate the current dependencies in my project to ensure they adhere to the .cursorrules file. Identify any dependencies that do not comply and provide a detailed report on the specific issues found. For each non-compliant dependency, suggest the necessary adjustments or changes needed to achieve compliance. Additionally, outline the potential impact of these changes on the overall project functionality and performance.

Please analyze the list of packages currently included in the project and provide a detailed justification for the necessity of each one. For every package, explain how it aligns with the current project requirements, including its specific role and contribution to the overall functionality. Additionally, identify any potential alternatives that could fulfill the same purpose, and discuss the implications of removing any packages that may not be essential. Format your response in a structured manner, with each package clearly labeled and its justification outlined in a few sentences.

Please provide a comprehensive list of all current dependencies used in the project. For each dependency, explain its purpose and confirm whether it is essential for the project's functionality. If any dependencies are deemed unnecessary, suggest alternatives or indicate if they can be removed without affecting the project. Format the response in a clear table with columns for the dependency name, purpose, necessity status, and any recommendations for removal or alternatives.

Please execute all relevant tests for the project to verify that it runs correctly with the updated dependency list. Provide a detailed report of the test results, including any errors or failures encountered, along with suggestions for resolving any issues. Additionally, summarize the overall status of the project after the tests are completed, indicating whether it is functioning as expected or if further action is needed.

Provide a detailed comparison of the dependency list for the project before and after the recent changes. Include all package names, versions, and any relevant notes on why specific packages were deemed unnecessary and removed. Additionally, confirm that the updated list reflects only the essential packages needed for the project to function optimally. Present this information in a clear format, highlighting the differences and ensuring that the rationale for each change is well explained.

Please recreate the scenario that led to unnecessary dependencies being added in the project. Describe the specific steps taken that resulted in these dependencies, including any relevant configurations or code snippets. After reproducing the scenario, confirm whether the issue still occurs and provide a detailed explanation of the outcome. If the issue has been resolved, outline the changes made to prevent it from happening again.

Please verify the current project setup against the .cursorrules file to ensure full compliance. Identify and list any discrepancies you find, including specific areas where the project does not meet the rules outlined in the file. For each discrepancy, provide a brief explanation of the issue and suggest potential solutions or adjustments needed to achieve compliance. Format your findings in a clear, organized manner, highlighting the most critical issues first.

Please create a detailed checklist to follow before adding any new dependencies to a project. The checklist should include specific steps to verify the necessity of each dependency, such as assessing its impact on performance, security, and maintainability. Additionally, include guidelines for ensuring compliance with established rules and standards relevant to the project. Format the checklist in a clear, actionable manner, with each step numbered and explained, so it can be easily followed by developers.

Please draft a new rule for the .cursorrules file that aims to prevent unnecessary dependencies from being added in future sessions. The rule should clearly define what constitutes an unnecessary dependency, provide examples of common scenarios where these may occur, and outline the steps that should be taken to avoid them. Additionally, include recommendations for best practices that developers should follow to ensure that only essential dependencies are included in their projects. Format the rule in a clear and concise manner, suitable for inclusion in a technical documentation.

Please insert a comment in the package.json file that warns against adding unnecessary dependencies. The comment should read: 'Warning: Avoid adding unnecessary dependencies to keep the project lightweight and maintainable. Review all dependencies carefully before including them.' Ensure that the comment is placed in a clear and visible section of the file, ideally near the top, so that it is easily noticed by anyone working on the project.

Create a session opener checklist that outlines the steps to verify the necessity of dependencies before starting any feature implementation. Include specific criteria to evaluate each dependency, such as its impact on performance, compatibility with existing systems, and potential risks associated with its inclusion. The checklist should also prompt for a review of alternative solutions or libraries that could achieve the same functionality without adding unnecessary complexity. Format the checklist in a clear and concise manner, with bullet points for easy reference during the session.

Please create a detailed project convention document that outlines the criteria for adding new dependencies to a project. Include sections that cover the rationale for adding dependencies, the evaluation process for assessing their necessity, guidelines for version control, and any potential impacts on project performance and security. Additionally, provide examples of acceptable and unacceptable dependencies, and suggest a format for documenting each new dependency added to the project. Ensure the document is clear, structured, and suitable for inclusion in project documentation.