← ClaudeAtlas

visual-auditlisted

Use when performing structured visual design critique of an interface. Covers hierarchy, contrast, spacing, typography, color, and component consistency with actionable fix recommendations. Do not use for design token architecture (use design-system-architecture) or animation specifications (use motion-design).
dtsong/agentic-council · ★ 0 · Web & Frontend · score 78
Install: claude install-skill dtsong/agentic-council
# Visual Audit ## Purpose Perform a structured visual design critique of an interface, producing specific actionable feedback on hierarchy, contrast, spacing, typography, color, and overall coherence. ## Scope Constraints Reads screenshots, mockups, or live implementation for visual analysis. Does not modify source code or design files. Does not generate new designs or components. ## Inputs - Screenshots, mockups, or live implementation of the interface - Design system or style guide (if it exists) - Target context (marketing page, app dashboard, settings screen, etc.) - Accessibility requirements (WCAG AA, AAA, or custom) ## Input Sanitization No user-provided values are used in commands or file paths. All inputs are treated as read-only analysis targets. ## Procedure ### Progress Checklist - [ ] Step 1: Squint test - [ ] Step 2: Hierarchy audit - [ ] Step 3: Typography audit - [ ] Step 4: Color and contrast audit - [ ] Step 5: Spacing and alignment audit - [ ] Step 6: Component consistency audit ### Step 1: Squint Test View the interface at arm's length (or blur it mentally). Identify: - What's the loudest element? Is it the right one? - Can you identify the primary action within 3 seconds? - Is there a clear visual reading order? - Are there any areas of visual "soup" (too much competing for attention)? ### Step 2: Hierarchy Audit Check the information hierarchy: - **Heading levels:** Are there clear H1 → H2 → H3 distinctions via size and weight? - **Primary