AI Prompts for Correcting Deprecated Suggestions

Please analyze the following code snippet: [PASTE CODE]. Determine if this approach is deprecated or incompatible with our current framework. If it is not suitable, provide a detailed explanation of the reasons for its incompatibility, including any relevant changes in the framework or best practices that have evolved. Additionally, suggest an alternative approach that aligns with the current standards and explain why it is preferable.

Review the following code snippet: [PASTE CODE]. Analyze it to determine if it is compatible with the framework version [FRAMEWORK VERSION] that we are currently using. Identify any incompatibilities and provide specific details about what aspects of the code do not align with the framework's requirements. Additionally, suggest potential modifications or alternatives to resolve these issues.

Analyze the recent suggestions made in the file: [FILE NAME]. Identify any patterns that are deprecated or considered anti-patterns, and provide a detailed explanation of why each identified pattern is problematic. Include examples of how these patterns can lead to issues in the context of [SPECIFIC CONTEXT OR APPLICATION]. Additionally, suggest alternative approaches or best practices that could be implemented to improve the quality of the suggestions.

Please review the following project-specific rules: [PASTE CONTENT]. Analyze the recent suggestions made for this project and confirm whether they comply with these rules. If there are any violations, highlight them clearly and provide a brief explanation for each. Additionally, suggest potential adjustments or corrections to ensure compliance with the established rules.

Evaluate the current project context and assess the appropriateness of your recent suggestions. For each suggestion, explain why it aligns or does not align with the overall objectives and requirements of the project. Include specific examples from the project to support your evaluation, and suggest alternative recommendations that would be more suitable. Aim for a detailed analysis that covers at least three suggestions and their relevance to the project's goals.

Please review the following deprecated code: [PASTE CODE]. Identify the specific issues that make it outdated and provide an updated version that adheres to current coding standards. Additionally, explain the changes you made and why they are necessary for compliance. Ensure that the new code is well-structured and includes comments for clarity.

Please analyze the following incompatible code: [PASTE CODE]. Identify the specific framework incompatibilities present and suggest detailed modifications to ensure compatibility with our framework version [FRAMEWORK VERSION]. Explain the reasoning behind each suggested change, and provide examples of how the corrected code should look. Additionally, outline any potential impacts these changes may have on the overall functionality of the code.

Please analyze the following code snippet that has been flagged as an anti-pattern: [PASTE CODE]. Identify the specific issues that make it an anti-pattern and suggest a detailed refactor that aligns with best practices. Explain the reasoning behind your suggestions, including how the changes improve the code's readability, maintainability, and performance. Provide the refactored code along with comments to clarify the improvements made.

Please review the following code: [PASTE CODE] and check it against our project-specific rules. Identify any areas where it does not align with these rules and explain the issues found. If corrections are needed, provide a revised version of the code that adheres to the project guidelines. Additionally, summarize the changes made and the reasoning behind them to ensure clarity.

Please review the following code: [PASTE CODE] and adjust it to ensure it aligns with our current project requirements. Consider the specific context of the project, including any recent changes in functionality, user needs, or performance goals. Provide a detailed explanation of the adjustments made and how they improve the code's relevance to the project. Additionally, suggest any best practices that could enhance the overall quality and maintainability of the code.

Please provide the updated code for the following section: [PASTE CODE]. Ensure that it no longer utilizes any deprecated patterns and explain the specific changes made to improve the code. Additionally, highlight any new best practices that have been implemented in this update and how they enhance the overall functionality or performance of the code.

Please run tests on the following corrected code: [PASTE CODE]. Confirm whether it works correctly with our framework and provide a detailed summary of the test results. Include information on any errors encountered, the overall success rate of the tests, and any specific areas of the code that may need further attention or improvement. Format the results in a clear and organized manner, highlighting key findings and recommendations for next steps.

Please analyze the refactored code provided below: [PASTE CODE]. Validate that it no longer contains any anti-patterns and identify the specific improvements made in this version compared to the previous one. Discuss how these changes enhance code readability, maintainability, and performance. Additionally, provide examples of any best practices that are now followed in the new code.

Please review the updated code provided below: [PASTE CODE]. Ensure that it complies with our project-specific rules and guidelines. Highlight any areas where it does not meet compliance and provide suggestions for how to correct these issues. Additionally, summarize the key rules that are being adhered to and any potential risks if compliance is not achieved.

Evaluate the following revised code: [PASTE CODE]. Confirm whether it fits the project context by analyzing its functionality, efficiency, and adherence to project requirements. Discuss how the code aligns with the overall architecture and design principles of the project. Additionally, provide specific examples or evidence that demonstrate its appropriateness for the intended use case, including any potential improvements or considerations for future development.

Please draft a new rule for our .cursorrules file that will prevent deprecated pattern suggestions based on the recent issue we encountered. The rule should clearly define the deprecated patterns to be avoided and include specific conditions under which these patterns should not be suggested. Additionally, provide a brief explanation of the rationale behind this rule and how it will improve our suggestion system. Format the rule text in a way that is ready to be implemented directly into the file.

Please insert a code comment above the following section: [PASTE CODE]. The comment should warn against patterns that may be incompatible with the framework being used. Ensure the comment is clear and concise, highlighting potential issues and suggesting best practices to avoid these pitfalls. The comment should be formatted correctly for the programming language in use and should be informative enough for other developers to understand the risks involved.

Create a comprehensive checklist to help identify and avoid common anti-patterns in project sessions. The checklist should include at least ten specific anti-patterns, along with a brief description of each one and examples of situations where they might occur. Additionally, provide actionable tips for how to avoid each anti-pattern and improve overall session effectiveness. Format the checklist in a clear, easy-to-read layout, suitable for quick reference during meetings or planning sessions.

Draft a comprehensive guide on ensuring that suggestions are contextually relevant to a project. The guide should include key principles for evaluating the appropriateness of suggestions, examples of contextual relevance in different scenarios, and tips for aligning suggestions with project goals and audience needs. Aim for a length of 500 words, structured with clear headings and bullet points for easy readability. Include a section on common pitfalls to avoid when assessing contextual relevance.

Create a reminder message that prompts users to check for rule compliance at the beginning of each session. The reminder should clearly outline the importance of adhering to established rules and guidelines, and encourage users to take a moment to review them. Include specific examples of rules that should be checked, and suggest a brief checklist format for easy reference. The message should be concise yet informative, ideally no more than 100 words, and should emphasize the benefits of compliance for a successful session.