MCP HubMCP Hub
스킬 목록으로 돌아가기

review-web-design

pjt222
업데이트됨 2 days ago
7 조회
17
2
17
GitHub에서 보기
디자인design

정보

이 스킬은 웹 디자인의 레이아웃, 타이포그래피, 색상, 간격 및 반응형 동작을 분석하여 디자인 원칙에 기반한 개선 권장사항을 제공합니다. 개발 전 목업을 검토하고, 구현된 사이트를 평가하며, 브랜드 일관성을 확인하는 데 사용됩니다. 이 도구는 웹 콘텐츠를 직접 가져와 평가할 수 있어 실행 가능한 디자인 피드백을 얻기에 이상적입니다.

빠른 설치

Claude Code

추천
기본
npx skills add pjt222/agent-almanac -a claude-code
플러그인 명령대체
/plugin add https://github.com/pjt222/agent-almanac
Git 클론대체
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/review-web-design

Claude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요

문서

Review Web Design

Evaluate a web design for visual quality, consistency, and effectiveness across devices.

When to Use

  • Reviewing a design mockup or prototype before development
  • Assessing an implemented site for design quality
  • Design review feedback session
  • Brand consistency across pages or sections
  • Responsive design behaviour across breakpoints

Inputs

  • Required: Design to review (URL, mockup, screenshots, or source)
  • Optional: Brand guidelines or design system docs
  • Optional: Target audience description
  • Optional: Reference designs or competitor examples
  • Optional: Specific areas of concern

Procedure

Step 1: Assess Visual Hierarchy

Visual hierarchy guides the user's eye through content by importance.

  • Clear focal point: Obvious entry point on each page?
  • Heading hierarchy: Headings descend logically (H1 → H2 → H3)?
  • Size contrast: Important elements larger than supporting elements?
  • Colour contrast: CTAs and key actions visually prominent?
  • Whitespace: Spacing separates logical groups effectively?
  • Reading flow: Layout follows natural reading pattern (F-pattern, Z-pattern)?
## Visual Hierarchy Assessment
| Page/Section | Focal Point | Hierarchy Clear? | Issues |
|-------------|-------------|-----------------|--------|
| Homepage | Hero section CTA | Yes | Secondary CTA competes with primary |
| Product page | Product image | Mostly | Price not prominent enough |
| Contact form | Submit button | No | Form title same size as body text |

Got: Each major page/section assessed for clear visual hierarchy. If fail: Without mockups, assess from live code using browser dev tools.

Step 2: Evaluate Typography

  • Font selection: Fonts appropriate for brand and content?
  • Font pairing: Heading and body fonts complement (max 2-3 families)?
  • Type scale: Consistent scale (e.g., 1.25 major second, 1.333 perfect fourth)?
  • Line height: Body 1.4-1.6; headings 1.1-1.3
  • Line length: Body 45-75 characters (optimal ~66)
  • Font weight: Weight variations consistent for hierarchy
  • Font size: Base ≥ 16px for body text
/* Example well-structured type scale (1.25 ratio) */
:root {
  --text-xs: 0.64rem;    /* 10.24px */
  --text-sm: 0.8rem;     /* 12.8px */
  --text-base: 1rem;     /* 16px */
  --text-lg: 1.25rem;    /* 20px */
  --text-xl: 1.563rem;   /* 25px */
  --text-2xl: 1.953rem;  /* 31.25px */
  --text-3xl: 2.441rem;  /* 39.06px */
}

Got: Typography assessed for consistency, readability, and hierarchy. If fail: With more than 3 font families, recommend consolidation.

Step 3: Review Colour Usage

  • Palette coherence: Intentional and limited (3-5 colours + neutrals)?
  • Brand alignment: Colours match brand guidelines?
  • Contrast ratios: Text meets WCAG AA (4.5:1 normal, 3:1 large)
  • Semantic colour: Colours used consistently for meaning (red=error, green=success)?
  • Colour blindness: Information conveyed by more than colour alone?
  • Dark/light mode: Both modes maintain readability and brand
