Web Design Reviewer
Use this skill for visual QA and source-level fixes after a page is already running. This is not the right skill for functional automation or regression suites.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
Activation Conditions
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- Reviewing a live page for layout or spacing defects
- Checking responsive behavior at a few critical widths
- Comparing a page to a design system or visual target
- Tracing a visible issue back to CSS, Tailwind classes, or component structure
Recommended Workflow
- Open the page with a browser-capable MCP client such as Playwright MCP.
- Capture the current state before editing.
- Test desktop and mobile widths.
- Fix the source code, then re-check the same viewports.
Playwright MCP Mapping
These tool names are current in the Playwright MCP server used by Codex:
browser_navigate to open the page
browser_snapshot to inspect accessible structure
browser_take_screenshot for before and after captures
browser_resize for responsive review
browser_console_messages and browser_network_requests to catch front-end breakage
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/web-design-reviewer and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Playwright MCP, Chrome DevTools MCP (optional)
- Fallback prompt: "Use the Web Design Reviewer skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use Playwright CLI, browser devtools, screenshots, and manual responsive checks when MCP browser tools are unavailable.
- Capture console or network issues with the browser or terminal before proposing visual fixes.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Starting from a generic template without adapting it: The output may look polished but still miss the real audience or medium.
- Ignoring final render or export review: Layout bugs often appear only after the asset is opened in its destination tool.
- Fixing content and presentation in one pass: It becomes hard to tell whether a problem is structural or visual.
Verification Protocol
Before claiming "skill applied successfully":
- Pass/fail: The Web Design Reviewer guidance is tied to a concrete route, component, screen, or design artifact.
- Pass/fail: Component states cover loading, empty, error, success, and responsive breakpoints where applicable.
- Pass/fail: Accessibility, visual hierarchy, and interaction behavior are reviewed against the shared component rubric.
- Pressure-test scenario: Review the component on a narrow mobile viewport, keyboard-only path, and slow-loading state.
- Success metric: Zero generic UI approval; every approval cites rendered behavior or source evidence.
Review Checklist
References & Resources
Documentation
- Visual Checklist - High-signal items for layout, contrast, spacing, and responsive review
- Framework Fixes - Typical fix locations for CSS, Tailwind, CSS modules, and component styles
Scripts
- CSS Risk Audit - Scan CSS and front-end source for risky fixed widths, viewport traps, and overflow patterns
Related Skills
- frontend-design: Use it when the workflow also needs UI composition and front-end design direction.
- stitch-design: Use it when the workflow also needs turning interface designs into implementation-ready assets.
- canvas-design: Use it when the workflow also needs visual composition and presentation-ready diagram work.
1---
2name: web-design-reviewer
3version: "2.0"
4last_updated: 2026-09-08
5tags: [web, design, reviewer, frontend, ui]
6description: "Visual inspection of live websites to find and fix design issues. Use when reviewing UI layout/design, checking responsive design visually, detecting visual inconsistencies, or diagnosing CSS/accessibility problems at the source code level. Not for automated E2E testing."
7metadata:
8 source: https://skillmd.com/skills/practicalswan/web-design-reviewer
9---
10
11# Web Design Reviewer
12
13Use this skill for visual QA and source-level fixes after a page is already running. This is not the right skill for functional automation or regression suites.
14
15- Leverage native parallel subagent dispatch and 200k+ context windows where available.
16
17
18## Activation Conditions
19
20Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
21
22- Reviewing a live page for layout or spacing defects
23- Checking responsive behavior at a few critical widths
24- Comparing a page to a design system or visual target
25- Tracing a visible issue back to CSS, Tailwind classes, or component structure
26
27## Recommended Workflow
28
291. Open the page with a browser-capable MCP client such as Playwright MCP.
302. Capture the current state before editing.
313. Test desktop and mobile widths.
324. Fix the source code, then re-check the same viewports.
33
34## Playwright MCP Mapping
35
36These tool names are current in the Playwright MCP server used by Codex:
37
38- `browser_navigate` to open the page
39- `browser_snapshot` to inspect accessible structure
40- `browser_take_screenshot` for before and after captures
41- `browser_resize` for responsive review
42- `browser_console_messages` and `browser_network_requests` to catch front-end breakage
43
44<!-- MCP:START -->
45
46<!-- PORTABILITY:START -->
47## Cross-Client Portability
48
49This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
50
51- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
52 workflow in project instructions when folder discovery is unavailable.
53- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
54- Codex: install or sync the folder into
55 `$CODEX_HOME/skills/web-design-reviewer` and restart Codex after major changes.
56
57<!-- PORTABILITY:END -->
58
59## MCP Availability And Fallback
60
61Preferred MCP Server: Playwright MCP, Chrome DevTools MCP (optional)
62
63- Fallback prompt: "Use the Web Design Reviewer skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
64- Use Playwright CLI, browser devtools, screenshots, and manual responsive checks when MCP browser tools are unavailable.
65- Capture console or network issues with the browser or terminal before proposing visual fixes.
66- Do not claim an MCP operation was used when the active host does not expose it.
67
68<!-- MCP:END -->
69
70## Anti-Patterns
71
72- Starting from a generic template without adapting it: The output may look polished but still miss the real audience or medium.
73- Ignoring final render or export review: Layout bugs often appear only after the asset is opened in its destination tool.
74- Fixing content and presentation in one pass: It becomes hard to tell whether a problem is structural or visual.
75
76## Verification Protocol
77
78Before claiming "skill applied successfully":
79
801. Pass/fail: The Web Design Reviewer guidance is tied to a concrete route, component, screen, or design artifact.
812. Pass/fail: Component states cover loading, empty, error, success, and responsive breakpoints where applicable.
823. Pass/fail: Accessibility, visual hierarchy, and interaction behavior are reviewed against the shared component rubric.
834. Pressure-test scenario: Review the component on a narrow mobile viewport, keyboard-only path, and slow-loading state.
845. Success metric: Zero generic UI approval; every approval cites rendered behavior or source evidence.
85
86## Review Checklist
87
88- [ ] No overflow or clipped content at target widths
89- [ ] Interactive controls remain visible and reachable
90- [ ] Text contrast and focus states are acceptable
91- [ ] Repeated components use consistent spacing, typography, and color
92- [ ] Fixes were verified visually after the code change
93
94## References & Resources
95
96### Documentation
97- [Visual Checklist](./references/visual-checklist.md) - High-signal items for layout, contrast, spacing, and responsive review
98- [Framework Fixes](./references/framework-fixes.md) - Typical fix locations for CSS, Tailwind, CSS modules, and component styles
99
100### Scripts
101- [CSS Risk Audit](./scripts/css-risk-audit.py) - Scan CSS and front-end source for risky fixed widths, viewport traps, and overflow patterns
102
103## Related Skills
104
105- [frontend-design](../frontend-design/SKILL.md): Use it when the workflow also needs UI composition and front-end design direction.
106- [stitch-design](../stitch-design/SKILL.md): Use it when the workflow also needs turning interface designs into implementation-ready assets.
107- [canvas-design](../canvas-design/SKILL.md): Use it when the workflow also needs visual composition and presentation-ready diagram work.