Design Audit
THIS SKILL TRIGGERS EVERYTHING
When user asks to "check my site" or "recommend improvements", this skill should:
- •Run comprehensive multi-category analysis
- •Spawn all 5 validation agents
- •Check SEO, CRO, Psychology, Accessibility
- •Provide prioritized recommendations
- •Offer to fix via other skills
Comprehensive Analysis Categories
| Category | What to Check | Skills/Agents Used |
|---|---|---|
| CRO | Value prop, CTAs, social proof, friction | design-audit + copy-analyzer |
| Copy | Headlines, CTAs, microcopy, reading level | copy-optimizer + copy-analyzer |
| Psychology | Framework fit, biases, triggers, trust | psychology references |
| Visual Design | Hierarchy, consistency, spacing, shadows | design-validator |
| Accessibility | WCAG, focus, contrast, touch targets | accessibility-checker |
| Mobile | Thumb zone, touch targets, readability | mobile-validator |
| Dark Mode | Anti-patterns, contrast, FOUC | dark-mode-checker |
| SEO | Meta, headings, structure, alt text | SEO references |
| Performance | Core Web Vitals, React patterns | react-best-practices |
Load ALL Relevant References
# 6-Layer Audit READ: ../../references/audit/first-impression.md READ: ../../references/audit/copy-clarity.md READ: ../../references/audit/psychological-triggers.md READ: ../../references/audit/cta-audit.md READ: ../../references/audit/mobile-audit.md READ: ../../references/audit/seo-audit.md # Psychology (for root cause analysis) READ: ../../references/psychology/visual-hierarchy.md READ: ../../references/psychology/trust-signals.md READ: ../../references/psychology/cognitive-biases.md # Design System (for visual analysis) READ: ../../references/design-system/spacing-scale.md READ: ../../references/design-system/shadows-elevation.md READ: ../../references/design-system/component-states.md # SEO (often forgotten!) READ: ../../references/seo/heading-hierarchy.md READ: ../../references/seo/meta-titles.md READ: ../../references/seo/meta-descriptions.md # Performance READ: ../../references/performance/core-web-vitals.md
Conversion Benchmarks (Know the Context)
Before auditing, understand what "good" looks like:
| Industry | Median CVR | Good | Excellent | Source |
|---|---|---|---|---|
| SaaS | 3.8% | 5-7% | 10%+ | Unbounce 2024 |
| Finance | 8.4% | 10-12% | 15%+ | Unbounce 2024 |
| E-commerce | 2.5-3% | 4-5% | 7%+ | Industry average |
| Events | 12.3% | 15%+ | 20%+ | Unbounce 2024 |
| Overall | 6.6% | 10% | 15%+ | Unbounce (41k pages) |
Traffic source matters: Email traffic converts at 19.3% vs paid search baseline
The 6-Layer Framework
Layer 1: First Impression (0-5 seconds)
Reference: ../../references/audit/first-impression.md
| Check | Pass Criteria | Fail Example | Impact |
|---|---|---|---|
| Value prop clarity | Visitor can explain what you do in 5 sec | Jargon-heavy headline | -30% engagement |
| Visual hierarchy | ONE clear focal point exists | Everything competing | Confusion, bounce |
| Trust signals | Logos/testimonials above fold | None visible | -26% trust (social proof data) |
| CTA visibility | Primary action obvious without scroll | Hidden or blends in | -304% vs above-fold |
Layer 2: Copy Clarity
Reference: ../../references/audit/copy-clarity.md
| Check | Pass Criteria | Fail Example | Impact |
|---|---|---|---|
| Headline benefit | Leads with user outcome | "AI-powered platform" | -17% revenue |
| Specificity | Includes numbers/timeframe | "Grow faster" | -36% clicks (no numbers) |
| Company vs You | Focuses on "you", not "we" | "We help businesses..." | -12% personalization |
| Feature→Benefit | Benefits, not features | "Built with React" | Users don't care |
Layer 3: Psychological Triggers
Reference: ../../references/audit/psychological-triggers.md
| Trigger | Implementation | Missing Impact |
|---|---|---|
| Social proof | Numbers, logos, testimonials | -270% potential uplift (Spiegel) |
| Urgency/scarcity | Time limits, limited spots | -332% if missing appropriately |
| Authority | Credentials, press, certifications | Reduced trust |
| Risk reversal | Free trial, guarantee, easy cancel | Higher friction |
Testimonial optimization:
- •3-5 on homepage, 100+ in library = 37% higher conversions
- •Show 4.2-4.5 stars (not 5.0) — perfect ratings seem fake
- •Video testimonials: +80% conversion vs text
Layer 4: CTA Effectiveness
Reference: ../../references/audit/cta-audit.md
| Check | Optimal | Suboptimal | Data |
|---|---|---|---|
| Copy | "Get my free analysis" | "Submit" | 202% better personalized |
| Placement | Above fold + decision points | Only at bottom | 304% better above fold |
| Count | Single primary per viewport | 5+ competing | 13.5% vs 10.5% CVR |
| Color contrast | Stands out from page | Blends in | 21% from color change |
| Size | Centered, prominent | Left-aligned, small | 682% more clicks centered |
Layer 5: Mobile Experience
Reference: ../../references/audit/mobile-audit.md
| Check | Requirement | Fail | Data |
|---|---|---|---|
| Touch targets | ≥44×44px (Apple) or 48×48dp (Material) | p-2 buttons (~32px) | 25%+ tap errors |
| Thumb zone | Primary CTA in bottom third | CTA at top | Hard reach for 70% |
| Text size | 16px minimum for body | 14px or smaller | Readability issues |
| Form inputs | Correct input types (email, tel) | All type="text" | No specialized keyboard |
Reality check: 82.9% of visitors are mobile, but convert 8% less than desktop. Close that gap.
Layer 6: Technical SEO
Reference: ../../references/audit/seo-audit.md
| Check | Requirement | Impact |
|---|---|---|
| Meta title | 50-60 chars, keyword + benefit | Search ranking |
| Meta description | 150-160 chars, includes CTA | Click-through rate |
| Heading hierarchy | Single H1, logical H2-H6 | Accessibility + SEO |
| Image alt text | Descriptive, not keyword stuffed | Accessibility |
| Page speed | LCP < 2.5s | -4.42% CVR per second delay |
Confidence Scoring
Only report findings you can verify. Rate every issue:
| Confidence | Criteria | Action |
|---|---|---|
| 90-100% | Can see exact problem in code/screenshot | ✅ Report as finding |
| 80-89% | Pattern strongly suggests issue | ✅ Report as finding |
| 70-79% | Possible issue, could be intentional | ⚠️ Note as observation |
| <70% | Uncertain, speculation | ❌ Do not report |
Example confidence assessment:
- •"Button is 32px tall" = 95% (measurable)
- •"Headline seems vague" = 75% (subjective)
- •"Users might not understand" = 50% (speculation)
Root Cause Analysis
After completing layers, ask:
1. Is This a Symptom or the Cause?
- •Multiple small buttons → Cause: No design system with spacing standards
- •Inconsistent colors → Cause: No token architecture
- •Weak copy throughout → Cause: No brand voice guidelines
2. What Pattern Repeats?
| Repeated Issue | Root Cause | Fix |
|---|---|---|
| Multiple contrast failures | No color system | Implement design tokens |
| Multiple CTA issues | No copy framework | Define copy guidelines |
| Multiple mobile issues | Desktop-first development | Adopt mobile-first |
| Inconsistent spacing | No spacing scale | Define 4px/8px system |
3. Why Did This Happen?
- •Template without customization → Recommend brand differentiation
- •No design review process → Recommend design audit checklist
- •Solo developer → Recommend design system adoption
Severity Classification
| Severity | Criteria | Conversion Impact | Examples |
|---|---|---|---|
| 🔴 Critical | Directly blocks conversion or fails accessibility | -20% to -50% | No value prop, invisible CTA, broken mobile, WCAG fails |
| 🟡 Important | Reduces effectiveness, missing optimization | -5% to -20% | Weak copy, no social proof, poor hierarchy |
| 🟢 Minor | Would help if improved | +1% to +5% | Better urgency, polish, micro-optimizations |
Report Format
## Audit Report: [Page Name] **Conversion Potential**: [Current estimate] → [Post-fix estimate] **Priority Score**: X critical, Y important, Z minor ### Executive Summary [2-3 sentences: biggest problems and biggest opportunities] ### Layer-by-Layer Findings #### Layer 1: First Impression - 🔴 [Finding] (95% confidence) - Location: [file:line or element] - Impact: [conversion impact] - Fix: [specific action] [Continue for all 6 layers...] ### Root Cause Analysis [Pattern identified and systemic fix] --- **CHECKPOINT**: What would you like me to fix? 1. Fix all (batches of 3) 2. Fix critical only 3. Fix specific issue 4. Export report
Anti-patterns (When Auditing)
| Mistake | Why It Fails | Instead |
|---|---|---|
| "Improve the hero" | Vague, not actionable | "Change headline from [X] to [Y] because [reason]" |
| Skip layers | Miss systematic issues | Complete ALL 6 layers |
| No psychology explanation | User can't learn | "Social proof missing — users need to see others succeeded (bandwagon effect)" |
| Fix without asking | May have context you don't | ALWAYS checkpoint |
| Audit desktop only | 82.9% traffic is mobile | Test at 375px width |
| Report low-confidence | Wastes user time | Only report ≥80% confidence |
| Generic recommendations | "Add whitespace" | "Add 48px spacing between sections X and Y" |
Reference Loading for Fixes
| Issue Type | MANDATORY Load |
|---|---|
| Copy issues | transformations/hero-transformation.md, transformations/cta-transformation.md |
| Component issues | components/cross-reference.md, patterns/[relevant].md |
| Theme/Color issues | theming/dark-mode-antipatterns.md |
| Mobile issues | mobile/thumb-zone.md, mobile/touch-targets.md |
| Performance issues | performance/core-web-vitals.md |
After Audit: Fix or Redesign
After presenting findings, offer clear next steps:
--- **NEXT STEPS:** 1. **Quick Fixes** - Fix critical issues one by one (I'll preserve current design) 2. **Improve Mode** - Apply all fixes while keeping current direction 3. **Redesign Mode** - If issues are systemic, consider fresh redesign → I'll ask about desired personality and build new Which would you like?
When to Suggest Redesign vs Fix
| Situation | Recommendation |
|---|---|
| 1-3 critical issues, good foundation | Fix mode |
| Multiple systemic issues (no design system, inconsistent) | Suggest redesign |
| User explicitly unhappy with current look | Offer redesign |
| Current design is fine but outdated | Improve mode |
MANDATORY PIPELINE (DO NOT SKIP)
This skill is part of a multi-step pipeline. You MUST follow these steps:
PHASE 1: Pre-Audit (MANDATORY)
Before auditing, you MUST load ALL audit references:
READ: ../../references/audit/first-impression.md READ: ../../references/audit/copy-clarity.md READ: ../../references/audit/psychological-triggers.md READ: ../../references/audit/cta-audit.md READ: ../../references/audit/mobile-audit.md READ: ../../references/audit/seo-audit.md
PHASE 2: Multi-Agent Validation (MANDATORY)
You MUST spawn ALL 5 validation agents in parallel:
"Let me launch all 5 Forgex validation agents in parallel..."
In a single message, launch these Task tool calls:
- •
design-validator
- •Prompt: "Validate visual hierarchy, consistency, responsiveness, and polish for [target]. Score 0-100 with specific issues."
- •
accessibility-checker
- •Prompt: "Check WCAG 2.1 AA compliance for [target]. Check Perceivable, Operable, Understandable, Robust. Score 0-100."
- •
mobile-validator
- •Prompt: "Validate touch targets, thumb zones, text readability, form usability for [target]. Score 0-100."
- •
dark-mode-checker
- •Prompt: "Check dark mode implementation for [target]. Look for pure black, shadow issues, saturation, FOUC, form elements. Score 0-100."
- •
copy-analyzer
- •Prompt: "Analyze headlines, CTAs, value propositions, psychology triggers for [target]. Score 0-100."
PHASE 3: 6-Layer Framework Overlay
After agents complete, apply the 6-layer framework:
- •First Impression (0-5 seconds)
- •Copy Clarity
- •Psychological Triggers
- •CTA Effectiveness
- •Mobile Experience
- •Technical SEO
Cross-reference agent findings with framework checklist.
PHASE 4: Aggregate & Report
- •Collect all agent scores
- •Filter findings to ≥80% confidence
- •Classify severity (Critical/Important/Minor)
- •Identify root causes (patterns that repeat)
- •Generate unified report (format above)
PHASE 5: Completion
Present findings with CHECKPOINT:
--- **CHECKPOINT**: What would you like me to fix? 1. Fix all (batches of 3) 2. Fix critical only 3. Fix specific issue 4. Export report
FIX MODE PIPELINE
When fixing issues:
- •
For copy issues → Invoke
copy-optimizerskill- •Load psychology frameworks
- •Apply headline/CTA transformations
- •Re-run copy-analyzer to verify
- •
For component issues → Invoke
component-builderskill- •Load relevant pattern references
- •Rebuild component with fixes
- •Re-run design-validator to verify
- •
For theme/color issues → Invoke
theme-systemskill- •Load dark-mode-antipatterns
- •Fix contrast, color issues
- •Re-run dark-mode-checker to verify
- •
For mobile issues → Load and apply:
codeREAD: ../../references/mobile/thumb-zone.md READ: ../../references/mobile/touch-targets.md
- •Re-run mobile-validator to verify
After Fixes
- •Re-run affected validation agents
- •Confirm all scores ≥80
- •Only then mark complete
REDESIGN MODE
When issues are systemic (3+ root causes):
- •Suggest redesign option
- •If accepted, invoke
component-builderwith redesign mode - •Full pipeline runs for new design