Generated banner for Frontend Design Review
Generated logo for Frontend Design Review

Frontend Design Review

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Review and audit
  • Software development
  • MIT
  • No issues found

From the author

Review and create distinctive, production-grade frontend interfaces with high design quality and design system compliance. Evaluates using three pillars: frictionless insight-to-action, quality craft, and trustworthy building. USE FOR: PR reviews, design reviews, accessibility audits, design system compliance checks, creative frontend design, UI code review, component reviews, responsive design checks, theme testing, and creating memorable UI. DO NOT USE FOR: Backend API reviews, database schema reviews, infrastructure or DevOps work, pure business logic without UI, or non-frontend code.
— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a framework for evaluating and building frontend interfaces. It operates in two modes: a design review mode for auditing existing UI against design system compliance and quality pillars, and a creative design mode for generating new interfaces with specific aesthetic directions. It emphasizes the use of design tokens, accessibility standards, and clear task-oriented design.

What it does

  • Evaluates UI implementations against design system specifications and Figma tokens.
  • Provides a checklist for design system compliance and accessibility.
  • Guides the creation of new interfaces based on specific aesthetic themes and constraints.
  • Assesses interfaces based on frictionless task completion and action hierarchy.
  • Checks for the presence of AI disclaimers and actionable error messaging.
  • Offers a structured format for reporting UI review findings.

When to use it

  • During pull request reviews to ensure design system adherence.
  • When auditing existing components for accessibility and token usage.
  • When designing new frontend interfaces that require a distinct aesthetic direction.
  • To verify that UI implementations match Figma design specifications.
  • When testing component variants and states across different themes.

Advantages

  • Promotes consistency through strict design system and token usage.
  • Encourages intentional aesthetic choices over generic design patterns.
  • Provides a clear, repeatable process for UI audits and reviews.
  • Focuses on user-centric design principles like task efficiency and clear navigation.
  • Supports accessibility and error transparency in frontend builds.

Usage examples

“Review this PR for design system compliance and accessibility.”
The agent evaluates the code against Figma specs, checks for hardcoded values, and verifies accessibility standards.
“Help me design a brutalist landing page for a new product.”
The agent suggests a typography and color palette, layout strategies, and implementation steps aligned with the requested aesthetic.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/microsoft/frontend-design-review/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip frontend-design-review.zip -d .agents/skills

Documentation by Microsoft

Frontend Design Review

Review UI implementations against design quality standards and your design system OR create distinctive, production-grade frontend interfaces from scratch.

Two Modes

Mode 1: Design Review

Evaluate existing UI for design system compliance, three quality pillars (Frictionless, Quality Craft, Trustworthy), accessibility, and code quality.

Mode 2: Creative Frontend Design

Create distinctive interfaces that avoid generic "AI slop" aesthetics, have clear conceptual direction, and execute with precision.


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
  • 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, cliched color schemes, predictable layouts, cookie-cutter design without context-specific character.

Match implementation complexity to vision. Maximalist = elaborate code. Minimalist = restraint and precision.


Design Review

Design System Workflow

Before implementing:

  1. Review component in your Storybook / component library for API and usage

  2. Use Figma Dev Mode to get exact specs (spacing, tokens, properties)

  3. Implement using design system components + design tokens

During review:

  1. Compare implementation to Figma design

  2. Verify design tokens are used (not hardcoded values)

  3. Check all variants/states are implemented correctly

  4. Flag deviations (needs design approval)

If component doesn't exist:

  1. Check if existing component can be adapted

  2. Reach out to design for new component creation

  3. Document exception and rationale in code

Review Process
  1. Identify user task

  2. Check design system for matching patterns

  3. Evaluate aesthetic direction

  4. Identify scope (component, feature, or flow)

  5. Evaluate each pillar

  6. Score and prioritize issues (blocking/major/minor)

  7. 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.


Review Output Format

See references/review-output-format.md for the full review template.

Review Type Modifiers

See references/review-type-modifiers.md for context-specific review focus areas (PR, Creative, Design, Accessibility).

Quick Checklist

See references/quick-checklist.md for the pre-approval checklist covering design system compliance, aesthetic quality, frictionless, quality craft, and trustworthy pillars.

Pattern Examples

See references/pattern-examples.md for good/bad examples of creative frontend and design system review work.


Acknowledgments

Creative frontend principles inspired by Anthropic's frontend-design skill. Design review principles and quality pillar framework created by @Quirinevwm for systematic UI evaluation.

Files

references/review-type-modifiers.md

Review Type Modifiers

Adjust focus based on review context:

PR Review

  • Focus: Code implementation, design system component usage, design token usage, accessibility in code

  • Check: Proper imports, design tokens used (not hardcoded), ARIA attributes present

  • Verify: Component matches Figma specs using Dev Mode

Creative Frontend Review

  • Focus: Aesthetic direction, typography choices, visual distinctiveness, motion design

  • Check: Clear conceptual intent, avoiding generic AI patterns, cohesive execution

  • Verify: Implementation complexity matches vision (maximalist needs elaborate code, minimalist needs precision)

Design Review

  • Focus: User flows, interaction patterns, visual hierarchy, navigation, design system alignment

  • Check: Task completion path, action hierarchy, progressive disclosure

  • Verify: All components exist in design system or have documented exceptions

Accessibility Audit

  • Focus: Deep dive Quality Craft pillar

  • Check: Keyboard testing, screen reader testing, contrast ratios, ARIA patterns

  • Test with: Screen readers (NVDA, JAWS, Narrator), keyboard only, 200% zoom

  • Verify: Design system accessibility features are properly implemented

Design System Compliance Audit

  • Focus: Deep dive design system usage

  • Check: All components match Figma specs, design tokens used throughout, no hardcoded values

  • Test: Compare implementation side-by-side with Figma using Dev Mode

  • Verify: Component variants, spacing, colors, typography all match design system

  • Document: Any deviations with rationale and plan to align

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Microsoft
Publisher
Microsoft (Official)
Source
microsoft/skills · .github/skills/frontend-design-review · commit 0696600
Licence
MIT License (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download frontend-design-review.zip