Frontend Design Review
Review UI implementations against design quality standards OR create distinctive, production-grade frontend interfaces
Two Modes
Mode 1: Design Review
Evaluate existing UI for:
- Design system compliance
- Three quality pillars (Frictionless, Quality Craft, Trustworthy)
- Accessibility
- Code quality
Mode 2: Creative Frontend Design
Create distinctive interfaces that:
- Avoid generic "AI slop" aesthetics
- Have clear conceptual direction
- Execute with precision
Design Review
Design System Workflow
Before implementing:
- Review component in your Storybook / component library for API and usage
- Use Figma Dev Mode to get exact specs (spacing, tokens, properties)
- Implement using design system components + design tokens
During review:
- Compare implementation to Figma design
- Verify design tokens are used (not hardcoded values)
- Check all variants/states are implemented correctly
- Flag deviations (needs design approval)
If component doesn't exist:
- Check if existing component can be adapted
- Reach out to design for new component creation
- Document exception and rationale in code
Review Process
- Identify user task
- Check design system for matching patterns
- Evaluate aesthetic direction
- Identify scope (component, feature, or flow)
- Evaluate each pillar
- Score and prioritize issues (blocking/major/minor)
- Provide recommendations with design system examples
Core Principles
- Task completion: Minimum clicks. Every screen answers "What can I do?" and "What happens next?"
- Action hierarchy: 1-2 primary actions per view. Progressive disclosure for secondary.
- Onboarding: Explain features on introduction. Smart defaults over configuration.
- Navigation: Clear entry/exit points. Back/cancel always available. Breadcrumbs for deep flows.
Quality Pillars
1. Frictionless Insight to Action
Evaluate: Task completable in ≤3 interactions? Primary action obvious and singular?
Red flags:
- Excessive clicks
- Multiple competing primary buttons
- Buried actions
- Dead ends
2. Quality is Craft
Evaluate:
- Design system compliance: matches Figma specs, uses design tokens
- Aesthetic direction: distinctive typography, cohesive colors, intentional motion
- Accessibility: Grade C minimum (WCAG 2.1 A), Grade B ideal (WCAG 2.1 AA)
Red flags:
- Generic AI aesthetics
- Hardcoded values
- Implementation doesn't match Figma
- Broken reflow
- Missing focus indicators
3. Trustworthy Building
Evaluate:
- AI transparency: disclaimer on AI-generated content
- Error transparency: actionable error messages
Red flags:
- Missing AI disclaimers
- Opaque errors without guidance
Creative Frontend Design
Before coding, commit to an aesthetic direction:
- Purpose: What problem does this solve? Who uses it?
- Tone: minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft/pastel, industrial, etc.
- Constraints: Framework, performance, accessibility requirements.
- Differentiation: What makes this distinctive and context-appropriate?
Aesthetics Guidelines
| Element |
Guidance |
| Typography |
Distinctive fonts that elevate aesthetics. Pair a display font with a refined body font. Avoid: Inter, Roboto, Arial, Space Grotesk. |
| Color & Theme |
Cohesive palette with CSS variables. Dominant colors + sharp accents > timid, evenly-distributed palettes. |
| Motion |
CSS-only preferred. One well-orchestrated page load with staggered reveals > scattered micro-interactions. |
| Spatial Composition |
Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density. |
| Backgrounds |
Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays. |
AVOID:
- Overused fonts
- Cliché color schemes
- Predictable layouts
- Cookie-cutter design without context-specific character
Match implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.
Accessibility Quick Check
Grade C (WCAG 2.1 A) — Minimum
Grade B (WCAG 2.1 AA) — Target
Grade A (WCAG 2.1 AAA) — Stretch
Review Output Format
## Summary
[One-line assessment: pass/needs work/blocking issues]
## Pillar Scores
| Pillar | Score | Notes |
|--------|-------|-------|
| Frictionless | ⚠️ | 4 clicks to complete primary task |
| Quality Craft | ✅ | Design system compliant |
| Trustworthy | ❌ | Missing AI disclaimer |
## Issues
### Blocking
1. [Issue]: [Description] → [Fix]
### Major
1. [Issue]: [Description] → [Fix]
### Minor
1. [Issue]: [Description] → [Fix]
## Recommendations
[Prioritized next steps with design system references]
Review Type Modifiers
PR Review Focus
- Code quality and patterns
- Design token usage
- Component API compliance
- Breaking changes to shared components
Creative Review Focus
- Aesthetic distinctiveness
- Conceptual coherence
- Technical execution of vision
- Performance impact of effects
Accessibility Audit Focus
- WCAG conformance level
- Assistive technology compatibility
- Keyboard navigation paths
- Screen reader announcements
Design System Compliance Focus
- Token usage vs hardcoded values
- Component variants coverage
- Figma-to-code accuracy
- Documentation updates needed
Quick Checklist
Pre-Approval
Design System:
React 19 Patterns (if applicable):
Aesthetic Quality:
Frictionless:
Quality Craft:
Trustworthy:
Modern Stack Reference
| Layer |
Recommended |
Notes |
| Framework |
React 19 |
useActionState, useOptimistic, use() |
| Styling |
Tailwind + CSS vars |
Design tokens via variables |
| Components |
shadcn/ui + Radix |
Open Code philosophy |
| Server state |
TanStack Query |
Caching, optimistic updates |
| Client state |
Zustand |
Simple, TypeScript-first |
| Forms |
React Hook Form + Zod |
Or native form actions |
| Testing |
Vitest + Testing Library |
Test behavior, not implementation |
Related Skills
This skill complements:
- ui-ux-design — Accessibility patterns, design system foundations
- Frontend agent — React 19 patterns, full component examples
- graphic-design — Visual design principles, SVG graphics
- code-review — Technical review patterns
Acknowledgments
Design review principles and quality pillar framework created by @Quirinevwm.
Creative frontend guidance inspired by Anthropic's frontend-design skill.
1---2name: frontend-design-review-43description: Review and create distinctive frontend interfaces — design system compliance, three quality pillars (Frictionless, Quality Craft, Trustworthy), accessibility4tier: standard5applyTo: '**/*.{html,jsx,tsx,vue,svelte,css,scss},**/components/**,**/ui/**'6currency: 2026-04-227metadata:8 source: https://skillmd.com/skills/fabioc-aloha/frontend-design-review-49---1011# Frontend Design Review1213> Review UI implementations against design quality standards **OR** create distinctive, production-grade frontend interfaces1415---1617## Two Modes1819### Mode 1: Design Review2021Evaluate existing UI for:22- Design system compliance23- Three quality pillars (Frictionless, Quality Craft, Trustworthy)24- Accessibility25- Code quality2627### Mode 2: Creative Frontend Design2829Create distinctive interfaces that:30- Avoid generic "AI slop" aesthetics31- Have clear conceptual direction32- Execute with precision3334---3536## Design Review3738### Design System Workflow3940**Before implementing:**411. Review component in your Storybook / component library for API and usage422. Use Figma Dev Mode to get exact specs (spacing, tokens, properties)433. Implement using design system components + design tokens4445**During review:**461. Compare implementation to Figma design472. Verify design tokens are used (not hardcoded values)483. Check all variants/states are implemented correctly494. Flag deviations (needs design approval)5051**If component doesn't exist:**521. Check if existing component can be adapted532. Reach out to design for new component creation543. Document exception and rationale in code5556### Review Process57581. Identify user task592. Check design system for matching patterns603. Evaluate aesthetic direction614. Identify scope (component, feature, or flow)625. Evaluate each pillar636. Score and prioritize issues (blocking/major/minor)647. Provide recommendations with design system examples6566### Core Principles6768- **Task completion**: Minimum clicks. Every screen answers "What can I do?" and "What happens next?"69- **Action hierarchy**: 1-2 primary actions per view. Progressive disclosure for secondary.70- **Onboarding**: Explain features on introduction. Smart defaults over configuration.71- **Navigation**: Clear entry/exit points. Back/cancel always available. Breadcrumbs for deep flows.7273---7475## Quality Pillars7677### 1. Frictionless Insight to Action7879**Evaluate:** Task completable in ≤3 interactions? Primary action obvious and singular?8081**Red flags:**82- Excessive clicks83- Multiple competing primary buttons84- Buried actions85- Dead ends8687### 2. Quality is Craft8889**Evaluate:**90- **Design system compliance**: matches Figma specs, uses design tokens91- **Aesthetic direction**: distinctive typography, cohesive colors, intentional motion92- **Accessibility**: Grade C minimum (WCAG 2.1 A), Grade B ideal (WCAG 2.1 AA)9394**Red flags:**95- Generic AI aesthetics96- Hardcoded values97- Implementation doesn't match Figma98- Broken reflow99- Missing focus indicators100101### 3. Trustworthy Building102103**Evaluate:**104- **AI transparency**: disclaimer on AI-generated content105- **Error transparency**: actionable error messages106107**Red flags:**108- Missing AI disclaimers109- Opaque errors without guidance110111---112113## Creative Frontend Design114115Before coding, commit to an aesthetic direction:116117- **Purpose**: What problem does this solve? Who uses it?118- **Tone**: minimal, maximalist, retro-futuristic, organic, luxury, playful, editorial, brutalist, art deco, soft/pastel, industrial, etc.119- **Constraints**: Framework, performance, accessibility requirements.120- **Differentiation**: What makes this distinctive and context-appropriate?121122### Aesthetics Guidelines123124| Element | Guidance |125|---------|----------|126| **Typography** | Distinctive fonts that elevate aesthetics. Pair a display font with a refined body font. **Avoid**: Inter, Roboto, Arial, Space Grotesk. |127| **Color & Theme** | Cohesive palette with CSS variables. Dominant colors + sharp accents > timid, evenly-distributed palettes. |128| **Motion** | CSS-only preferred. One well-orchestrated page load with staggered reveals > scattered micro-interactions. |129| **Spatial Composition** | Asymmetry, overlap, diagonal flow, grid-breaking elements, generous negative space OR controlled density. |130| **Backgrounds** | Gradient meshes, noise textures, geometric patterns, layered transparencies, dramatic shadows, grain overlays. |131132**AVOID:**133- Overused fonts134- Cliché color schemes135- Predictable layouts136- Cookie-cutter design without context-specific character137138Match implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.139140---141142## Accessibility Quick Check143144### Grade C (WCAG 2.1 A) — Minimum145146- [ ] All interactive elements keyboard accessible147- [ ] Focus visible on all focusable elements148- [ ] Images have alt text149- [ ] Color is not the only means of conveying information150- [ ] Form fields have labels151152### Grade B (WCAG 2.1 AA) — Target153154- [ ] Color contrast ≥4.5:1 (text), ≥3:1 (large text, UI components)155- [ ] Focus indicators visible and clear156- [ ] Text resizable to 200% without loss of functionality157- [ ] Keyboard focus order logical158- [ ] Error messages identify the field and describe the error159160### Grade A (WCAG 2.1 AAA) — Stretch161162- [ ] Color contrast ≥7:1 (text)163- [ ] No timing-based interactions without controls164- [ ] Sign language for video content165- [ ] Extended audio descriptions166167---168169## Review Output Format170171```markdown172## Summary173[One-line assessment: pass/needs work/blocking issues]174175## Pillar Scores176| Pillar | Score | Notes |177|--------|-------|-------|178| Frictionless | ⚠️ | 4 clicks to complete primary task |179| Quality Craft | ✅ | Design system compliant |180| Trustworthy | ❌ | Missing AI disclaimer |181182## Issues183184### Blocking1851. [Issue]: [Description] → [Fix]186187### Major1881. [Issue]: [Description] → [Fix]189190### Minor1911. [Issue]: [Description] → [Fix]192193## Recommendations194[Prioritized next steps with design system references]195```196197---198199## Review Type Modifiers200201### PR Review Focus202203- Code quality and patterns204- Design token usage205- Component API compliance206- Breaking changes to shared components207208### Creative Review Focus209210- Aesthetic distinctiveness211- Conceptual coherence212- Technical execution of vision213- Performance impact of effects214215### Accessibility Audit Focus216217- WCAG conformance level218- Assistive technology compatibility219- Keyboard navigation paths220- Screen reader announcements221222### Design System Compliance Focus223224- Token usage vs hardcoded values225- Component variants coverage226- Figma-to-code accuracy227- Documentation updates needed228229---230231## Quick Checklist232233### Pre-Approval234235**Design System:**236- [ ] Uses design system components (not custom implementations)237- [ ] Uses design tokens (not hardcoded colors/spacing)238- [ ] Matches Figma specs within tolerance239- [ ] All variants/states implemented240241**React 19 Patterns (if applicable):**242- [ ] Forms use `useActionState` (not manual useState + fetch)243- [ ] Optimistic updates use `useOptimistic` hook244- [ ] Server state via TanStack Query (not local state for fetched data)245- [ ] Submit buttons use `useFormStatus` from design system246- [ ] No unnecessary `forwardRef` (React 19 accepts ref as prop)247248**Aesthetic Quality:**249- [ ] Distinctive typography choice250- [ ] Cohesive color palette via CSS variables251- [ ] Intentional motion (or explicit choice of none)252- [ ] Appropriate visual density253254**Frictionless:**255- [ ] Primary action ≤3 interactions256- [ ] Clear action hierarchy257- [ ] No dead ends258- [ ] Progress indicators for multi-step flows259- [ ] Optimistic UI for perceived performance260261**Quality Craft:**262- [ ] Responsive/reflow works263- [ ] Focus indicators visible (`:focus-visible` with ring)264- [ ] Loading states present (skeleton > spinner)265- [ ] Error states handled with `role="alert"`266267**Trustworthy:**268- [ ] AI content disclosed269- [ ] Errors are actionable270- [ ] User data handling transparent271272---273274## Modern Stack Reference275276| Layer | Recommended | Notes |277|-------|-------------|-------|278| Framework | React 19 | useActionState, useOptimistic, use() |279| Styling | Tailwind + CSS vars | Design tokens via variables |280| Components | shadcn/ui + Radix | Open Code philosophy |281| Server state | TanStack Query | Caching, optimistic updates |282| Client state | Zustand | Simple, TypeScript-first |283| Forms | React Hook Form + Zod | Or native form actions |284| Testing | Vitest + Testing Library | Test behavior, not implementation |285286## Related Skills287288This skill complements:289- **ui-ux-design** — Accessibility patterns, design system foundations290- **Frontend** agent — React 19 patterns, full component examples291- **graphic-design** — Visual design principles, SVG graphics292- **code-review** — Technical review patterns293294---295296## Acknowledgments297298Design review principles and quality pillar framework created by [@Quirinevwm](https://github.com/Quirinevwm).299Creative frontend guidance inspired by [Anthropic's frontend-design skill](https://github.com/anthropics/skills/tree/main/skills/frontend-design).