AI Prompts for Identify Tailwind Style Conflicts

Please provide the exact styles generated for the Button component in your project. Compare these styles with the expected styles defined in your Tailwind configuration. Highlight any discrepancies you find, and explain how these differences could affect the component's appearance and functionality.

Please analyze the following build error message related to a styling conflict: [ERROR MESSAGE]. Identify the specific components or styles that are causing the conflict and provide recommendations on how to resolve the issue. Format your response with a summary of the conflict, potential causes, and suggested solutions.

Before generating a new component, please explain your understanding of the original instruction regarding Tailwind styles. Include any specific aspects of the styles that may lead to conflicts or misinterpretations. Additionally, provide examples of how these styles might be applied correctly to avoid issues in the new component.

Compare the expected styles for the Card component with the actual styles that were generated. Please provide a detailed list that includes the specific expected styles, such as colors, fonts, and spacing, alongside the actual styles produced by the system. Highlight any discrepancies and explain how they differ from your expectations, including potential reasons for the conflicts. Format your response in a clear table for easy comparison.

Identify the specific Tailwind rule or utility class that was violated in the last output. Provide the exact clause from your Tailwind configuration that was not adhered to, and explain why this violation occurred. Additionally, suggest a potential solution to resolve this conflict and ensure compliance with the Tailwind styling guidelines.

Identify the conflicting inline styles in the Button component located at [FILE PATH]. Revert the background color to match the Tailwind configuration of 'bg-blue-500' and ensure that no other styles are overriding this setting. Provide a summary of the changes made and any additional recommendations for avoiding similar conflicts in the future.

Rewrite the Card component to strictly adhere to Tailwind's spacing rules. Ensure that the padding is set to 'p-4' and the margin is set to 'm-2'. Please provide the updated code snippet, and confirm that no custom spacing utilities have been added.

Please modify the Navbar component by changing the font size to 'text-lg' while ensuring that all other styles remain unchanged. This will help to isolate the styling conflict related to Tailwind. After making the change, provide a brief explanation of how this adjustment affects the overall styling and any potential conflicts that may arise from it.

Please review the class names used in the Modal component and ensure they adhere to Tailwind's formatting conventions. Identify any custom utility classes that may conflict with Tailwind's classes and provide a list of these classes. Additionally, suggest specific changes to replace or remove these conflicting classes to ensure full compliance with Tailwind's standards.

Please review the import statements in the file located at [FILE PATH]. Confirm that all necessary Tailwind plugins are properly imported without any conflicting styles. Provide a summary of any issues found, along with specific recommendations for correcting the import dependencies and resolving potential conflicts.

Render the Button component in isolation and conduct a test to ensure it displays correctly. Verify that there are no styling errors in the console. Additionally, check the component's responsiveness and functionality by interacting with it, and document any issues found during the test. Provide a summary of the results, including any errors encountered and suggestions for resolution.

Please provide a detailed diff of the changes made to the Card component in the context of resolving styling conflicts. Highlight all modifications clearly, and explain how each change contributes to resolving the conflicts. Additionally, summarize any potential impacts these changes may have on the overall styling and functionality of the component.

Reproduce the original scenario where the Card component failed to render by following these steps: [STEP 1], [STEP 2], and [STEP 3]. Once you have recreated the issue, verify that the Card component now displays correctly after the fixes have been applied. Document any differences in behavior or appearance compared to the original failure.

Please verify the responsiveness of the Navbar component by testing it across various screen sizes: [SCREEN SIZE 1], [SCREEN SIZE 2], and [SCREEN SIZE 3]. Ensure that the styles applied do not conflict with Tailwind's breakpoints. Provide a detailed report on any issues encountered, including screenshots and specific examples of style conflicts, along with suggested fixes.

Please review the contents of the tailwind.config.js file for the project. Confirm that all required configurations are present and correctly set up. Additionally, identify any conflicting styles that may cause issues in the application. Provide a summary of your findings, including specific configurations that are intact and any conflicts that need to be resolved.

Create a base prompt that guarantees all generated components conform to Tailwind CSS styles. Specify that the AI should check for compliance with the Tailwind configuration and, in case of any styling conflicts, it should default back to the appropriate Tailwind utility classes. Provide a clear structure for how the AI should present this information, including examples of compliant styles and potential conflicts.

Create a detailed component specification for a Button that adheres to Tailwind CSS conventions. The specification should include the required Tailwind classes, such as className='[TAILWIND_CLASSES]'. Additionally, outline the expected behavior of the Button, including its hover and focus states, accessibility considerations, and any props that should be supported. Format the output as a structured document with headings for each section, such as "Classes," "Behavior," and "Accessibility.

Create a style constraint for consistent spacing in your project. Ensure that all components adhere to Tailwind CSS spacing utilities by stating: "All components must use Tailwind spacing utilities. Custom spacing classes that conflict with Tailwind are not allowed." Additionally, provide examples of acceptable spacing utilities and explain why maintaining this consistency is important for the overall design and user experience.

Create a detailed configuration note for integrating Tailwind styles with shadcn/ui components. Specify the necessary steps to ensure that all shadcn/ui components effectively utilize Tailwind classes as defined in [TAILWIND_CONFIG_PATH]. Additionally, outline potential pitfalls, such as the use of custom styles that may lead to conflicts, and provide examples of best practices to avoid these issues. Format the note as a clear guide with sections for integration steps, common conflicts, and recommended solutions.

Create a context-reload prompt to be used at the beginning of each new generation. The prompt should instruct the AI: 'Before generating any UI components, verify that all styles comply with the current Tailwind configuration. If conflicts are detected, stop the generation process and provide a detailed explanation of the conflicts along with steps to resolve them before proceeding.' Ensure the prompt is clear and actionable.