ui-consistency

To standardize UI design patterns, apply design-system-driven rules that enforce consistent styling, accessible interactions, and visual tokens across forms, tables, buttons, and dialogs to reduce UI debt and inconsistency.

The best way to ensure accessibility for tooltips and dialogs is to implement explicit guidelines specifying focus states, aria-labels, and disabled state behaviors to enforce coherent and accessible user interactions.

You can implement decision trees for UI element visibility by applying frontmatter-based guidelines and in-skill body instructions that specify when and how components should be displayed and interacted with across modules.

Yes, these component guidelines apply to empty states and loading states, providing standardized visual tokens and accessibility patterns to ensure uniform user experiences across all application features and modules.

UI inconsistency happens as features evolve and lack standardized patterns; design systems solve this by enforcing uniform components, accessible patterns, and explicit rules across all modules to reduce UI debt.

Yes, you need explicit frontmatter-based guidelines to enforce disabled states, accessibility rules, and visual tokens, ensuring that developers and designers follow consistent component patterns across the application.