AI Prompts for Identifying Runtime Errors in UI Components

Please provide the exact error message you received when attempting to render the component named [COMPONENT NAME]. Include details about the error type that was thrown, and format your response to clearly separate the component name, the error message, and the error type for better clarity.

Please analyze the following build error encountered during the last deployment attempt: [BUILD ERROR]. Identify the potential causes of this error, suggest possible solutions, and outline steps to resolve the issue effectively. Provide your analysis in a structured format, including a summary of the error, the likely reasons, and recommended actions to fix it.

Please provide your interpretation of the original instruction regarding the generation of a new component. Include details on what you understood the requirements to be, any specific features or functionalities you envisioned, and any constraints or considerations that should be taken into account. This will help ensure that we are aligned before proceeding with the component generation.

Identify the expected behavior of the [COMPONENT NAME] when it renders correctly, and contrast it with the actual behavior you are currently experiencing. Provide detailed descriptions of the specific functionalities that are failing, including any error messages or unexpected outcomes. Format your response in two sections: one for expected behavior and one for actual behavior, ensuring clarity in your explanations.

Please analyze the last output and identify any violated design constraints or rules. Quote the specific constraint that was not adhered to, and explain how it relates to the expected functionality of the component. Provide a summary of the implications of this violation on the overall design.

Please fix the import statement for the component located at [FILE] on line [LINE]. The original import statement is: [PASTE]. The incorrect version you currently have is: [PASTE]. Revert the import statement back to the original version only, ensuring that no other changes are made to the code.

Please rewrite the function signature in the code located at [FILE]:[LINE]. The original signature is [PASTE], and the modified signature is [PASTE]. Ensure that only the signature is reverted back to the original format while keeping the rest of the function intact.

Identify the incorrect props being passed to the component located at [FILE]:[LINE]. The expected props are as follows: [PASTE]. Please provide a corrected version of the props while ensuring that the component body remains unchanged. Format your response to clearly show the adjustments made to the props.

Please review the component located at [FILE] on line [LINE] and verify that it follows the expected structure. If it does not, identify the discrepancies and provide a corrected version that adheres to the specified format: [PASTE]. Additionally, explain why the changes are necessary to ensure compliance with the structure.

Please analyze the dependencies listed in the package.json file and identify any version conflicts. Specifically, check the version of [SPECIFIC DEPENDENCY] and compare it to the required versions for compatibility. Provide a detailed report on any discrepancies found, including suggested version updates and potential impacts on the project.

Please run a test on the component located at [FILE]:[LINE]. Confirm that it renders correctly without throwing any errors. After the test is complete, provide a detailed report of the results, including any issues encountered and suggestions for improvement if applicable.

Please provide a detailed diff of changes made to the component located at [FILE] on line [LINE]. Highlight all modifications that were implemented to resolve the runtime error, and include explanations for each change made. Format the output to clearly distinguish between the original and modified code sections for easy comparison.

Replay the original scenario that caused the runtime error in the system. Please provide a detailed account of the steps taken during the replay, including any error messages or unexpected behavior observed. Confirm whether the issue persists or if it has been resolved, and include any relevant logs or screenshots to support your findings.

Please test the component with a variety of edge case inputs, including [EDGE CASE INPUTS]. Document the results of each test, noting any unexpected behaviors or failures. Additionally, provide suggestions for how the component can be improved to handle these edge cases more effectively. Format your findings in a structured report with sections for each input tested, the observed behavior, and recommendations.

Please confirm the output state of the component after applying the fixes. Specifically, check that the output matches the expected format and functionality as defined in the specifications. Provide a detailed comparison of the actual output versus the expected output, highlighting any discrepancies and suggesting further adjustments if necessary.

Please verify that all imports in the component file are correct and exist in the file tree before generating the component. If any import is missing, provide an alert message indicating which imports are not found and stop the generation process. Ensure that the output includes a list of missing imports and a clear instruction on how to resolve the issue.

Please generate a function signature that adheres to the following format: 'FUNCTION_NAME(PARAM1: TYPE1, PARAM2: TYPE2): RETURN_TYPE'. If the generated signature deviates from this expected format, provide an alert indicating the specific deviation and suggest a correction to align with the required structure.

Please create a detailed guideline for enforcing component structure in code. Specify that the structure must follow the format: 'export default function COMPONENT_NAME() { return <JSX>; }'. Include examples of correct and incorrect implementations, and explain the consequences of violating this structure. Additionally, provide suggestions on how to effectively communicate this requirement to the development team to prevent recurrence of violations.

Please create a detailed checklist for verifying dependency compatibility in the package.json file before deployment. Include steps to identify any conflicts, methods for resolving these conflicts, and best practices to ensure all dependencies are compatible with the project. Format the output as a numbered list for easy reference.

Reset the context for this session by ensuring that all previous states are cleared. Begin a fresh generation process for creating non-functional components. Provide a brief overview of the key parameters and guidelines for the new context to ensure clarity and focus in the component generation.