MCP HubMCP Hub
Volver a habilidades

review-web-design

pjt222
Actualizado 2 days ago
5 vistas
17
2
17
Ver en GitHub
Diseñodesign

Acerca de

Esta Habilidad de Claude revisa diseños web evaluando el diseño, tipografía, color, espaciado, capacidad de respuesta y coherencia con la marca. Proporciona retroalimentación práctica sobre principios de diseño y recomendaciones de mejora. Úsala para evaluar maquetas, sitios en vivo o durante revisiones de diseño previas al desarrollo.

Instalación rápida

Claude Code

Recomendado
Principal
npx skills add pjt222/agent-almanac -a claude-code
Comando PluginAlternativo
/plugin add https://github.com/pjt222/agent-almanac
Git CloneAlternativo
git clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/review-web-design

Copia y pega este comando en Claude Code para instalar esta habilidad

Documentación

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.

BreakpointWidthRepresents
Mobile375pxiPhone SE / small phones
Mobile L428pxiPhone 14 / large phones
Tablet768pxiPad portrait
Desktop1280pxStandard laptop
Wide1536px+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, accessibility
  • setup-tailwind-typescript — Tailwind CSS for design systems
  • scaffold-nextjs-app — Next.js scaffolding

Repositorio GitHub

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

Habilidades relacionadas

executing-plans

Diseño

Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.

Ver habilidad

requesting-code-review

Diseño

Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.

Ver habilidad

connect-mcp-server

Diseño

Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.

Ver habilidad

web-cli-teleport

Diseño

Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.

Ver habilidad