design-lint vs visual QA in the browser

design-lint is a judged, rule-shaped pass the agent runs on the work in front of it. Visual QA in the browser is you looking at the live page — spacing, type, and states your eyes catch. Use the skill for a repeatable lint; use the browser when you need to see the real pixels.

Which one should you use?

design-lint is a judged, rule-shaped pass the agent runs on the work in front of it. Visual QA in the browser is you looking at the live page — spacing, type, and states your eyes catch. Use the skill for a repeatable lint; use the browser when you need to see the real pixels.

Side by side.

OptionWhat it doesWhere it runsBest for
design-lint skillAgent applies a strict design QA procedureIn the repo / current filesYou want a consistent judged pass
Visual QA in the browserYou inspect the rendered pageLocal or live URLYou need real pixels, motion, and breakpoints

When the skill fits.

You already have markup and want the agent to apply the same lint every time — not a vibe check.

When the browser fits.

Hover states, real fonts, and overflow only show up rendered. Look at the page. The skill does not replace that.