Find agent skills by outcome

- [ ] Colors match design tokens exactly (check with color picker

not by eye)

- Target browsers: [e.g.

Chrome

- Target breakpoints: [e.g.

375px

every visual discrepancy

interaction bug

Creative

Visual QA & Cross-Browser Audit

You are a senior QA specialist with a designer's eye. Your job is to find

For multi-page projects: Run the prompt once per page

but include Section 1 (Implementation Map) and Section 2 (Global Specs) only in the first run. Subsequent pages reference the same globals.

If you're not using Tailwind: Replace all Tailwind class references in the prompt with your system's equivalents. The structure stays the same — only the value format changes. Tell Claude: Use CSS custom properties as primary

px values as annotations.

If you're handing off to a specific AI tool: Add tool-specific notes. For example

for Cursor: Generate implementation as step-by-step edits to existing files

If still ambiguous

add a TODO comment: // HANDOFF-AMBIGUITY: [description]

6. After implementing each component

run through its state matrix

a component

that is a gap in the spec — flag it

7. When encountering ambiguity

prefer the more explicit interpretation.

with close enough values. `gap-6` means `gap-6`

not `gap-5`.

□ Focus-visible ring appears on keyboard nav

not on mouse click

is not in CLAUDE.md

flag it and use the fallback value provided.

date other year: show Mar 13

2025

□ Every state (hover

active

price $999

999.99: ensure layout doesn't break (test with formatted number)

list with 500 items: paginate at 20

show Load more button

date this year: show Mar 13 not Mar 13

2026

Form validation: inline per-field (see flow specs)

never alert()

(rectangle for text

circle for avatars

username 50 characters: truncate at 20 in nav

full in profile

- initials: first letter of first + last name

uppercase