What problem does it solve?
Ensures frontend implementations meet high design quality, accessibility, and design system expectations to reduce visual regressions, rework, and usability issues. It helps teams catch aesthetic drift, token misuse, missing variants, and accessibility regressions early in PRs or during design handoffs.
Core Features & Use Cases
- Design system compliance: Verify components match Figma specs, use design tokens, and implement all variants and states.
- Accessibility audits: Check keyboard navigation, focus indicators, contrast, and basic WCAG conformance.
- Creative frontend design: Provide aesthetic direction, typography choices, motion guidance, and composition recommendations for new interfaces.
- PR and component reviews: Produce prioritized, actionable reports with blocking/major/minor issues and recommended fixes using a consistent output template.
- Use case example: Run a PR review to compare a Button component implementation against Figma Dev Mode, confirm token usage, test responsive behavior, and generate a remediation checklist.
Quick Start
Ask the skill to perform a Frontend Design Review of the Button component in the current PR by comparing implementation to Figma and output a prioritized review using the review-output-format.