AI Prompts for Ensuring TypeScript Compliance in Autocomplete

Given the following TypeScript interface or type definition: [PASTE TYPE], analyze the suggested completions that do not conform to these definitions. Identify specific violations in the suggestions and provide a detailed explanation for each one, including how they deviate from the expected structure, types, or constraints outlined in the interface. Additionally, suggest corrections or alternatives that would align with the defined types, ensuring clarity and adherence to TypeScript standards.

Please review the last few autocomplete suggestions made in the codebase. Identify and highlight any suggestions that do not comply with the existing TypeScript types. For each non-compliant suggestion, provide a brief explanation of the issue and suggest a possible correction or alternative that aligns with the TypeScript types. Format your response in a clear list, including the suggestion, the type it should comply with, and the proposed correction.

Please evaluate your awareness of the TypeScript types defined in this project. If you are not aware of these types, provide a detailed explanation of how you assess type compliance in your suggestions. Include specific methods or strategies you use to ensure that your recommendations align with the defined types. Additionally, discuss any potential challenges you face when working with type compliance in this context.

Please analyze the issue of context loss during long sessions and its effects on adhering to TypeScript types. Specifically, confirm whether this context loss impacts the accuracy and relevance of your suggestions. Provide a detailed explanation of how this phenomenon occurs, any patterns observed, and potential solutions or improvements that could mitigate these issues. Additionally, include examples to illustrate how context loss manifests in your responses.

Evaluate the project tree structure for TypeScript compliance. Analyze the current project tree and confirm whether it effectively supports TypeScript features and best practices. Provide a detailed assessment of any areas where the project tree may lack clarity or organization, and suggest improvements to enhance TypeScript compliance. Include specific examples of how the project tree can be optimized for better type safety and maintainability.

Please review the following code snippet: [PASTE CODE]. It currently violates the TypeScript type: [PASTE TYPE]. I need you to correct this code so that it complies with the specified type. Provide the corrected code along with a brief explanation of the changes made to ensure compliance.

Please review the recent suggestions made in the context of TypeScript types. Identify any instances where the suggestions do not comply with the defined types and provide corrections for each non-compliant suggestion. For each correction, explain why the original suggestion was non-compliant and how the new suggestion aligns with the defined types. Additionally, summarize the importance of type compliance in maintaining code quality and preventing runtime errors.

Revise the autocomplete logic to prioritize TypeScript type compliance in the suggestions provided. Detail the specific changes made to the logic, including how the prioritization of type compliance improves the overall functionality and user experience. Include examples of how the new logic handles different types and any potential edge cases that were addressed. Additionally, provide a summary of the expected outcomes from these adjustments and how they enhance the accuracy of the autocomplete feature.

Identify and highlight lines in the current file that do not comply with TypeScript types. For each non-compliant line, provide a corrected version along with an explanation of why the original line was non-compliant. Include details on the specific TypeScript rules that were violated and suggest best practices for ensuring compliance in the future. Format the output clearly, separating each non-compliant line and its correction for easy reference.

Please re-scan the project for TypeScript type definitions. Ensure that all suggestions align with these definitions and provide a detailed list of any adjustments made during this process. Include specific examples of how the suggestions were modified to fit the type definitions, and explain the reasoning behind each adjustment. Additionally, summarize any potential impacts these changes may have on the overall project functionality.

Review the current codebase for compliance with TypeScript types. Provide a detailed report that includes any discrepancies or issues found during the type checks, along with the specific lines of code where these issues occur. Additionally, summarize the overall compliance status of the codebase, highlighting any areas that require attention or further modification to ensure full type compliance. Format the output clearly, with sections for compliant and non-compliant code, and include recommendations for resolving any issues identified.

Please run the TypeScript compiler on the current codebase to check for any type errors. Provide a detailed report of the results, including the number of errors found, their locations in the code, and any relevant messages that explain the issues. Additionally, summarize any warnings that may not be errors but could affect the code quality. Format the output in a clear and organized manner for easy review.

Reproduce the scenario that led to the original TypeScript violation. Provide a detailed explanation of the issue, including the specific code that caused the violation. Then, show the corrected code that resolves the issue, highlighting the changes made. Finally, confirm that the violation no longer occurs by demonstrating the successful compilation or execution of the corrected code.

Please provide a detailed list of all suggestions that have been corrected for TypeScript compliance in the project. For each suggestion, include the original suggestion, the corrected version, and a brief explanation of why the correction was necessary. Additionally, confirm whether these corrections are consistently applied throughout the entire project, and highlight any areas where further adjustments may be needed. Format the response in a clear and organized manner for easy reference.

Please run the relevant test cases to validate that the TypeScript compliance issues have been resolved. Provide a detailed report of the test results, including which test cases passed and which failed, along with any error messages or issues encountered during the testing process. Additionally, summarize any changes made to the code that may have affected the test outcomes. Format the results in a clear table, highlighting the key findings and recommendations for further action if necessary.

Please write a new rule for the .cursorrules file that enforces TypeScript compliance for future sessions. The rule should include specific conditions that must be met for code to be considered compliant, such as type annotations, interface usage, and any other relevant TypeScript features. Additionally, provide a brief explanation of how this rule will help prevent similar issues from occurring in the future. Format the rule text clearly and ensure it is ready to be implemented directly into the file.

Create a comprehensive compliance checklist to ensure TypeScript adherence in coding sessions. The checklist should include key checks such as verifying type definitions, ensuring proper use of interfaces and types, confirming that all variables are correctly typed, and checking for any unused variables or imports. Additionally, include steps for validating that functions have appropriate return types and that any external libraries are correctly typed. Format the checklist in a clear, bullet-point style for easy reference at the beginning of each session.

Please generate a code comment that should be placed above the affected function in TypeScript. The comment should warn AI assistants about the specific TypeScript constraint that applies to this function. Include details about the constraint, why it is important, and any potential issues that may arise if it is not adhered to. Format the comment in a way that is clear and informative for future developers who may work with this code.

Create a detailed protocol for reviewing TypeScript types at the beginning of each development session. Outline the specific steps that should be taken to ensure compliance with best practices. Include guidelines for identifying and addressing any inconsistencies or errors in the types, methods for documenting changes, and a checklist to verify that all types have been reviewed. Additionally, suggest a process for providing feedback to team members on their type definitions and how to incorporate this review into the overall development workflow.

Create a session opener that emphasizes the importance of TypeScript compliance requirements. The opener should remind users to adhere to best practices in TypeScript, including type safety, proper interfaces, and avoiding any implicit 'any' types. Ensure the text is clear and concise, ideally no longer than three sentences, and can be used as a reminder before making any suggestions. Format the opener in a way that is engaging and encourages users to think critically about their TypeScript code.