agentleFS
timeyourtimeyour/agentskills-audit-collection/.claude/skills/visual-qa/SKILL.md

visual-qa

Skill1 starsChanged 6 months agoMITView on GitHub

Audit visual quality, aesthetic craft, UI consistency, layout, responsive behavior, typography, spacing, trust signals, and AI slop patterns in a website, app, screenshot, or generated UI.

20 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user wants to know whether a page feels designed, credible, consistent, and conversion-ready.

    line 11
  2. Distinctive:

    Use measurable aesthetic heuristics for spacing, hierarchy, color roles, visual weight, component consistency, and Figma/code fidelity when …

    line 19
  3. Very specific:

    Use S0-S4 severity and include regression checks for visual fixes.

    line 24

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Visual QA

Use this skill when the user wants to know whether a page feels designed, credible, consistent, and conversion-ready.

Do

  1. Identify product category and intended user scenario.
  2. Inspect first viewport, hierarchy, spacing, typography, color, imagery, components, and responsive behavior.
  3. Inventory visible media, document links, embeds, and product screenshots when they affect trust or layout.
  4. Flag AI slop: generic gradients, repeated icon cards, fake proof, vague copy, mismatched components, irrelevant imagery.
  5. Use measurable aesthetic heuristics for spacing, hierarchy, color roles, visual weight, component consistency, and Figma/code fidelity when evidence exists.
  6. Separate screenshot-backed findings from source-only findings.
  7. Compare against the right product pattern: local service, SaaS, portfolio, directory, dashboard, lifestyle commerce, etc.
    • For product-pattern questions (scenario, outcome, next-step, inspiration vs. action), invoke /ai-product-audit or use ../ai-product-audit/references/product-pattern-rubric.md.
  8. Produce section-level issue cards and copyable design-fix prompts.
  9. Use S0-S4 severity and include regression checks for visual fixes.
  10. For multi-section reviews, emit progress updates after each major page section or viewport group.

References

  • references/aesthetic-quality-audit.md
  • references/aesthetic-metrics.md
  • references/webpage-audit-rubric.md
  • ../audit/references/progressive-reporting.md for long visual audits
  • ../audit/references/web-surface-discovery.md when media, documents, or embeds need inventory

Output

  • Aesthetic audit summary.
  • Visual score with evidence level.
  • Pattern fit table.
  • AI slop signals.
  • S0-S4 severity.
  • Issue cards.
  • Copyable fix pack.
  • Regression checks.
  • Lessons.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.