frontend-design-review

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

1|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/AlahmadiQ8/sre-agent-demo --skill frontend-design-review-alahmadiq8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: frontend-design-review
Source: https://github.com/AlahmadiQ8/sre-agent-demo/tree/main/.claude/skills/frontend-design-review
Command: npx skills add https://github.com/AlahmadiQ8/sre-agent-demo --skill frontend-design-review-alahmadiq8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? UI work often ships with generic aesthetics, hardcoded values instead of design tokens, accessibility gaps, and deviations from Figma specs. This Skill provides a structured framework to review existing UI implementations or create distinctive frontend designs that meet design system and quality standards. ## Core Features & Use Cases - Design Review Mode: Evaluate UI against three quality pillars (Frictionless Insight to Action, Quality Craft, Trustworthy Building), design system compliance, and accessibility, with issues prioritized as blocking, major, or minor. - Creative Frontend Mode: Establish a clear aesthetic direction covering typography, color, motion, spatial composition, and backgrounds before writing interface code. - Review Type Modifiers: Adjust focus for PR reviews, creative reviews, design reviews, accessibility audits, and design system compliance audits. - Use Case: During a PR review of a new dashboard component, run a design review to verify Figma Dev Mode specs, design token usage, keyboard navigation, and dark mode contrast, then output a scored pillar assessment with actionable recommendations. ## Quick Start Review this UI component implementation for design system compliance, accessibility, and the three quality pillars, then provide a scored assessment with prioritized 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 for design system compliance?

Compare the implementation against Figma specs using Dev Mode, verify design tokens are used instead of hardcoded values, and confirm all variants and states match the design system. Document any deviations with rationale and design approval.

What are the three quality pillars for frontend design review?

The pillars are Frictionless Insight to Action (tasks completable in three or fewer interactions with one clear primary action), Quality Craft (design system compliance, distinctive aesthetics, accessibility), and Trustworthy Building (AI disclaimers and actionable error messages).

How do I avoid generic AI-looking frontend design?

Commit to a clear aesthetic direction before coding: choose distinctive typography, a cohesive color palette with CSS variables, intentional motion, and asymmetric composition. Avoid overused fonts like Inter and Roboto, cliched color schemes, and cookie-cutter layouts.

What accessibility standard does a frontend design review check?

Reviews target Grade C minimum (WCAG 2.1 Level A) with Grade B ideal (WCAG 2.1 Level AA). Checks include keyboard navigation, focus indicators, contrast ratios, ARIA attributes, and testing in light, dark, and high contrast modes.

When should I not use a frontend design review?

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