review-web-design
정보
이 Claude Skill은 레이아웃, 타이포그래피, 색상, 간격, 반응형 디자인, 브랜드 일관성을 평가하여 웹 디자인을 검토합니다. 디자인 원칙에 기반한 실행 가능한 피드백과 개선 권장 사항을 제공합니다. 목업, 라이브 사이트 평가 또는 개발 전 디자인 리뷰 과정에서 활용하세요.
빠른 설치
Claude Code
추천npx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/review-web-designClaude Code에서 이 명령을 복사하여 붙여넣어 스킬을 설치하세요
문서
Review Web Design
Judge web design for visual quality, consistency, effectiveness across devices.
When Use
- Review mockup or prototype before dev
- Judge implemented site for design quality
- Give feedback in design review
- Check brand consistency across pages
- Test responsive behaviour at breakpoints
Inputs
- Required: Design (URL, mockup, screenshots, source)
- Optional: Brand guidelines or design system docs
- Optional: Target audience description
- Optional: Reference designs or competitors
- Optional: Areas of concern
Steps
Step 1: Assess Visual Hierarchy
Hierarchy guides eye through content by importance.
- Focal point: Obvious entry point per page?
- Heading hierarchy: H1 → H2 → H3 logical?
- Size contrast: Important elements bigger?
- Colour contrast: CTAs prominent?
- Whitespace: Spacing separates groups?
- Reading flow: 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 page assessed for hierarchy.
If fail: No mockups? Assess from live code via dev tools.
Step 2: Evaluate Typography
- Font selection: Right for brand, content?
- Font pairing: Heading + body fit (max 2-3 families)?
- Type scale: Consistent (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 chars (~66 best)
- Font weight: Used consistent for hierarchy
- Font size: Base ≥ 16px for body
/* 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, hierarchy.
If fail: More than 3 font families? Recommend consolidation.
Step 3: Review Colour Usage
- Palette coherence: Intentional, limited (3-5 + neutrals)?
- Brand alignment: Match guidelines?
- Contrast ratios: WCAG AA (4.5:1 normal, 3:1 large)
- Semantic colour: Consistent meaning (red=err, green=ok)?
- Colour blindness: Info conveyed by more than colour?
- Dark/light mode: Both modes readable, on-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: Palette reviewed for coherence, accessibility, semantic consistency.
If fail: Use contrast checker (WebAIM) for exact ratios.
Step 4: Assess Layout and Spacing
- Grid system: Consistent grid (12-col, auto, custom)?
- Spacing scale: Systematic (4px/8px base, Tailwind-like)?
- Alignment: Elements on grid (no "almost aligned")?
- Density: Right for content (data-heavy vs marketing)?
- Whitespace: Used to group, separate?
- Consistency: Similar sections spaced same?
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, spacing scale.
If fail: Spacing inconsistent? Recommend spacing scale (Tailwind space-*).
Step 5: Evaluate Responsive Design
Test at key breakpoints.
| Breakpoint | Width | Represents |
|---|---|---|
| Mobile | 375px | iPhone SE / small phones |
| Mobile L | 428px | iPhone 14 / large phones |
| Tablet | 768px | iPad portrait |
| Desktop | 1280px | Standard laptop |
| Wide | 1536px+ | Desktop monitor |
Per breakpoint check.
- Layout adaptation: Reflow right (stack mobile, side-by-side desktop)?
- Touch targets: ≥ 44x44px on mobile?
- Text readability: Font size right for viewport?
- Image scaling: Resize without distortion or overflow?
- Navigation: Mobile nav accessible (hamburger, bottom)?
- No horizontal scroll: Content does not overflow horizontal
## 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, issues documented.
If fail: No responsive tools? Review CSS media queries for coverage.
Step 6: Check Brand Consistency
- Logo usage: Right size, spacing, clear zone
- Colour accuracy: Brand colors match spec (hex values, not "close")
- Typography match: Fonts match brand
- Tone/voice: UI copy matches brand personality
- Iconography: Consistent set (style, weight, grid)
- Photography style: Match brand if applicable
Got: Brand elements verified vs guidelines, deviations noted.
If fail: No brand guidelines? Note as recommendation, assess internal consistency.
Step 7: Write 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 gives specific, visual-reference feedback with prioritized improvements.
If fail: Scoring feels arbitrary? Use simpler pass/concern/fail.
Checks
- Visual hierarchy assessed for all major pages
- Typography evaluated for readability, consistency, scale
- Colour contrast verified vs WCAG AA min
- Layout and spacing checked for grid consistency
- Responsive design tested at 3+ breakpoints
- Brand consistency verified vs guidelines (or internal consistency)
- Feedback specific with visual refs (page, section, element)
Pitfalls
- Subjective without reasoning: "I don't like the colour" not actionable. Explain why (contrast, brand mismatch, accessibility).
- Ignore accessibility: Visual review must include WCAG contrast. Beautiful designs that exclude users not good.
- Review mockups only: Test responsive, hover states, transitions — not just static layouts.
- Prescribe solutions: Describe problem ("text hard to read") not dictate fix ("use #333").
- Forget context: Banking app and gaming site have different standards. Review against right context.
See Also
review-ux-ui— usability, interaction, accessibilitysetup-tailwind-typescript— Tailwind CSS for design systemsscaffold-nextjs-app— Next.js scaffolding
GitHub 저장소
연관 스킬
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 또는 모바일 환경 전환 시 세션 상태와 컨텍스트를 관리하여 워크플로를 최적화합니다. 다양한 단계에서 서로 다른 도구가 필요한 복잡한 프로젝트에 사용하세요.
