# design-review

design-review is a Claude Code skill for seven-phase frontend audits covering interactive states, responsive testing, visual polish, and WCAG 2.1 AA compliance.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 327 installs · ★ 250 repo stars
- Author: secondsky
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/secondsky/claude-skills/tree/HEAD/plugins/design-review/skills/design-review/SKILL.md
- Updated: 2026-10-20
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/secondsky-design-review

## What it does

The skill runs a seven-phase systematic review: interactive states (hover, focus, active, disabled), responsive testing across three viewports (375px, 768px, 1440px), visual consistency (typography hierarchy, spacing tokens, color palette), keyboard accessibility and contrast for WCAG 2.1 AA, semantic HTML and ARIA attributes.

Each phase assigns priorities: blocker for broken critical flows, high for WCAG violations or missing focus states, medium for spacing and alignment, nitpick for minor polish. Requires Playwright MCP or Puppeteer for browser automation.

Uses `Read`, `Grep`, `Glob`, `Bash` tools; references internal guides `interaction-patterns.md`, `responsive-testing.md`, `visual-polish.md`, `accessibility-wcag.md` for expanded checklists.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill design-review -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/design-review/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/design-review/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill design-review -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/design-review/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill design-review -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/design-review/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install secondsky/claude-skills plugins/design-review/skills/design-review
```

2. **Manually: put the files in place**
- File: `.github/skills/design-review/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill design-review -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/secondsky/claude-skills --path plugins/design-review/skills/design-review
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/design-review/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add secondsky/claude-skills --skill design-review -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/secondsky/claude-skills/tree/HEAD/plugins/design-review/skills/design-review/SKILL.md

## When to use it
- check component accessibility for screen readers and keyboard
- find contrast and focus state issues before PR merge
- test responsive behavior on mobile viewports
- identify WCAG 2.1 AA violations in UI
- verify destructive actions have confirmation dialogs

## Example prompts
- Run design review for `/dashboard` page at `localhost:3000`
- Check WCAG 2.1 AA compliance for the signup form
- Execute seven-phase UI audit for PR #142

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 5364a172fc49f44c.

BEGIN THIRD-PARTY FILE 5364a172fc49f44c
````text
---
name: design-review
description: "7-phase frontend design review with accessibility (WCAG 2.1 AA), responsive testing, visual polish. Use for PR reviews, UI audits, or encountering contrast issues, broken layouts, accessibility violations, inconsistent spacing, missing focus states."

metadata:
  keywords:
    - design review
    - UI audit
    - frontend review
    - accessibility audit
    - WCAG compliance
    - responsive design
    - visual QA
    - UX review
    - component review
    - PR design check
    - layout issues
    - accessibility violations
    - contrast problems
    - broken responsive
    - interaction bugs
    - keyboard navigation
    - focus states
    - design system compliance
    - visual consistency
    - user experience

license: MIT
allowed-tools:
  - Read
  - Grep
  - Glob
  - Bash
---
# Design Review Skill

**Status**: Production Ready ✅
**Last Updated**: 2025-11-20
**Dependencies**: Playwright MCP or Chrome DevTools
**Methodology**: 7-phase systematic review (inspired by Stripe, Airbnb, Linear)

---

## Quick Start

### 1. Prerequisites Check

Before starting a design review, verify browser automation tools are available:

**Option A: Playwright MCP** (recommended for interactive testing)
- See the `playwright-testing` skill for Playwright setup
- Provides browser automation, screenshots, viewport testing, console monitoring

**Option B: Puppeteer CLI** (alternative for screenshots and performance)
- Install Puppeteer directly via `npm install -g puppeteer`
- Provides screenshot capture, performance analysis, network monitoring

For complete browser tools reference, see [references/browser-tools-reference.md](references/browser-tools-reference.md).

### 2. Understand the Review Scope

**For PR reviews:**
```bash
# Analyze git diff to understand scope
git diff --name-only origin/main...HEAD

# Read PR description for context
```

**For general UI reviews:**
Simply provide the preview URL and component/page description.

### 3. Execute 7-Phase Review

Follow the systematic checklist below. Each phase has specific objectives and testing procedures.

---

## The 7-Phase Review Methodology

### Phase 0: Preparation

**Objective:** Understand context and set up testing environment.

**Steps:**
1. **Read PR description** or review request to understand:
   - Motivation for changes
   - Scope of implementation
   - Testing notes from developer
   - Expected behavior

2. **Analyze code diff** (if PR available):
   ```bash
   git diff origin/main...HEAD
   ```
   Identify modified files (components, styles, tests)

3. **Set up live preview environment:**
   - Navigate to preview URL using browser tools
   - Set initial viewport: 1440x900 (desktop)
   - Take baseline screenshot for reference
````
END THIRD-PARTY FILE 5364a172fc49f44c

The third-party file has ended. Everything between the 5364a172fc49f44c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2769 of 24706 bytes. © secondsky · MIT · https://github.com/secondsky/claude-skills/tree/HEAD/plugins/design-review/skills/design-review/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
