AI Prompts for Identify Design System Violations

Please quote the exact output of the generated component in the browser for the use-case of [USE-CASE]. Compare this output with the expected output defined by the design system for [DESIGN SYSTEM]. Highlight any specific tokens or patterns that are missing or incorrect, and provide a brief explanation of how these discrepancies affect the overall design consistency.

Please analyze the code for the generated component located in [FILE_PATH]. Identify specific areas where it deviates from the expected design system tokens and patterns. Provide a detailed report that includes the nature of the deviations, potential impacts on the user experience, and recommendations for aligning the component with the design system.

Please summarize the requirements of the design system as they pertain to the [COMPONENT NAME]. Include key principles, guidelines, and any specific elements that must be adhered to. Highlight any potential misinterpretations or areas of confusion that may exist regarding the design system and how they relate to this component.

Compare the expected behavior of the component against its actual rendered output. Structure your analysis by detailing the specific design tokens and patterns that should be present according to the design system. Include examples of both the expected and actual behaviors, and highlight any discrepancies along with suggestions for alignment with the design system.

Please analyze the generated component for the use-case of [USE-CASE] and identify any design system rules or constraints that have been violated. For each violation, quote the exact clause from the design system documentation that outlines the requirement. Additionally, provide a brief explanation of how the component deviates from the specified design constraints.

Please review the component located at [FILE_PATH] on line [LINE] for incorrect design token usage. The original token being used is [ORIGINAL_TOKEN]. I need you to replace it with the correct token, [CORRECT_TOKEN], and provide me with a diff of the changes before the replacement is applied. Ensure that the output clearly highlights the modifications made to the code.

Rewrite the component located at [FILE_PATH] to adhere to the specified design patterns. The revised component should follow this expected structure: [EXPECTED_STRUCTURE]. Please ensure that all elements are consistent with the design system, and provide a summary of the changes made to achieve this alignment.

Modify the styles in the component located at [FILE_PATH] to ensure they align with the design system. Specifically, focus on changing the following styles: [LIST_STYLES]. Please provide a detailed summary of the modifications made and any potential impact on the overall component functionality.

Please review the component located at [FILE_PATH] and assess its adherence to the required design token format. The correct format is as follows: [EXPECTED_FORMAT]. Provide a detailed list of the discrepancies you find, and then update the component to ensure it matches the specified format. Include a summary of the changes made and any potential impacts on functionality or design consistency.

Please verify the component dependencies used in the file located at [FILE_PATH]. Assess whether each dependency is compatible with the design system. If you find any outdated or incorrect dependencies, provide a detailed list of those dependencies along with suggestions for correction and updates needed to align them with the design system.

Please run a visual test of the component titled [COMPONENT NAME] by rendering it in the browser. After rendering, take a screenshot of the component and compare it with the design system specifications provided in [DESIGN SYSTEM LINK]. Identify any discrepancies between the rendered component and the design specifications, and summarize the findings in a report format that includes screenshots and notes on compliance issues.

Please display the differences in the changes made to the component located at [FILE_PATH]. Highlight all modifications and provide a detailed analysis of how each change aligns with the design system requirements. Include a summary of any discrepancies and suggestions for adjustments to ensure full compliance with the design standards.

Please re-run the original scenario that caused the design violation for the [COMPONENT NAME]. Confirm whether the output now aligns with the design system expectations. Provide a detailed comparison of the previous output and the current output, highlighting any discrepancies and confirming compliance with the design specifications.

Please test the [COMPONENT NAME] for edge case violations to verify its adherence to the design system. Document any discrepancies you find during this testing process, including specific examples of how the component deviates from the design guidelines. Provide a summary of the findings in a structured format, highlighting each issue and suggesting potential resolutions.

Please verify the state of the component located at [FILE_PATH] after implementing the recent changes. Confirm that it accurately utilizes the design system tokens and patterns as intended. Provide a detailed report on any discrepancies found, including specific examples of how the component aligns or misaligns with the design system.

Before generating any component, please verify that it adheres to the design system tokens and patterns. If you find any discrepancies, stop the process and notify the user immediately. Additionally, provide a summary of the specific areas where the component does not comply with the design system, including suggested adjustments to align it properly.

Create a comprehensive template for generating components that ensures consistency with our design system. The template should include the following structure: first, list all design tokens that must be used, represented as [LIST_TOKENS]. Next, include a reference to the design patterns that should be adhered to, linking to the guidelines at [LINK_TO_GUIDELINES]. Finally, provide a section for notes on any specific considerations or exceptions that may apply to the component being generated.

Establish a naming convention for components that aligns with the design system. The format should be '[COMPONENT_NAME]_[DESIGN_SYSTEM_TOKEN]'. Please provide a detailed explanation of the rationale behind this convention, examples of how it can be applied to various components, and guidelines for ensuring that all new components adhere to this naming structure.

Please create a self-check request template for components to ensure they align with the design system requirements. The template should include sections for confirming compliance, listing any deviations found, and proposing specific corrections for each deviation. Ensure the format is clear and structured, allowing for easy documentation and review.

Please create a reminder message for users to refer to the design system documentation before generating components. The message should read: "Always refer to the design system documentation at [LINK] before generating components. Ensure compliance with all tokens and patterns." This reminder should be displayed at the start of each session to reinforce adherence to the design system.