AI Prompts for Ensuring Code Style Compliance

Here is my ESLint configuration file: [PASTE CONTENT]. Please analyze the configuration and identify which specific rules are being ignored in my code. For each ignored rule, provide a brief explanation of why it may not be followed, including potential reasons related to project settings, coding standards, or any conflicts with other rules. Additionally, suggest any adjustments I can make to ensure compliance with these rules moving forward.

Please review the following Prettier configuration file: [PASTE CONTENT]. Analyze the formatting rules specified in this configuration and confirm whether they are being applied correctly. If any rules are not being followed, provide a detailed list of the missing formatting rules along with explanations of how they differ from the expected standards. Additionally, suggest any changes needed to ensure compliance with the Prettier guidelines.

Please analyze the following style guide for my project: [PASTE CONTENT]. Identify any style conventions that have not been adhered to in the recent code changes. Provide a detailed report outlining each convention that is not being followed, including specific examples from the code changes. Additionally, suggest how these conventions can be properly implemented in future code updates to ensure consistency with the style guide.

Please review the following .cursorrules file content: [PASTE CONTENT]. Confirm your understanding of these rules and identify any specific rules that are not being applied correctly. Additionally, provide suggestions on how to ensure compliance with the rules and enhance the overall effectiveness of the file. Include any relevant best practices or adjustments that could improve the implementation of these rules.

Please review the recent code changes made in the project. Identify and highlight specific areas where the code style deviates from the established project conventions. For each identified issue, provide a brief explanation of the convention that was not followed and suggest a correction. Additionally, summarize the overall impact of these style inconsistencies on code readability and maintainability.

Identify the following ESLint violations in my code: [LIST VIOLATIONS]. For each violation, provide a detailed explanation of the issue and then correct it according to the rules specified in my ESLint configuration. Ensure that the corrected code adheres to best practices and is properly formatted. Present the corrections in a clear format, showing both the original and the corrected code for easy comparison.

Reformat the following code to comply with the Prettier configuration provided. Ensure that all aspects of the code, including indentation, line breaks, and spacing, are adjusted according to Prettier's standards. After making the changes, provide a clear summary of what modifications were made and highlight any specific areas where the formatting was significantly altered. The original code is as follows: [INSERT CODE HERE].

Please review the code provided and adjust it to adhere to the project's style guide. Ensure that all formatting, naming conventions, and structure align with the specified guidelines. After making the necessary adjustments, provide a detailed list of the changes made, explaining how each change contributes to compliance with the style guide. Include examples where relevant to illustrate the modifications.

Please review the .cursorrules file and identify the following rules that have been missed: [LIST RULES]. Explain the significance of each rule and how they should be applied to the current codebase. Provide specific examples of how to implement these rules effectively, and suggest any necessary changes to ensure compliance with the updated guidelines. Additionally, summarize the potential impact on the code quality and maintainability after applying these rules.

Please review the following specific code style issues: [LIST ISSUES]. For each issue, provide a detailed correction and explain the reasoning behind the changes you made. Include any relevant coding standards or best practices that apply to each correction. Format your response as a list, clearly indicating the original issue, the corrected code, and the explanation for the fix.

Please run ESLint on the updated code provided and display the output results. Ensure that you confirm there are no remaining violations in the code. Additionally, provide a summary of any issues that were found and how they were resolved, if applicable. Format the output in a clear and structured manner, highlighting any areas that required attention.

Please validate the formatting of the following code snippet: [INSERT CODE HERE]. Run Prettier to check for any formatting issues and provide a detailed report of any discrepancies found. Include specific line numbers where issues exist, a description of the formatting problems, and suggestions for how to resolve each issue. Ensure that the final output adheres to standard formatting guidelines and is easy to read.

Please review the provided code and evaluate its adherence to the specified style guide. Identify any areas where conventions are not being followed and provide detailed feedback on what needs to be corrected. Additionally, summarize the overall compliance of the code with the style guide, highlighting any significant issues or areas of improvement. Format your response in a clear and structured manner, including specific examples from the code where applicable.

Please verify the application of the rules specified in the .cursorrules file to the provided code. List each rule and indicate whether it has been successfully applied or not. If any rules are not applied, provide a brief explanation of why they were not met and suggest potential solutions for compliance. Format the output in a clear table with columns for the rule name, compliance status, and notes.

Please recreate the scenario that initially caused the style issues in the code. Provide a detailed description of the original situation, including any relevant code snippets or configurations that were in place. After reproducing the scenario, confirm whether the problem still exists, and present a clear comparison of the before and after states, highlighting any changes made to resolve the issue. Ensure that the explanation is thorough enough for someone unfamiliar with the original problem to understand the context and the solution.

Please draft a new rule for CLAUDE.md aimed at preventing style violations that have been identified in recent issues. The rule should clearly outline the specific style guidelines that need to be adhered to, including examples of common violations and the correct formatting or practices to follow. Ensure that the rule is concise yet comprehensive, providing enough detail for users to understand and apply it effectively. Format the rule in a way that can be directly added to the CLAUDE.md document.

Create a comprehensive style checklist to ensure adherence to project style conventions at the beginning of each session. The checklist should include items such as verifying code formatting, checking naming conventions for variables and functions, ensuring proper documentation practices are followed, and confirming that all code adheres to the project's architectural guidelines. Format the checklist in bullet points for easy readability and include at least ten specific items that cover various aspects of coding style and best practices.

Please generate a comment that can be inserted above functions to warn AI assistants about specific style constraints. The comment should clearly outline the style guidelines that need to be followed, including any particular formatting rules or conventions that are important for this code. Ensure the comment is concise yet informative, and provide an example of how it should be formatted in the code. The comment should be suitable for use in a programming environment and help maintain code quality.

Please suggest detailed updates to the .cursorrules file that will enhance style compliance for our coding standards. Include specific rules or guidelines that should be added or modified, and explain the rationale behind each change. Additionally, provide examples of how these changes will improve code readability and maintainability. Format your response as a structured list of changes, including any relevant code snippets where applicable.

Create a session opener that emphasizes the importance of checking style compliance before implementing any changes. The opener should include a brief reminder of the key style guidelines to follow and the potential consequences of not adhering to them. Additionally, suggest a few questions to consider when reviewing the style compliance, such as 'Does this change align with our established coding standards?' and 'Have I consulted the style guide for this project?' Format the opener as a concise paragraph that can be easily referenced at the beginning of each session.