AI Prompts for Silent Build Failure Diagnosis

Please quote the exact output from the last build attempt, focusing on the specific component or function that caused the failure. Then, compare this output with the expected output based on your original instructions. Highlight any discrepancies and provide insights into why the failure may have occurred.

Please analyze the following build log from the deployment tab: [BUILD LOG]. Identify any warnings or errors that may not have been displayed in the interface. Provide a summary of your findings, highlighting the most critical issues and suggesting potential solutions for each.

Please interpret the original instruction given for the UI component related to the use-case 'v0-build-fails-silently.' Provide a detailed explanation of your understanding, highlighting any areas where miscommunication may have occurred. Include specific examples from the instruction that could lead to different interpretations and suggest how these could be clarified to avoid future issues.

Compare the expected behavior of the component with the actual behavior observed. Clearly outline the expected output format and functionality, detailing each aspect where the actual behavior deviates from expectations. Present this comparison in a structured format, including sections for the expected output, actual output, and a brief analysis of the discrepancies.

Please analyze the last output and identify any violated design constraints or rules. Quote the specific constraint that was not adhered to, and provide a brief explanation of how this violation impacts the overall output. Format your response with the quoted constraint clearly highlighted, followed by your analysis.

Please revert the signature of the component located at src/components/MyComponent.jsx:15. The original signature is 'function MyComponent(props)', and it was changed to 'function MyComponent()'. Provide the diff of the changes made to the signature before applying the revert. Ensure that the output clearly highlights the differences between the two signatures.

Rewrite the function in [FILE PATH] to ensure it adheres to the specified constraints. The original function is: 'function helper() { ... }'. Include parameters for all required inputs, and ensure that the function handles errors gracefully while providing meaningful feedback. Additionally, document the purpose of each parameter and the expected output format.

Please update the Tailwind CSS configuration by changing the class 'bg-red-500' to 'bg-red-600' in the file located at [FILE PATH]. Explain why this change is necessary to meet the design specifications and outline any potential impacts this modification may have on the overall styling of the application. Additionally, provide a brief summary of how this change aligns with the project's design goals.

Please review the component located in src/components/MyComponent.jsx and ensure it adheres to the specified format. Specifically, it should include prop types and default props. After making the necessary updates, provide the revised code for the component along with a brief explanation of the changes made.

Please review the import statements in the file located at [FILE PATH]. Specifically, verify that the statement 'import MyComponent from \"../components/MyComponent\";' correctly points to the intended file. If there are any discrepancies, provide the correct file path and explain why the original path was incorrect.

Please run a test build for the project [PROJECT NAME]. Confirm that the output matches the expected behavior by checking for any errors or warnings in the console. Provide a summary of the results, including any discrepancies found and suggestions for resolving them.

Please provide the diff of changes made in the file src/components/MyComponent.jsx. Highlight the specific modifications and explain how they align with the expected component structure. Additionally, include any relevant context or implications of these changes for the overall functionality of the component.

Replay the original scenario that caused the build to fail in the context of [APPLICATION NAME]. Confirm that the component now functions correctly without errors by providing a detailed report on the outcome, including any error messages encountered previously, the current status of the component, and any changes made to resolve the issue. Additionally, outline the steps taken during the replay to ensure thorough verification.

Identify and analyze potential edge cases in the file src/utils/helpers.js. List all possible inputs that could lead to issues and describe how each one is currently handled. Provide recommendations for improving input handling to ensure robustness and prevent silent failures. Format your response as a detailed report with sections for each edge case identified, including examples and suggested code modifications.

Please verify the state of the file src/styles/global.css. Ensure that it has been updated according to the latest design specifications and that there are no errors present. Provide a summary of any discrepancies found, along with suggestions for corrections if necessary.

Before any build step, verify that all components adhere to the specified design constraints. If any component fails to meet the criteria, stop the build and report the issue in a clear format that includes the component name, the specific constraint it failed, and suggestions for resolution. Ensure that this validation process is reusable across different projects by outlining any necessary configuration settings or parameters that need to be adjusted for each build.

Create a detailed component specification snippet for [COMPONENT NAME]. Use the following format: 'Component: [COMPONENT NAME], Props: { [PROP1]: [TYPE1], [PROP2]: [TYPE2] }, Constraints: Must follow design guidelines.' Ensure that the snippet is complete and accurately represents the component's properties and constraints. Provide the exact snippet in a code block format.

Please create a style constraint note for Tailwind CSS that adheres to the following guidelines. The note should clearly state that all components must utilize Tailwind classes that align with the established design system. Additionally, include a warning that any deviation from these classes will lead to a build failure. Format the output as a single, concise statement that can be easily referenced by developers.

Generate a configuration note for shadcn/ui that emphasizes the importance of registering all components in the shadcn/ui configuration file. The note should clearly state: 'Ensure all components are registered in the shadcn/ui configuration file. Missing components will cause silent build failures.' Format the output as a concise bullet point for easy reference.

Create a context reload prompt for new sessions that ensures compliance with the latest design specifications. The prompt should state: 'At the start of each session, verify the last successful build output and ensure all components are compliant with the latest design specifications.' Please provide the exact wording for this prompt.