20 of the best prompts for ensuring config file compliance, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
20 of the best prompts for ensuring config file compliance, step by step across 4 stages. Works with ChatGPT, Claude, and Gemini.
Getting Ensuring Config File Compliance right takes more than a single prompt. This 4-stage guide covers Diagnose the Wall, Isolate and Fix, Verify the Resolution, and more, breaking the whole process into focused steps where each prompt builds on the last. Windsurf is not reading or applying the project rules from the config file, causing unexpected behavior and errors. This leads to misaligned code edits and potential project disruption. These prompts help developers ensure Windsurf adheres to project-specific rules, restoring expected functionality. Every prompt is optimized and runs in ChatGPT, Claude, and Gemini.
Identify if Windsurf is recognizing and attempting to apply the config file rules.
Check Config File Recognition
Please check if the CLAUDE.md file is present in my project directory. Confirm its existence and identify any potential issues that may prevent it from being read correctly. Additionally, provide details on the file's expected format and any specific configurations that might affect its recognition. If there are errors, suggest possible solutions to resolve them.
Identify Ignored Rules
Please analyze the content of my CLAUDE.md file, which is as follows: [PASTE CONTENT]. Identify and list the specific rules mentioned in the file that are being ignored or cannot be applied. For each rule, provide a brief explanation of why it is being ignored or what the limitations are in applying it. Additionally, suggest any potential adjustments or considerations that could help in addressing these ignored rules.
Review File Path
Please review the file path and naming convention of my CLAUDE.md file to identify any potential issues that may prevent access. Provide a detailed analysis of the correct structure for file paths, including common pitfalls and best practices for naming conventions. If there are specific examples of errors or improvements I should consider, please include those as well. Additionally, suggest any troubleshooting steps I can take to resolve access issues related to file paths.
Analyze File Syntax
Please analyze the syntax of the content in my CLAUDE.md file: [PASTE CONTENT]. Identify any syntax errors or issues that could prevent proper reading or interpretation of the file. Provide a detailed report of the errors found, including the specific lines where they occur and suggestions for correcting them. Additionally, explain how these errors might affect the overall functionality or readability of the document.
Confirm Rule Application Attempt
Please confirm whether you have attempted to apply any rules from the CLAUDE.md file during the last task. If you have, provide a detailed list of the specific rules you applied, including their names and a brief description of how each rule was implemented in the task. Additionally, explain any challenges you faced while applying these rules and how they impacted the overall outcome of the task.
Focus on correcting any identified issues with the config file or its recognition.
Correct File Path Issues
Please help me troubleshoot file path issues related to CLAUDE.md. I need you to analyze the common reasons for path errors and suggest the correct path or naming conventions that would ensure the file is accessible. Additionally, provide examples of both correct and incorrect file paths, and explain how to structure paths in a way that avoids these issues in the future. Make sure to cover any specific considerations for different operating systems if applicable.
Resolve Syntax Errors
Please review the following content for my CLAUDE.md file: [PASTE CONTENT]. Identify any remaining syntax errors and provide a detailed explanation of what the issues are, along with suggestions for correcting them. Additionally, confirm whether the provided content resolves all syntax issues and ensure that it adheres to standard markdown formatting. If there are any improvements or best practices I should follow, please include those as well.
Force Rule Re-evaluation
Please re-evaluate the rules outlined in the CLAUDE.md file and provide a detailed confirmation of how they are currently being applied. Include a summary of each rule, any discrepancies you find in their application, and suggestions for adjustments if necessary. Additionally, explain the implications of these rules on the overall process and how they can be improved for better compliance. Format your response in a clear, structured manner with bullet points for easy readability.
Update Rule Parsing Logic
Please analyze the current rule parsing logic and identify potential issues that may arise with specific rules. Suggest detailed modifications to the rule structure that would enhance compliance and improve overall parsing accuracy. Include examples of the original rule format and the proposed changes, explaining how these modifications would resolve the parsing issues. Additionally, outline any potential impacts these changes may have on existing functionality.
Reconfirm File Access
Please confirm whether you have access to the CLAUDE.md file and can apply its rules effectively. If there are any issues with accessing the file, provide details on what the problems are and suggest potential solutions to resolve them. Additionally, outline any steps that can be taken to ensure smooth application of the rules specified in the file.
Ensure that Windsurf is now correctly applying the config file rules.
Validate Rule Application
Please validate the application of all rules outlined in the [FILE NAME] document within the current project. Provide a detailed report that includes: a summary of each rule, whether it is being applied correctly, any discrepancies found, and suggestions for resolving any issues. Additionally, include the potential impact of each rule on the project if not applied correctly. Format the report as a structured document with headings for each rule and a conclusion summarizing the overall compliance status.
Check for Errors
Please perform a diagnostic check to identify any errors related to the CLAUDE.md file in the current project setup. Include a detailed report of any issues found, specifying the nature of each error and potential solutions or recommendations for resolution. Additionally, provide a summary of the overall health of the project setup, highlighting any other areas that may require attention or improvement. Format the findings in a clear and organized manner for easy reference.
Confirm Config Compliance
Please verify that the current project setup adheres to all the compliance rules outlined in the CLAUDE.md file. Provide a detailed report highlighting any areas of non-compliance, including specific sections of the CLAUDE.md file that were violated. Additionally, suggest corrective actions that can be taken to ensure full compliance moving forward. Format the report in a clear and structured manner, with headings for each section of compliance reviewed.
Generate Compliance Report
Generate a compliance report that outlines the rules specified in the CLAUDE.md file. Include a section that details which rules are currently being applied and another section that highlights any rules that are still being ignored. For each rule, provide a brief explanation of its purpose and the implications of compliance or non-compliance. Format the report with clear headings for each section and ensure it is comprehensive enough to serve as a reference for compliance verification.
Run Project Test
Please run a comprehensive test on the project to verify that the application of CLAUDE.md rules does not introduce any new errors. Include a detailed report of the test results, highlighting any issues found, along with their severity and potential impact on the application. Additionally, provide recommendations for resolving any identified errors and ensure that the application maintains its intended functionality. The report should be structured clearly, with sections for findings, recommendations, and a summary of the overall test results.
Create safeguards to ensure future compliance with the config file.
Draft New Rule for CLAUDE.md
Please draft a new rule for the CLAUDE.md document that addresses recent issues encountered. The rule should clearly outline the specific problems that have arisen and provide actionable steps to prevent their recurrence. Include examples of situations where this rule would apply, and suggest any necessary changes to existing processes or guidelines. Ensure the language is clear and concise, and format the rule in a way that is easy to understand and implement.
Create File Access Checklist
Please create a detailed checklist to ensure that the CLAUDE.md file is always accessible and correctly named in future projects. The checklist should include steps such as verifying the file's location in the project directory, confirming the correct naming conventions are followed, and ensuring that proper permissions are set for file access. Additionally, include reminders for regular audits of the file's accessibility and a process for updating the file if changes are made. Format the checklist in a clear, organized manner for easy reference.
Add Syntax Validation Rule
Please create a new rule for the CLAUDE.md documentation that mandates syntax validation must be completed prior to the application of any project rules. This rule should outline the specific syntax standards that need to be met, the process for validating syntax, and the consequences of failing to adhere to this requirement. Additionally, include examples of valid and invalid syntax to provide clarity. Format the rule in a clear, structured manner suitable for inclusion in the documentation.
Implement Rule Parsing Guide
Create a comprehensive guide on how rules should be structured for optimal parsing and application. Include sections on the key components of a rule, best practices for naming conventions, and examples of well-structured rules. Additionally, outline common pitfalls to avoid and provide tips on how to ensure rules are easily maintainable and scalable. Format the guide in a clear, organized manner with headings and bullet points for easy reference.
Establish Compliance Verification
Please help me create a detailed compliance verification step to include in the CLAUDE.md document. This step should outline the specific rules that need to be checked for compliance before project execution, including any relevant standards or regulations. Additionally, provide a checklist format that can be easily followed, ensuring that each rule is clearly defined and includes criteria for successful compliance. The final output should be structured in a way that allows team members to easily understand and implement the verification process.
Windsurf might not recognize the CLAUDE.md file due to incorrect file paths, naming conventions, or syntax errors. Ensuring the file is correctly placed and formatted is crucial for rule application.
Verify that the CLAUDE.md file is in the correct directory and free of syntax errors. Use Windsurf's diagnostic tools to check file recognition.
Check for syntax errors or parsing issues in the CLAUDE.md file. Adjust rule structure if necessary and confirm with Windsurf that the rules are now being applied.
Yes, by adding verification steps in CLAUDE.md, you can automate compliance checks to ensure rules are applied correctly before project execution.
Use Windsurf's diagnostic prompts to identify issues with file recognition, syntax, or rule application, and apply the suggested fixes to resolve them.
AI Prompts for Ensuring Config File Compliance
Bolt is not reading or applying the project rules, config file, or instructions file, causing unexpected behavior and potential project failures.
See promptsAI Prompts for Ensuring Config File Compliance
Cursor is not reading or applying the project rules from the config file, causing unexpected behavior.
See promptsAI Prompts for Ensuring Config File Compliance
Lovable is not applying the project rules, config file, or instructions file, causing unexpected behavior in the app.
See prompts