What problem does it solve?
It prevents common frontend UI regressions—especially theme, layout, and rendering issues—that pass HTTP/HTML checks but still break the actual user experience.
Core Features & Use Cases
- Dark/Light Mode Specificity & Visual Leaks: Ensures CSS rules reliably override light defaults with
.dark and avoids selector patterns (like :not(.dark)) that cause light colors to bleed into dark mode.
- Evidence-Based Visual Verification: Requires screenshots for dark, light, and multiple viewports (mobile, tablet, desktop) so completeness is judged visually, not just by successful responses.
- UI Parity, Responsiveness, Accessibility, and SEO Checks: Covers i18n key parity (when applicable), mobile responsiveness, WCAG AA baseline, focus/labels, and social/SEO preview tags for every UI-affecting change.
Use case example: After updating a component’s styles and adding a theme toggle, use this checklist to confirm both themes render correctly across screen sizes, that the toggle is accessible and labeled, and that social preview metadata updates.
Quick Start
Apply the frontend-ui skill to your next HTML/CSS/template change and complete the required checklist items before finishing the UI task.