What problem does it solve? Frontend theme changes often break in untested places: dialogs, mobile views, hover states, or nested panels end up unreadable in one of the light/dark modes. This Skill provides a structured checklist so theme adaptation work is verified systematically instead of only fixing the currently visible component. ## Core Features & Use Cases - Comprehensive Coverage Checklist: Ten sections covering mode coverage, device coverage, component structure, text hierarchy, interactive states, surface layering, form controls, mobile specifics, and code quality. - Reference Pattern Guidance: Points to established in-repo patterns (NodePreview, Chain proxy, Airport management clusters) so new changes reuse proven theme semantics instead of inventing new ones. - Delivery & Exit Criteria: Enforces explicit coverage statements, light/dark verification methods, and partial-coverage labeling when not all variants were checked. - Use Case: After updating a MUI dialog's colors in a React app, run this checklist to confirm the dialog, its mobile variant, hover/disabled states, and nested panels all render correctly in both light and dark modes before shipping. ## Quick Start Use the theme-check skill to verify my dialog color changes are fully adapted for both light and dark modes on desktop and mobile.
