Find agent skills by outcome

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

not by eye)

At each breakpoint

check:

For each page/section

verify:

- [ ] Typography: correct font

weight

- Target breakpoints: [e.g.

375px

Creative

Visual QA & Cross-Browser Audit

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

- Target browsers: [e.g.

Chrome

every visual discrepancy

interaction bug

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

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.

Coding & Debugging

If no CLAUDE.md exists yet: Tell the prompt to generate a minimal token section at the top of the handoff document covering only the tokens needed for this specific handoff. It won't be a full design system

but it prevents hardcoded values.

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.

7. When encountering ambiguity

prefer the more explicit interpretation.

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

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

not `gap-5`.

□ Every state (hover

active

is not in CLAUDE.md

flag it and use the fallback value provided.

□ Focus-visible ring appears on keyboard nav

not on mouse click

Coding & Debugging

After implementation

the AI agent (or human developer) should verify:

date other year: show Mar 13

2025

date this year: show Mar 13 not Mar 13

2026

list with 500 items: paginate at 20

show Load more button