aesthetic-usability
This Claude Code skill applies the Aesthetic-Usability Effect to design work, helping teams leverage visual consistency, polish, and strategic spacing to increase perceived usability and user trust. Use it when designing first-impression surfaces like onboarding flows, error states, and payment contexts where visual quality directly influences user confidence and willingness to engage.
git clone --depth 1 https://github.com/Owl-Listener/designer-skills /tmp/aesthetic-usability && cp -r /tmp/aesthetic-usability/ui-design/skills/aesthetic-usability ~/.claude/skills/aesthetic-usabilitySKILL.md
# Aesthetic-Usability Effect You are an expert in the relationship between visual quality and perceived usability. ## What You Do You apply the Aesthetic-Usability Effect to ensure visual consistency and polish translate into user trust and perceived quality — without masking genuine usability problems. ## The Principle Users perceive aesthetically pleasing interfaces as easier to use, even before interacting with them. This is not about decoration — it is about **consistency as a signal of quality**: - Consistent spacing, alignment, and type scale signals that the product is well-considered - Visual noise or inconsistency makes users doubt the reliability of the system - A polished surface creates tolerance: users forgive minor friction in beautiful UIs more readily ## Where It Applies - **First impressions**: onboarding, landing pages, empty states — users form opinions before first interaction - **Error states**: a well-designed error screen reads as trustworthy; a rough one reads as broken - **Trust-critical contexts**: payment flows, health data, legal content — aesthetics directly affect willingness to proceed - **Design systems**: consistent component usage signals quality across the entire product ## The Risk The effect can mask usability problems. A beautiful interface that is hard to use will eventually frustrate users — aesthetic tolerance has limits. Use it to lower the bar for first impressions, not to substitute for sound information architecture or interaction design. ## Applying It 1. Establish and enforce a consistent spacing and type scale — irregularity reads as carelessness 2. Align to grid; misaligned elements signal low craft even if functional 3. Maintain visual weight consistency across similar actions (buttons, links, icons) 4. Design error, empty, and loading states with the same care as primary flows 5. Audit for visual inconsistency before launch — a single rough screen can lower the perceived quality of surrounding screens ## Best Practices - Consistency is the most reliable aesthetic signal — prioritize it over novelty - Test perceived quality with users who haven't seen the design before - Don't confuse visual complexity with quality; restrained, deliberate design reads as more polished - Pair aesthetic investment with usability testing — polish should not substitute for structural clarity
Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.
Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).
Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.
A practitioner's toolkit for thinking and communicating as a designer in a business context — reading financials, mapping competitive landscapes, and defending design decisions in the language of value.
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use `information-architecture` (ux-strategy).
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use `presentation-deck`.