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)

檢舉或申請下架