Design Audit Skill
Evaluate interfaces against proven UX principles. Based on Making UX Decisions by Tommy Geoco.
When to Use This Skill
- Making UI/UX design decisions under time pressure
- Evaluating design trade-offs with business context
- Choosing appropriate UI patterns for specific problems
- Reviewing designs for completeness and quality
- Structuring design thinking for new interfaces
Core Philosophy
Speed β Recklessness. Designing quickly is not automatically reckless. Recklessly designing quickly is reckless. The difference is intentionality.
The 3 Pillars of Warp-Speed Decisioning
- Scaffolding β Rules you use to automate recurring decisions
- Decisioning β Process you use for making new decisions
- Crafting β Checklists you use for executing decisions
Quick Reference Structure
Foundational Frameworks
references/00-core-framework.mdβ 3 pillars, decisioning workflow, macro betsreferences/01-anchors.mdβ 7 foundational mindsets for design resiliencereferences/02-information-scaffold.mdβ Psychology, economics, accessibility, defaults
Checklists (Execution)
references/10-checklist-new-interfaces.mdβ 6-step process for designing new interfacesreferences/11-checklist-fidelity.mdβ Component states, interactions, scalability, feedbackreferences/12-checklist-visual-style.mdβ Spacing, color, elevation, typography, motionreferences/13-checklist-innovation.mdβ 5 levels of originality spectrum
Patterns (Reusable Solutions)
references/20-patterns-chunking.mdβ Cards, tabs, accordions, pagination, carouselsreferences/21-patterns-progressive-disclosure.mdβ Tooltips, popovers, drawers, modalsreferences/22-patterns-cognitive-load.mdβ Steppers, wizards, minimalist nav, simplified formsreferences/23-patterns-visual-hierarchy.mdβ Typography, color, whitespace, size, proximityreferences/24-patterns-social-proof.mdβ Testimonials, UGC, badges, social integrationreferences/25-patterns-feedback.mdβ Progress bars, notifications, validation, contextual helpreferences/26-patterns-error-handling.mdβ Form validation, undo/redo, dialogs, autosavereferences/27-patterns-accessibility.mdβ Keyboard nav, ARIA, alt text, contrast, zoomreferences/28-patterns-personalization.mdβ Dashboards, adaptive content, preferences, l10nreferences/29-patterns-onboarding.mdβ Tours, contextual tips, tutorials, checklistsreferences/30-patterns-information.mdβ Breadcrumbs, sitemaps, tagging, faceted searchreferences/31-patterns-navigation.mdβ Priority nav, off-canvas, sticky, bottom nav
Usage Instructions
For Design Decisions
- Read
00-core-framework.mdfor the decisioning workflow - Identify if this is a recurring decision (use scaffold) or new decision (use process)
- Apply the 3-step weighing: institutional knowledge β user familiarity β research
For New Interfaces
- Follow the 6-step checklist in
10-checklist-new-interfaces.md - Reference relevant pattern files for specific UI components
- Use fidelity and visual style checklists to enhance quality
For Pattern Selection
- Identify the core problem (chunking, disclosure, cognitive load, etc.)
- Load the relevant pattern reference
- Evaluate benefits, use cases, psychological principles, and implementation guidelines
Decision Workflow Summary
When facing a UI decision:
1. WEIGH INFORMATION
ββ What does institutional knowledge say? (existing patterns, brand, tech constraints)
ββ What are users familiar with? (conventions, competitor patterns)
ββ What does research say? (user testing, analytics, studies)
2. NARROW OPTIONS
ββ Eliminate what conflicts with constraints
ββ Prioritize what aligns with macro bets
ββ Choose based on JTBD support
3. EXECUTE
ββ Apply relevant checklist + patterns
Macro Bet Categories
Companies win through one or more of:
| Bet | Description | Design Implication |
|---|---|---|
| Velocity | Features to market faster | Reuse patterns, find metaphors in other markets |
| Efficiency | Manage waste better | Design systems, reduce WIP |
| Accuracy | Be right more often | Stronger research, instrumentation |
| Innovation | Discover untapped potential | Novel patterns, cross-domain inspiration |
Always align micro design bets with company macro bets.
Key Principle: Good Design Decisions Are Relative
A design decision is "good" when it:
- Supports the product's jobs-to-be-done
- Aligns with company macro bets
- Respects constraints (time, tech, team)
- Balances user familiarity with differentiation needs
There is no universally correct UI solutionβonly contextually appropriate ones.
Generating Audit Reports
When asked to audit a design, generate a comprehensive report. Always include these sections:
Required Sections (always include)
- Visual Hierarchy β Headings, CTAs, grouping, reading flow, type scale, color hierarchy, whitespace
- Visual Style β Spacing consistency, color usage, elevation/depth, typography, motion/animation
- Accessibility β Keyboard navigation, focus states, contrast ratios, screen reader support, touch targets
Contextual Sections (include when relevant)
- Navigation β For multi-page apps: wayfinding, breadcrumbs, menu structure, information architecture
- Usability β For interactive flows: discoverability, feedback, error handling, cognitive load
- Onboarding β For new user experiences: first-run, tutorials, progressive disclosure
- Social Proof β For landing/marketing pages: testimonials, trust signals, social integration
- Forms β For data entry: labels, validation, error messages, field types
Audit Output Format
{
"title": "Design Name β Screen/Flow",
"project": "Project Name",
"date": "YYYY-MM-DD",
"figma_url": "optional",
"screenshot_url": "optional - URL to screenshot",
"macro_bets": [
{ "category": "velocity|efficiency|accuracy|innovation", "description": "...", "alignment": "strong|moderate|weak" }
],
"jtbd": [
{ "user": "User Type", "situation": "context without 'When'", "motivation": "goal without 'I want to'", "outcome": "benefit without 'so I can'" }
],
"visual_hierarchy": {
"title": "Visual Hierarchy",
"checks": [
{ "label": "Check name", "status": "pass|warn|fail|na", "notes": "Details" }
]
},
"visual_style": { ... },
"accessibility": { ... },
"priority_fixes": [
{ "rank": 1, "title": "Fix title", "description": "What and why", "framework_reference": "XX-filename.md β Section Name" }
],
"notes": "Optional overall observations"
}
Checks Per Section (aim for 6-10 each)
Visual Hierarchy: heading distinction, primary action clarity, grouping/proximity, reading flow, type scale, color hierarchy, whitespace usage, visual weight balance
Visual Style: spacing consistency, color palette adherence, elevation/shadows, typography system, border/radius consistency, icon style, motion principles
Accessibility: keyboard operability, visible focus, color contrast (4.5:1), touch targets (44px), alt text, semantic markup, reduced motion support
Navigation: clear current location, predictable menu behavior, breadcrumb presence, search accessibility, mobile navigation pattern
Usability: feature discoverability, feedback on actions, error prevention, recovery options, cognitive load management, loading states