AgentStack
Sign in Publish
MCP servers Skills Toolkits Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Visual Audit

skill-dragoon0x-taste-skills-visual-audit · by Dragoon0x

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.

↗ Repository
— No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-dragoon0x-taste-skills-visual-audit

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Visual Audit? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 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

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Agent Skills