Frontend Design Review

microsoft/skills/.github/skills/frontend-design-review

作者 microsoft354361d83247无许可证已添加到 1 个工作区3.1K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库昨天更新

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.

精选仅含说明设计与创意
AI 生成的概览

审查前端界面的设计质量、设计系统合规性与无障碍性,或创建独特的生产级界面。

功能
该技能有两种模式。设计审查模式依据设计系统合规性、无障碍性、代码质量以及三大质量支柱(顺畅的洞察到行动、品质即工艺、可信赖的构建)评估现有界面。创意模式指导创建具有明确美学方向的独特界面,涵盖字体、色彩、动效、空间构图与背景。它产出带评分并按优先级排序的审查结论与建议,参考文件提供审查输出模板、审查类型修饰项、批准前检查清单以及正反示例。
适用场景
适用于拉取请求审查、设计审查、无障碍审计、设计系统合规检查、UI 与组件代码审查、响应式设计与主题测试,或创建令人印象深刻的界面。不适用于后端 API 审查、数据库架构审查、基础设施或 DevOps 工作,以及没有界面的纯业务逻辑。审查流程从识别用户任务、在设计系统中查找匹配模式并逐项评估支柱开始。设计系统工作流会检查 Storybook 或组件库中的组件,使用 Figma Dev Mode 获取精确规格,并验证使用设计令牌而非硬编码值。无障碍目标为最低 C 级(WCAG 2.1 A),理想为 B 级(WCAG 2.1 AA)。
运行要求
无需脚本或工具,仅为指令型技能;references 目录下的参考文档由模型读取。设计系统审查假定可访问组件库或 Storybook 以及 Figma 规格,但未说明需要凭据或网络访问。

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 [blocked] for the full review template.

Review Type Modifiers

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

Quick Checklist

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

Pattern Examples

See references/pattern-examples.md [blocked] 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.

来源与署名

来源:microsoft/skills位于.github/skills/frontend-design-review提交354361d

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

在 README 中添加徽章

向读者展示该技能已收录于 SourceWeft,徽章链接到本页。

“Listed on SourceWeft”徽章预览
[![Listed on SourceWeft](https://sourceweft.com/badge/skills/gh-microsoft-skills-frontend-design-review.svg)](https://sourceweft.com/skills/gh-microsoft-skills-frontend-design-review?utm_source=readme&utm_medium=badge)

举报或申请下架