Skip to content

Dragoon0x/taste-skills / skills/perception/visual-audit

visual-audit

Verified

The 10-second design audit. Look at any design and name what's working and what's not within seconds. Trains rapid pattern recognition for hierarchy, spacing, type, and color. Use when evaluating designs quickly, giving first-impression feedback, or building perception speed.

Visual Audit

Look at any design and name what's working and what's not. Fast.

How to use

  • /visual-audit Apply 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
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 470kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall