AI Prompts for Correcting TypeScript Violations in Autocomplete

Please analyze the following TypeScript code for incorrect autocomplete suggestions: [PASTE CODE]. Identify all types or interfaces that are being violated and provide a detailed explanation for each violation. Include information on how these violations affect the functionality of the code and suggest possible corrections or improvements to resolve the issues. Format your response in a clear, structured manner with bullet points for each identified issue.

Analyze the following autocomplete suggestions: [PASTE SUGGESTIONS]. Evaluate whether each suggestion aligns with the defined TypeScript types and interfaces. Provide a detailed report that includes any discrepancies found, suggestions for corrections, and an explanation of how the suggestions could be improved to better fit the expected types. Additionally, summarize the overall quality of the autocomplete suggestions based on their adherence to the defined types.

Please review the following TypeScript type definitions: [PASTE DEFINITIONS]. Analyze the autocomplete suggestions generated and confirm whether they adhere to the specified type definitions. Provide feedback on any discrepancies you find, including specific examples of suggestions that do not align with the definitions. Additionally, suggest improvements or corrections to ensure that the autocomplete suggestions accurately reflect the intended type definitions.

Please analyze the edits made in Cascade mode to the following files: [LIST FILES]. Focus on identifying any TypeScript type violations that may have been introduced as a result of these changes. For each violation, provide a brief description of the issue, the specific line number where it occurs, and suggest possible solutions or corrections. Additionally, summarize the overall impact of these violations on the functionality and type safety of the codebase.

Please examine the contents of my CLAUDE.md file, which I will provide: [PASTE CONTENT]. Analyze the rules defined within the file to determine if the TypeScript types are being ignored in the autocomplete suggestions. Specifically, identify any discrepancies or issues related to the handling of TypeScript types and suggest possible improvements or corrections to ensure that the autocomplete functionality adheres to the specified rules. Provide a detailed report of your findings, including examples if applicable.

Please review the current autocomplete logic and identify any violations related to the specified TypeScript types: [LIST TYPES]. Once you have identified the issues, provide a detailed explanation of each violation and suggest specific adjustments to the autocomplete logic that will ensure compliance with these types. Additionally, outline the potential impact of these changes on the overall functionality and performance of the autocomplete feature.

Please review the autocomplete suggestions in the project and ensure they conform to the TypeScript interfaces defined. Identify any discrepancies between the suggestions and the interfaces, and provide a detailed list of necessary changes to enforce type safety. Include specific examples of suggestions that do not meet the interface requirements and explain how they can be corrected. Additionally, suggest any improvements to the interface definitions that could enhance type safety in future autocomplete suggestions.

Please provide a detailed adjustment of the Cascade mode settings to ensure it does not make edits that violate TypeScript types. Outline the specific settings that need to be modified, including any parameters or values that should be changed. Additionally, explain the rationale behind each adjustment and how it will enhance type safety in the code. Format the response as a clear list of updated settings with explanations for each change.

Revise the CLAUDE.md file to include a detailed section on stricter rules for TypeScript type adherence in autocomplete suggestions. Ensure that the new rules clearly outline the specific type-checking requirements that must be met for suggestions to be included. Include examples of valid and invalid type usages, as well as explanations of how these stricter rules will improve the accuracy and relevance of autocomplete suggestions. Format the updated rules in a clear, structured manner with headings and bullet points for easy reference.

Please review the following code snippets that contain type violations: [PASTE SNIPPETS]. For each snippet, identify the specific type violations and provide corrected versions that adhere to TypeScript types. Additionally, explain the changes made and why they resolve the violations. Format your response to include the original snippet, the corrected version, and a brief explanation for each correction.

Please perform a TypeScript type check on the following files: [LIST FILES]. Ensure that there are no type violations present in any of the files. If any violations are found, provide a detailed report outlining the specific issues, including the file names, line numbers, and descriptions of the violations. Additionally, suggest possible solutions or corrections for each violation identified.

Please review the updated autocomplete suggestions for the following code: [PASTE CODE]. Analyze whether the suggestions properly adhere to TypeScript types and provide detailed feedback on any discrepancies or areas for improvement. Specifically, check for type correctness, completeness of suggestions, and any potential issues that could arise from the current implementation. Summarize your findings in a structured format, highlighting both strengths and weaknesses in the suggestions.

Please verify the edits made in Cascade mode for the following files: [LIST FILES]. Check each file for any TypeScript type violations and provide a summary of your findings. Include details on any violations found, the specific lines where they occur, and suggestions for resolving these issues. Additionally, confirm that all intended changes were successfully applied without introducing new errors.

Please verify whether the updated rules outlined in CLAUDE.md are being applied correctly in the autocomplete suggestions. Analyze the suggestions generated and confirm if they align with the specified rules. If there are discrepancies, provide a detailed report on which rules are not being followed and suggest potential adjustments to ensure compliance. Include examples of both correct and incorrect suggestions to illustrate your findings.

Please run the full test suite on the project and verify the integrity of the code. Ensure that there are no TypeScript type violations present. After running the tests, provide a detailed report of the results, including any errors or warnings encountered, and summarize the overall status of the code integrity. If any issues are found, please categorize them by severity and suggest potential fixes.

Draft a new rule for CLAUDE.md that enforces TypeScript type adherence in autocomplete features. The rule should clearly outline the requirements for type definitions, including any specific types that must be enforced and examples of correct and incorrect usage. Additionally, explain the rationale behind the rule and how it addresses recent issues encountered. Format the rule in a clear and concise manner, ensuring it is easy to understand and implement.

Please generate a comment to be inserted in the codebase that reminds developers to verify TypeScript types in autocomplete suggestions. The comment should be clear and concise, emphasizing the importance of type checking to avoid potential errors. Aim for a length of 1-2 sentences, and ensure it encourages best practices in maintaining type safety. Format the comment in a way that is easily understandable and can be quickly referenced by developers.

Create a comprehensive checklist for starting a windsurfing session that ensures all necessary preparations are made. Include items such as checking equipment condition, verifying safety gear, confirming weather conditions, and ensuring all TypeScript types are respected in the coding environment. The checklist should be structured in a clear format, with each item being actionable and specific, allowing for easy reference before heading out on the water. Aim for at least 10 detailed items that cover all essential aspects of preparation.

Define a comprehensive naming convention for TypeScript types that aims to prevent autocomplete violations. Include specific guidelines on how to name types based on their purpose, such as using prefixes or suffixes to indicate their usage, and suggest patterns for naming interfaces, enums, and type aliases. Additionally, provide examples of good and bad naming practices, and explain how this convention can enhance code readability and maintainability within a project. Format your response in a structured manner with clear headings for each section.

Design a project guard that automatically rejects code submissions that violate TypeScript types. Explain the underlying mechanism of how this guard detects type violations during the code review process. Include detailed setup instructions, covering any necessary configurations in the project files, integration steps with the existing development workflow, and examples of common type violations that the guard should catch. Additionally, outline best practices for maintaining the guard and ensuring it remains effective as the codebase evolves.