Frontend Design Review
MicrosoftOfficialPublished by Microsoft
- Skill
- Review and audit
- Software development
- MIT
- No issues found
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
Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/frontend-design-review/downloadUnzip 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:
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.
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
- ATTRIBUTION.mdAdded by AutoGineer875 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md6.0 KiB
- references/pattern-examples.md759 B
- references/quick-checklist.md1.5 KiB
- references/review-output-format.md2.7 KiB
- references/review-type-modifiers.md1.6 KiB
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