visual-excellence
Visual quality standards, user flows, and use case coverage requirements. Use when building UI, reviewing frontend, or validating user experiences.
When & Why to Use This Skill
This Claude skill establishes comprehensive visual quality standards and testing protocols for frontend development. It ensures UI excellence by providing mandatory checklists for responsive design, interactive states, and WCAG 2.1 AA accessibility compliance. By integrating user flow coverage and automated visual testing strategies, it helps developers and QA teams deliver polished, accessible, and robust user experiences across all devices.
Use Cases
- Frontend Code Reviews: Use the skill to systematically audit new UI components against professional styling standards and interactive state requirements.
- Responsive Design Validation: Ensure seamless user experiences by verifying layout integrity across multiple breakpoints, from mobile (320px) to ultra-wide displays.
- Accessibility Auditing: Implement WCAG 2.1 AA standards by checking keyboard navigation, ARIA labels, and color contrast ratios during the development phase.
- Automated Visual Testing: Leverage Playwright integration to capture screenshots and compare UI states against baselines to prevent visual regressions.
- User Flow Stress Testing: Define and validate 'Happy Path', 'Error Path', and 'Edge Case' scenarios to ensure the application handles network interruptions and empty states gracefully.
| name | visual-excellence |
|---|---|
| description | Visual quality standards, user flows, and use case coverage requirements. Use when building UI, reviewing frontend, or validating user experiences. |
Visual Excellence Requirements
Mandatory Quality Checks
- ✅ All pages professionally styled
- ✅ All viewports tested (320px, 768px, 1024px, 1440px+)
- ✅ All interactive states tested
- ✅ No template artifacts or placeholders
- ✅ Smooth responsive transitions
- ✅ WCAG 2.1 AA accessibility
Interactive States
Test ALL of these for every interactive element:
| State | Description |
|---|---|
| Default | Normal appearance |
| Hover | Mouse over |
| Focus | Keyboard focus |
| Active | Being clicked/pressed |
| Disabled | Not interactive |
| Loading | Async operation in progress |
| Error | Validation/error state |
User Flow Coverage
Every feature must have complete user flows documented and tested:
- Happy Path: Standard successful completion
- Error Path: Validation failures, API errors
- Edge Cases: Empty states, max limits, special characters
- Interruptions: Network loss, session timeout, back button
Use Case Testing Matrix
| Use Case | Entry Point | Expected Outcome | Error Handling |
|---|---|---|---|
| [Action] | [Where user starts] | [Success state] | [Failure state] |
Accessibility (WCAG 2.1 AA)
- Keyboard navigable (tab order logical)
- Screen reader compatible (ARIA labels)
- Color contrast ratio ≥ 4.5:1
- Focus indicators visible
- Alt text for images
Visual Testing with Playwright MCP
- Screenshot at each breakpoint (320, 768, 1024, 1440px)
- Capture all interactive states
- Compare with baseline
- Test complete user flows
- Monitor console for errors