frontend-design-review

Review and create frontend interfaces against design system compliance and quality pillars.

Updated Apr 22, 2024
One-click install
npx skills add https://github.com/oligamiq/fast-explorer --skill frontend-design-review-oligamiq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: frontend-design-review
Source: https://github.com/oligamiq/fast-explorer/tree/main/.agents/skills/frontend-design-review
Command: npx skills add https://github.com/oligamiq/fast-explorer --skill frontend-design-review-oligamiq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UI implementations often drift from design system specs, ship with accessibility gaps, or fall into generic visual patterns. This Skill provides a structured framework to review frontend code against design standards or to create distinctive interfaces with a clear aesthetic direction. ## Core Features & Use Cases - Design Review Mode: Evaluate UI against three quality pillars (frictionless insight-to-action, quality craft, trustworthy building), design system compliance, Figma spec fidelity, and WCAG accessibility targets. - Creative Frontend Design Mode: Establish an intentional aesthetic direction covering typography, color, motion, and spatial composition before writing code, avoiding generic layouts. - Structured Review Output: Score and prioritize issues as blocking, major, or minor with design-system-backed recommendations. - Use Case: During a PR review of a new settings page, run a design review to verify design token usage, check focus indicators and reflow behavior, and flag competing primary actions before approval. ## Quick Start Review this UI component implementation for design system compliance, accessibility, and the three quality pillars, then list blocking and major issues.

Frequently Asked Questions about frontend-design-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a UI component against a design system?▼

Compare the implementation to Figma specs using Dev Mode, verify design tokens are used instead of hardcoded values, and check that all variants and states are implemented. Flag any deviations for design approval and document exceptions with rationale in code.

What makes a frontend design review checklist effective?▼

An effective checklist covers design system compliance, aesthetic direction, accessibility, and task flow. This Skill evaluates three pillars: frictionless insight-to-action, quality craft, and trustworthy building, with issues scored as blocking, major, or minor.

What accessibility standard does a design review check?▼

The review targets Grade C minimum, equivalent to WCAG 2.1 Level A, with Grade B (WCAG 2.1 AA) as the ideal. Checks include focus indicators, reflow behavior, and contrast requirements.

When should I not use a frontend design review process?▼

Do not use it for backend API reviews, database schema reviews, infrastructure or DevOps work, or pure business logic without UI. It is scoped strictly to frontend interfaces and user-facing components.

How do I avoid generic AI-generated UI aesthetics?▼

Commit to an aesthetic direction before coding: define purpose, tone, constraints, and differentiation. Use distinctive font pairings, cohesive color palettes with dominant accents, and intentional motion rather than overused fonts and predictable layouts.