Menu

Individual skill

ux-aesthetics-audit

0upvotes

Audit the visual quality of a UI against established visual-design principles — hierarchy, emphasis, contrast, spacing, alignment, grouping, consistency, and depth. Produces a severity-rated issue list with concrete fixes. Specializes in catching overdesign, clutter, and competing focal points. Use when reviewing whether a screen looks professional, or as a validation step after generating UI.

ux/audits/aesthetics/SKILL.md

Read pinned source

Source commit 5007cd0241ccaa51ae2e4681f9618912dc10e239

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
40
Repository last updated
Jul 2, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Visual Aesthetics Audit Skill


## How this skill behaves (read first)

This is an **evaluative** skill — it reviews existing work, it doesn't generate. It auto-runs and is built to be **called as a validation step** by generative skills. It's the **visual-quality backbone** of the repo: generators that produce UI (`pricing`, `login-signup`, `dashboard`, `onboarding`, component skills) hand off here to confirm they didn't tip into clutter or break hierarchy.

It owns **visual composition**. Two deliberate deferrals so it doesn't duplicate:

- **Color-contrast ratios, and any accessibility concern** (keyboard, screen readers, alt text) → the **accessibility audit**. This skill judges *visual* contrast/emphasis and harmony, not WCAG ratios.
- **Usability, flow, and interaction logic** → the **heuristics audit**. This skill judges how it *looks*, not how it *works*.

**Scope discipline.** When invoked directly (the user named this audit), review **only this concern** — don't pull in sibling audits. It runs alongside other lenses only when an orchestrator (`ux-design-review`) or a generative skill calls it under `docs/orchestration-policy.md`, where it sits in **Tier B — offered (and suppressed when a design system already defines visual harmony)**. Explicit scope always wins.
Back to top