Design Lint (Quick Check)

When to Use

Use this skill when you need quick automated lint — detects common design system violations in seconds.

When NOT to use

• For deeper review of design judgment (composition, hierarchy, rhythm) → use /ss-review
• For accessibility specifically → use /ss-a11y
• For Nielsen UX heuristics → use /ss-audit
• For applying refactors — this only flags violations; use /ss-review to fix

Target: $ARGUMENTS

What This Does

Fast, grep-based candidate scan. First read the project design tokens and conventions: pure black, physical spacing, data-slot, cn() and size-* are project-dependent choices, not universal violations. Replace [file] with a quoted actual path. The /ss-* commands are upstream host conventions and may not be installed. Inspect each match in context before reporting a defect.