About visual-audit
visual-audit is a design review skill for evaluating designs in a conversation. It emphasizes specific observations over subjective reactions and structures feedback around intent, strengths, problems, and one high-impact change.
Key features
- 0110-second design review
- 02Identify the primary visual element
- 03Separate observations from reactions
- 04Structured diagnosis and change
Use cases
- 01Quickly review a design shared in a conversation
- 02Audit a design described in text
- 03Identify hierarchy or spacing issues
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/visual-auditin Claude Code to confirm it loaded.
Details
From the project READMEVisual Audit
Look at any design and name what's working and what's not. Fast.
How to use
/visual-auditApply rapid perception constraints to evaluate any design in this conversation./visual-audit <url or screenshot>Run a 10-second audit on the described or provided design.
Constraints
The 10-Second Rule
- MUST identify the primary visual element within 3 seconds of looking
- MUST name 3 specific observations (not feelings) within 10 seconds
- MUST distinguish between observations ("the CTA is the same weight as the nav") and reactions ("it looks cluttered")
- NEVER use vague words: clean, nice, modern, sleek, beautiful, stunning, minimal, bold
- SHOULD replace every vague word with a specific observation about hierarchy, weight, rhythm, density, or contrast
What to Observe
- Where does the eye go first? Is that intentional?
- How many type sizes are visible? Is there a clear scale?
- What's the spacing system? Is it consistent?
- How many colors are in use? What roles do they play?
- What's the density? Does it match the use case?
- What states are visible? What states are missing?
Output Structure
- First: name the design's apparent intent (what it's trying to do)
- Second: name what's working (specific decisions, not aesthetics)
- Third: name what's not working (specific decisions, with reasoning)
- Fourth: one change that would have the most impact
Anti-Patterns
- Listing only positive observations to be polite
- Jumping to solutions before diagnosing the problem
- Evaluating aesthetics instead of decisions
- Giving feedback about style preferences rather than quality signals
Comments
Markdown supported