AI Prompts for Enforcing Consistent Naming Conventions

Analyze the current file and identify all the different naming conventions utilized throughout the code. Specifically, list any instances of camelCase, snake_case, and PascalCase, providing clear examples for each type found. Additionally, include a brief explanation of the context in which each naming convention is used, and suggest any improvements for consistency across the file. Format your response in a structured list for clarity.

Scan the provided code file for any variables or functions that do not adhere to the established naming conventions of the project. Please create a detailed report that includes a list of the identified violations, specifying the exact names of the variables or functions, and describe how they deviate from the naming conventions. Additionally, provide suggestions for how each violation can be corrected to align with the project's standards. Format the report in a clear and organized manner for easy reference.

Please analyze the following .cursorrules file content: [PASTE CONTENT]. Identify the naming conventions specified within this file and evaluate whether they are being consistently followed throughout the project. Provide a summary of any discrepancies you find, including specific examples of where the conventions are not adhered to, and suggest improvements to ensure consistency in naming conventions moving forward.

Analyze the current file for naming convention issues and provide a detailed summary. Identify and categorize the types of violations, such as inconsistent casing, unclear naming, or non-standard abbreviations. For each type, include the total number of violations found and any specific examples that illustrate these issues. Additionally, suggest best practices for improving naming conventions to enhance code readability and maintainability.

Analyze the open files in the project and identify any naming conventions that do not align with the established project standards. Provide a detailed report that includes specific examples of inconsistent naming patterns, the files where these inconsistencies occur, and suggestions for how to correct them. Additionally, summarize the potential impact of these deviations on code readability and maintainability. Format the findings in a clear and organized manner, making it easy to understand the necessary changes.

Please convert all variable and function names in the provided code file to camelCase format according to the project's naming conventions. Ensure that all instances of names are updated consistently throughout the file. Additionally, provide a summary of the changes made, including the original names and their corresponding camelCase versions. Format the output as a list for clarity, and include any relevant notes about potential conflicts or considerations during the conversion process.

Please convert all identifiers in the codebase to snake_case format according to the project's naming conventions. Ensure that variable names, function names, and any other relevant identifiers are consistently updated. Provide a summary of the changes made, including any potential issues encountered during the conversion process. Additionally, include examples of before and after for clarity.

Please review the code in this file and identify any class names that do not adhere to the PascalCase naming convention as outlined in the project guidelines. For each class name that is inconsistent, provide the corrected version in PascalCase format. Additionally, include a brief explanation of why adhering to this naming convention is important for code readability and maintainability.

Please review the current file and standardize all naming conventions to align with the specified format outlined in the project’s .cursorrules file. Ensure that all variable names, function names, and class names are consistent and follow the defined rules. Provide a summary of the changes made, highlighting any names that were modified and the reasoning behind the adjustments. Additionally, include examples of both the original and standardized names for clarity.

Identify and correct all naming convention violations in the open files to ensure they align with the project's established standards. Please provide a detailed report of the changes made, including the original names and the corrected names for each violation. Additionally, summarize the overall impact of these corrections on the codebase's readability and maintainability. Ensure that the final naming conventions are consistent throughout the project.

Please review the current file and confirm that all naming conventions adhere to the project standards. Specifically, identify any inconsistencies in variable names, function names, and class names. Provide a summary of any discrepancies found, including examples of the inconsistent names and suggestions for how to correct them. Additionally, outline the specific naming conventions that should be followed according to the project guidelines.

Please validate that all files in the project adhere to the specified naming conventions. Provide a detailed report that includes any files that do not comply, along with the reasons for non-compliance. Additionally, suggest possible corrections for each file that is not following the conventions. Ensure the report is structured clearly, highlighting the compliant and non-compliant files separately, and include a summary of the overall compliance status of the project.

Generate a comprehensive report on the current state of naming conventions used throughout the project files. Include an analysis of the consistency and clarity of names for variables, functions, classes, and files. Highlight any discrepancies or areas where naming conventions do not align with best practices, and provide recommendations for standardizing naming conventions moving forward. Format the report with sections for each type of naming element, and include examples of both good and poor naming practices.

Please scan the project for any remaining naming convention issues. Identify and list each issue you find, providing a brief description of the inconsistency and the specific location in the code where it occurs. Additionally, suggest appropriate naming conventions that should be applied to resolve these issues. Format the output as a structured report with clear headings for each identified issue.

Please verify that the rules specified in the [RULES FILE NAME] are being correctly applied to all currently open files. List any files where the rules are not being applied as expected, and provide details on which specific rules are failing. Additionally, include any recommendations for correcting the inconsistencies found in the application of these rules. Format your response as a report that highlights the discrepancies and suggests actionable steps to resolve them.

Please create a new naming rule for the .cursorrules file to enforce consistent naming conventions based on the resolved issues. The rule should specify the format for naming variables, functions, and classes, including any required prefixes or suffixes. Additionally, outline any exceptions to the rule and provide examples of both compliant and non-compliant names. Ensure that the final rule is clear and concise, suitable for inclusion in the project documentation.

Please add a comment at the top of the code file that clearly explains the naming conventions to be followed throughout the codebase. Include specific examples of how variables, functions, and classes should be named, ensuring that the guidelines are easy to understand and apply. The comment should be structured in a way that highlights the key rules and provides context for why these conventions are important for maintaining consistency. Aim for a length of at least 100 words to ensure thoroughness.

Please create a comprehensive checklist for developers to follow at the beginning of each coding session to ensure consistent naming conventions. The checklist should include specific guidelines on variable naming, function naming, class naming, and file naming. Additionally, include examples of good and bad naming practices, as well as tips for maintaining clarity and readability in code. Format the checklist in a clear, bullet-point style that is easy to follow, and ensure it covers common pitfalls to avoid.

Draft a comprehensive naming convention document for the project. Include specific rules for variable names, function names, and class names, ensuring clarity on the format, casing (e.g., camelCase, snake_case), and any prefixes or suffixes that should be used. Additionally, provide examples for each type of name to illustrate the conventions in practice. Aim for a structured format that can serve as a reference for all team members to maintain consistency throughout the codebase.

Create a project guard that automatically verifies naming convention compliance for all code before it is committed. The guard should check for specific naming standards such as camelCase for variables, PascalCase for classes, and snake_case for functions. Additionally, provide a detailed report of any violations found, including the file names and line numbers where the issues occur. Ensure that the guard is easy to integrate into existing workflows and can be configured to allow exceptions for specific cases if necessary.