## Colour Assessment
| Usage | Colour | Contrast Ratio | WCAG AA | Notes |
|-------|--------|----------------|---------|-------|
| Body text on white | #333333 | 12.6:1 | Pass | Good |
| Link text on white | #2563eb | 5.2:1 | Pass | Good |
| Muted text on light gray | #9ca3af on #f3f4f6 | 2.1:1 | FAIL | Increase contrast |
| CTA button text | #ffffff on #22c55e | 3.1:1 | FAIL for small text | Use darker green or larger text |

Got: Colour palette reviewed for coherence, accessibility, and semantic consistency. If fail: Use a contrast checker (WebAIM) to verify exact ratios.

Step 4: Assess Layout and Spacing

  • Grid system: Consistent grid (12-column, auto-layout, custom)?
  • Spacing scale: Systematic (4px/8px base, or Tailwind-like scale)?
  • Alignment: Elements aligned to the grid (no "almost aligned" items)?
  • Density: Appropriate for content type (data-heavy vs. marketing)?
  • Whitespace: Used intentionally to group and separate?
  • Consistency: Similar sections spaced identically?

Spacing audit:

## Spacing Consistency Check
| Element Pair | Expected Gap | Actual Gap | Consistent? |
|-------------|-------------|------------|-------------|
| Section title to content | 24px | 24px | Yes |
| Card to card | 16px | 16px/24px | No — inconsistent |
| Form label to input | 8px | 4px/8px/12px | No — varies |

