review-web-design
정보
이 스킬은 웹 디자인의 레이아웃, 타이포그래피, 색상, 간격, 반응형 디자인, 브랜드 일관성을 분석합니다. 개발 전 목업 검토, 구현된 사이트 평가, 다양한 브레이크포인트에서의 테스트에 유용합니다. URL, 목업, 스크린샷을 입력받을 수 있으며, 브랜드 가이드라인을 참조하여 포괄적인 피드백을 제공합니다.
빠른 설치
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
Eval web design → visual quality, consistency, cross-device.
Use When
- Mockup|prototype pre-dev review
- Implemented site|app design quality
- Design review session feedback
- Brand consistency multi-page
- Responsive behavior across breakpoints
In
- Required: Design (URL|mockup|screenshot|src)
- Optional: Brand guidelines|design system
- Optional: Target audience
- Optional: Reference|competitor designs
- Optional: Concerns
Do
Step 1: Visual Hierarchy
Guides eye → importance.
- Focal point: Obvious entry per page?
- Heading hierarchy: H1→H2→H3 logical?
- Size contrast: Important > supporting?
- Color contrast: CTAs prominent?
- Whitespace: Separates groups?
- Reading flow: F|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 |
→ Each page assessed.
If err: no mockups → live code via dev tools.
Step 2: Typography
- Font selection: Right for brand+content?
- Pairing: Heading+body complement (max 2-3 families)?
- Scale: Consistent (1.25 maj 2nd, 1.333 4th)?
- Line height: Body 1.4-1.6, headings 1.1-1.3
- Line length: 45-75 chars (~66 optimal)
- Weight: Used for hierarchy
- Size: ≥16px 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 */
}
→ Typo consistent, readable, hierarchical.
If err: >3 families → consolidate.
Step 3: Color
- Palette: Limited (3-5 + neutrals)?
- Brand: Matches guidelines?
- Contrast: WCAG AA (4.5:1 normal, 3:1 large)
- Semantic: Consistent (red=err, green=ok)?
- Color blind: Not sole means?
- Dark/light: Both readable + brand consistent?
## 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 |
→ Palette coherent + accessible + semantic.
If err: contrast checker tool (WebAIM).
Step 4: Layout + Spacing
- Grid: Consistent (12-col, auto, custom)?
- Spacing scale: Systematic (4|8px base, Tailwind)?
- Alignment: To grid (no "almost")?
- Density: Right for content?
- Whitespace: Intentional?
- Consistency: Similar = same spacing?
## 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 |
→ Systematic grid + spacing.
If err: inconsistent → adopt scale (Tailwind space-*).
Step 5: Responsive
| 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:
- Layout adapt: Reflows (stack mobile, side desktop)?
- Touch targets: ≥44x44 mobile?
- Text: Right size?
- Images: Scale w/o distortion?
- Nav: Mobile accessible?
- No h-scroll
## 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 |
→ All breakpoints tested + documented.
If err: no tools → review CSS media queries.
Step 6: Brand Consistency
- Logo: Right size, spacing, clear zone
- Color: Matches spec (hex, not "close")
- Typo: Matches guidelines
- Tone: UI copy matches personality
- Icons: Consistent set
- Photo: Matches brand
→ Brand verified vs guidelines.
If err: no guidelines → note + assess internal consistency.
Step 7: Write 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]
→ Specific, visual-reference feedback + prioritized improvements.
If err: scoring arbitrary → pass|concern|fail.
Check
- Visual hierarchy all major pages
- Typo readable + consistent + scaled
- Color contrast vs WCAG AA
- Layout + spacing grid consistent
- Responsive 3+ breakpoints
- Brand vs guidelines (or internal)
- Specific feedback w/ visual refs
Traps
- Subjective no reason: "Don't like color" → not actionable. Explain why.
- Ignore access: Must include WCAG contrast. Beautiful + excludes ≠ good.
- Mockups only: Test responsive, hover, transitions — not static.
- Prescribe: Describe problem, not specific fix.
- No context: Banking ≠ gaming. Review against context.
→
review-ux-ui— usability + interaction + accesssetup-tailwind-typescript— Tailwind CSS implscaffold-nextjs-app— Next.js scaffold
GitHub 저장소
연관 스킬
evaluating-llms-harness
테스팅이 Claude Skill은 MMLU, GSM8K를 포함한 60개 이상의 표준화된 학술 과제에서 LLM 성능을 벤치마크하기 위해 lm-evaluation-harness를 실행합니다. 개발자들이 모델 품질을 비교하고, 학습 진행 상황을 추적하거나 학술 결과를 보고할 수 있도록 설계되었습니다. 이 도구는 HuggingFace와 vLLM 모델을 포함한 다양한 백엔드를 지원합니다.
cloudflare-cron-triggers
테스팅이 스킬은 cron 표현식을 사용하여 Worker를 스케줄링하기 위한 Cloudflare Cron Triggers 구현에 관한 포괄적인 지식을 제공합니다. 주기적 작업, 유지보수 작업, 자동화된 워크플로우 설정 방법을 다루며, 잘못된 cron 표현식이나 시간대 문제 같은 일반적인 이슈들을 해결하는 방법을 포함합니다. 개발자들은 이를 통해 스케줄된 핸들러 구성, cron 트리거 테스트, Workflows 및 Green Compute와의 연동 작업을 수행할 수 있습니다.
webapp-testing
테스팅이 Claude Skill은 Python 스크립트를 통해 로컬 웹 애플리케이션을 테스트하기 위한 Playwright 기반 툴킷을 제공합니다. 프론트엔드 검증, UI 디버깅, 스크린샷 캡처, 로그 확인 기능을 지원하며 서버 라이프사이클을 관리합니다. 브라우저 자동화 작업에 사용하되 컨텍스트 오염을 방지하기 위해 소스 코드를 읽지 않고 스크립트를 직접 실행하세요.
finishing-a-development-branch
테스팅이 스킬은 테스트 통과를 확인한 후 체계적인 통합 옵션을 제시하여 개발자가 완성된 작업을 마무리하도록 돕습니다. 구현이 완료된 후 머지, PR 생성, 브랜치 정리와 같은 워크플로우를 안내합니다. 코드가 준비되고 테스트가 완료되었을 때 개발 프로세스를 체계적으로 마무리하기 위해 사용하세요.
