AI Prompts for Resolving Tailwind Style Conflicts

Please identify the conflicting Tailwind class that is causing issues with my existing styles. Quote the exact class name that was generated and specify the component where this conflict occurs. Additionally, provide the expected class name that should have been applied in this scenario.

Please analyze the following component code for style conflicts: [COMPONENT CODE]. Ensure to include all relevant Tailwind CSS classes and any custom utility classes that are applied. After reviewing, provide a detailed explanation of the conflicts and suggest potential solutions to resolve them.

Please interpret the original style instruction regarding the Tailwind styles in the context of the use-case: BOLT-TAILWIND-STYLING-CONFLICT. Explain your understanding of the expected outcome for the styles applied, detailing any specific elements or classes that are crucial to achieving this outcome. Additionally, provide a brief summary of potential conflicts that may arise from the current implementation and how they might affect the final design.

Compare the expected styles with the actual styles being rendered in the component related to the use-case of BOLT and Tailwind. List the expected Tailwind classes in one column and the actual classes applied in another column. Additionally, provide a brief explanation of any discrepancies and potential reasons for the styling conflicts, along with suggestions for resolving these issues. Format the output as a table for clarity.

Please analyze the generated styles for the use-case of [USE-CASE] and identify the specific Tailwind rule or utility class that has been violated. Quote the exact clause from the Tailwind documentation that outlines the expected behavior for this rule. Additionally, provide a brief explanation of how this violation affects the overall styling and suggest potential solutions to resolve the conflict.

Identify the conflicting Tailwind class in the component located at [FILE] on line [LINE]. Modify the class by replacing it with the correct Tailwind class that aligns with the expected styling rules. Provide a brief explanation of the changes made and how they resolve the conflict, ensuring that the component maintains its intended design and functionality.

Rewrite the styling for the component located at [FILE]:[LINE] to ensure that it strictly adheres to Tailwind's utility classes. Provide a detailed list of the approved Tailwind classes that should be utilized, and explain how to implement these classes to prevent any styling conflicts. Additionally, include examples of the revised code that demonstrate the correct usage of these classes in the component.

Identify the conflicting styles in the component located at [FILE]:[LINE]. Make a scoped change by wrapping these styles in a conditional check to prevent conflicts. Ensure that the appropriate Tailwind classes are applied based on the current state of the component. Provide a clear explanation of the changes made and how they resolve the styling conflict.

Enforce the formatting rules for Tailwind classes in the component located at [FILE] on line [LINE]. Analyze the current class application and ensure that they are ordered correctly according to Tailwind's recommended patterns. Provide a revised code snippet that reflects the necessary changes and explain the adjustments made to improve adherence to these formatting rules.

Examine the imports in [FILE] to identify any dependencies that could potentially conflict with Tailwind styling. Provide a detailed list of any outdated or incorrectly imported dependencies, and suggest the necessary updates or corrections to ensure all required Tailwind dependencies are properly integrated. Additionally, explain how each identified issue may impact the styling and functionality of the project.

Please conduct a visual test of the component to verify that the correct Tailwind styles are applied. Ensure that you check for any remaining style conflicts in the UI and provide a detailed report on your findings. Include screenshots of the component before and after the resolution, highlighting any discrepancies or issues that persist.

Please provide a detailed comparison of the changes made to [FILE] to verify the resolution of the styling conflict. Highlight the specific lines where the Tailwind classes were modified, and explain the impact of these changes on the overall styling. Additionally, include a summary of any remaining issues or considerations that should be addressed.

Replay the original scenario that exhibited the style conflict related to [BOLT TAILWIND STYLING CONFLICT]. Confirm that the issue has been resolved by checking if the expected styles are now rendering correctly. Provide a detailed report on any discrepancies observed during the replay, including screenshots if necessary, and outline the steps taken to verify the resolution.

Please analyze the component for potential edge case regressions related to styling conflicts with Tailwind. Ensure that all states of the component, including [STATE 1], [STATE 2], and [STATE 3], render correctly without introducing any new style issues. Provide a detailed report on any discrepancies found, including screenshots and suggestions for resolving any identified conflicts.

Please verify the final output state of the component in the browser. Check that the expected TAILWIND CSS CLASSES are correctly applied and ensure there are no conflicting styles present. Provide a detailed report on any discrepancies found, including specific classes that are missing or conflicts that need to be resolved.

Before rendering any component in the [PROJECT NAME], please verify that all Tailwind CSS classes are applied correctly according to the Tailwind documentation. If any conflicts are detected, stop the rendering process and alert the developer with a detailed message about the specific conflict. Ensure that this check is integrated into the development workflow to prevent any styling issues from recurring.

Create a conversation-starter template that includes a detailed checklist for verifying Tailwind styles before any component deployment. The checklist should include specific items such as: [CHECK 1], [CHECK 2], and [CHECK 3]. Additionally, provide guidance on what actions to take if any of the checks fail, emphasizing the importance of halting the deployment process to prevent style conflicts. Format the output as a clear and concise list for easy reference.

Draft a project specification message regarding the styling conventions for components in the context of a bolt-tailwind-styling-conflict use case. The message should clearly state that all components must utilize Tailwind utility classes exclusively. Additionally, it should emphasize that custom styles should be avoided unless absolutely necessary and must be documented thoroughly. Please format this message in a professional tone suitable for team communication, ensuring clarity and adherence to the specified guidelines.

Create a naming convention guideline for Tailwind CSS classes to prevent conflicts with custom utility classes. Specify that all Tailwind classes should be prefixed with 'TW-' to clearly distinguish them. Additionally, explain the importance of this convention in maintaining a clean and organized codebase, and provide examples of how this can be implemented in a project.

Please create a self-check request for an agent to run before deployment. The request should include a directive to check for any style conflicts in the components. If any conflicts are detected, the agent should list them and halt the deployment process until all issues are resolved. Format the output clearly to highlight the conflicts and steps needed for resolution.