Got: Layout uses systematic grid and spacing scale consistently. If fail: With inconsistent spacing, recommend a spacing scale (e.g., Tailwind's space-*).

Step 5: Evaluate Responsive Design

Test across key breakpoints:

BreakpointWidthRepresents
Mobile375pxiPhone SE / small phones
Mobile L428pxiPhone 14 / large phones
Tablet768pxiPad portrait
Desktop1280pxStandard laptop
Wide1536px+Desktop monitor

At each breakpoint, check:

  • Layout adaptation: Layout reflows (stack on mobile, side-by-side on desktop)?
  • Touch targets: Interactive elements ≥ 44x44px on mobile?
  • Text readability: Font size appropriate for viewport?
  • Image scaling: Images resize without distortion or overflow?
  • Navigation: Mobile nav accessible (hamburger, bottom nav)?
  • No horizontal scroll: Content does not overflow viewport horizontally
## Responsive Review
| Breakpoint | Layout | Touch Targets | Text | Images | Navigation | Issues |
|-----------|--------|---------------|------|--------|------------|--------|
| 375px | OK | OK | OK | Overflow on hero | Hamburger | Hero image clips |
| 768px | OK | OK | OK | OK | Hamburger | None |
| 1280px | OK | N/A | OK | OK | Full nav | None |
| 1536px | OK | N/A | Line length too long | OK | Full nav | Add max-width to content |

Got: Design tested at all key breakpoints with issues documented. If fail: Without responsive testing tools, review CSS media queries for coverage.

Step 6: Check Brand Consistency

  • Logo usage: Logo rendered correctly (size, spacing, clear zone)
  • Colour accuracy: Brand colours match spec (hex values, not "close enough")
  • Typography match: Fonts match brand guidelines
  • Tone/voice: UI copy matches brand personality
  • Iconography: Icons from a consistent set (style, weight, grid)
  • Photography style: Images match brand guidelines (if applicable)

Got: Brand elements verified against guidelines with deviations noted. If fail: Without brand guidelines, note this as a recommendation and assess internal consistency instead.

Step 7: Write the Design Review

## Web Design Review

### Overall Impression
[2-3 sentences: overall quality, strongest and weakest aspects]

### Visual Hierarchy: [Score/5]
[Key findings with specific references]

### Typography: [Score/5]
[Key findings with specific references]

### Colour: [Score/5]
[Key findings with specific references]

### Layout & Spacing: [Score/5]
[Key findings with specific references]

### Responsive Design: [Score/5]
[Key findings with specific references]

### Brand Consistency: [Score/5]
[Key findings with specific references]

### Priority Improvements
1. [Most impactful change — specific and actionable]
2. [Second priority]
3. [Third priority]

### Positive Notes
1. [What works well and should be preserved]

Got: Review provides specific, visual-reference feedback with prioritized improvements. If fail: If scoring feels arbitrary, use a simpler pass/concern/fail system.

Validation

  • Visual hierarchy assessed for all major pages/sections
  • Typography evaluated for readability, consistency, and scale
  • Colour contrast verified against WCAG AA minimums
  • Layout and spacing checked for grid consistency
  • Responsive design tested at 3+ breakpoints
  • Brand consistency verified against guidelines (or internal consistency assessed)
  • Feedback is specific with visual references (page, section, element)

Pitfalls

  • Subjective without reasoning: "I don't like the colour" is not actionable. Explain why (contrast, brand mismatch, accessibility).
  • Ignoring accessibility: Visual design review must include WCAG contrast checks. Beautiful designs that exclude users are not good designs.
  • Reviewing mockups only: Test responsive behaviour, hover states, and transitions — not just static layouts.
  • Prescribing solutions: Describe the problem ("text is hard to read on this background") rather than dictating a fix ("use #333").
  • Forgetting context: A banking app and a gaming site have different design standards. Review against the appropriate context.

Related Skills

  • review-ux-ui — usability, interaction patterns, accessibility
  • setup-tailwind-typescript — Tailwind CSS for design systems
  • scaffold-nextjs-app — Next.js application scaffolding

GitHub 저장소

pjt222/agent-almanac
경로: i18n/caveman-lite/skills/review-web-design
0
agentsagentskillsai-assisted-developmentclaude-codeskillsteams

연관 스킬

executing-plans

디자인

executing-plans 스킬은 검토 체크포인트가 포함된 통제된 배치로 실행할 완전한 구현 계획이 있을 때 사용합니다. 이 스킬은 계획을 불러와 비판적으로 검토한 후, 소규모 배치(기본값 3개 작업)로 작업을 실행하면서 각 배치 사이에 진행 상황을 아키텍트 검토를 위해 보고합니다. 이를 통해 내재된 품질 관리 체크포인트를 갖춘 체계적인 구현이 보장됩니다.

스킬 보기

requesting-code-review

디자인

이 스킬은 코드 변경 사항을 요구 사항에 따라 분석하기 위해 코드 리뷰어 하위 에이전트를 호출합니다. 작업 완료 후, 주요 기능 구현 후, 또는 메인 브랜치에 병합하기 전에 사용해야 합니다. 이 리뷰는 현재 구현체와 원래 계획을 비교하여 문제를 조기에 발견하는 데 도움이 됩니다.

스킬 보기

connect-mcp-server

디자인

이 스킬은 개발자들이 HTTP, stdio 또는 SSE 전송 방식을 통해 MCP 서버를 Claude Code에 연결하는 포괄적인 가이드를 제공합니다. GitHub, Notion 및 사용자 정의 API와 같은 외부 서비스를 통합하기 위한 설치, 구성, 인증 및 보안을 다룹니다. MCP 통합 설정, 외부 도구 구성 또는 Claude의 모델 컨텍스트 프로토콜 작업 시 활용하세요.

스킬 보기

web-cli-teleport

디자인

이 스킬은 작업 분석을 기반으로 개발자가 Claude Code 웹 인터페이스와 CLI 인터페이스 중 선택할 수 있도록 돕고, 두 환경 간 원활한 세션 텔레포트를 가능하게 합니다. 웹, CLI 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.

스킬 보기