AI Prompts for Ensuring Code Style Compliance

Read the following CLAUDE.md file: [PASTE CONTENT]. Summarize each rule outlined in the document to demonstrate your understanding. Then, analyze the last task and identify which specific rule should have been applied, providing a brief explanation of why that rule is relevant to the task. Format your response clearly, listing the rules and your analysis in separate sections.

Analyze the following code snippet for ESLint compliance: [PASTE CODE]. Identify any ESLint rules that should have been applied but were ignored in this code. Provide a detailed list of these rules, including a brief explanation of each rule and its significance for maintaining code quality. Additionally, suggest specific corrections or improvements that could be made to adhere to these rules, and format your response in a clear and organized manner.

Review the following Prettier configuration settings from my .prettierrc file: [PASTE CONTENT]. Analyze how these settings affect the generated code and identify any discrepancies or areas where the code does not conform to the specified formatting rules. Summarize your findings with specific examples of inconsistencies and provide recommendations for adjustments to ensure compliance with the configuration.

Examine the following code: [PASTE CODE]. Identify any style convention mismatches according to the project's coding guidelines. Provide a detailed analysis that includes specific examples of the mismatches, explain why each deviation is a problem, and suggest how to correct each issue. Finally, summarize the overall impact of these mismatches on code readability and maintainability, highlighting any potential risks they pose to future development.

Evaluate the impact of changes made to the following files in Cascade mode: [LIST FILES]. Analyze each file for any alterations that may have violated established style rules. Provide a detailed report that includes specific examples of the violations found, recommendations for corrections, and an overall assessment of how these changes affect the codebase's adherence to style guidelines. Ensure the findings are formatted in a clear and organized manner, highlighting key issues and suggested improvements for better compliance with the style guidelines.

Re-evaluate the following code while enforcing the specified ESLint rules: [LIST_RULES]. Identify any violations present in the code and provide a detailed report outlining the issues found. For each violation, include the original code snippet, describe the identified issue, and suggest specific corrections and improvements to ensure compliance with the ESLint rules. Format your output as a clear list for easy reference.

Reformat the following code according to the Prettier configuration provided: [PASTE CONFIG]. Identify and correct all formatting issues, including indentation, line breaks, and spacing. Ensure the output is clean, consistent, and adheres strictly to the specified configuration. Provide the reformatted code as a complete block, clearly indicating any changes made.

Review the following code for style convention errors: [PASTE CODE]. Adjust it to align with the project's style conventions as outlined in these guidelines: [PASTE GUIDELINES]. Ensure that all discrepancies are addressed, and provide a summary of the changes made, highlighting any significant adjustments that improve adherence to the style conventions.

Review the following files for any style violations that may have been introduced by Cascade mode: [LIST_FILES]. Identify specific issues related to code formatting, naming conventions, and best practices. Provide a detailed report of the corrections needed, including examples of the violations and the recommended fixes. Ensure that your final output adheres to the established coding standards for the project and includes actionable steps for each identified issue.

Review the provided custom rules file: [PASTE CONTENT] and ensure that the code adheres to all specified conventions. Identify any areas where the code does not comply with these rules, suggest specific changes to correct them, and provide a detailed explanation for each suggested change. Include the rationale behind the custom rules and explain how the proposed modifications will enhance code quality and maintainability.

Perform an ESLint check on the codebase. Provide a detailed summary of any remaining issues, including the types of issues found, their specific locations in the code, and suggestions for resolving each one. If the codebase is compliant, confirm this with a brief statement. Additionally, outline best practices that could enhance overall code quality in the future.

Validate the following code for compliance with Prettier formatting standards: [CODE SNIPPET]. Check all sections for adherence to style guidelines, including indentation, spacing, and line length. Summarize any formatting issues identified and provide specific suggestions for corrections. If the code is correctly formatted, confirm that it meets all Prettier requirements.

Review the provided code and cross-check it against the project's style guidelines. Identify specific areas where the code does not conform to the specified conventions, and provide detailed feedback on each discrepancy. Additionally, summarize the overall adherence to the style guidelines and suggest improvements that could enhance code quality. Ensure your response is formatted clearly and structured, highlighting the specific sections of the code that require attention.

Conduct an audit of the changes made in Cascade mode to ensure compliance with established style rules. Review all relevant files and identify any discrepancies, specifying which files do not meet the standards. Provide a summary of these discrepancies along with suggestions for corrections. Additionally, outline the key style rules that should be followed for future changes to maintain consistency across the project.

Validate the application of custom rules in the provided code: [CODE SNIPPET]. Review the code against the conventions outlined in the custom rules file: [CUSTOM RULES FILE]. Identify any discrepancies or areas where the conventions are not being followed, and provide a detailed report that includes specific examples of violations, suggestions for corrections, and an overall assessment of compliance with the custom rules. Format the report in a clear and organized manner, highlighting key findings and recommendations.

Create a new rule for a CLAUDE.md file that enforces style compliance based on recent issues encountered in the project. Specify the style guidelines that need to be followed, including relevant examples of correct and incorrect usage. Provide the exact text to be added to the CLAUDE.md file, ensuring it is formatted for easy integration. Additionally, explain the rationale behind the rule and how it addresses the identified issues to prevent recurrence.

Draft a comprehensive set of ESLint rules for future code in the [PROJECT NAME]. The rules should address code style, best practices, and potential errors. Include specific configuration details such as rule names, severity levels (error or warning), and any additional options or settings. For each rule, provide a clear rationale explaining its importance for maintaining code quality. Format the output as a JSON configuration file suitable for implementation.

Create a Prettier configuration template that ensures consistent code formatting across a project. Include key settings such as PRINT WIDTH, TAB WIDTH, USE OF SEMICOLONS, SINGLE VS. DOUBLE QUOTES, TRAILING COMMAS, and any other relevant options. Format the output as a JSON object and provide brief explanations for each setting to clarify their purpose and impact on code style.

Create a code comment template that outlines the key style conventions for a project. Include sections for NAMING CONVENTIONS, CODE FORMATTING RULES, and BEST PRACTICES for writing clear and maintainable code. Structure the template with headings for each section and provide examples where applicable. This comment should be placed at the top of each code file to remind developers of the style guide and promote consistency throughout the codebase.

Create a comprehensive session-opener checklist for coding sessions to ensure style compliance. Include specific items such as verifying code formatting standards, confirming adherence to naming conventions, ensuring documentation standards are met, and checking for code readability and consistency across the project. Format the checklist clearly, with each item listed as a separate point for easy reference during the session.