Ran Deslint (v0.9.0, just updated) on shadcn-ui/ui — caught 999 design-system issues and wiped 61.6 hours of AI debt
Most linting tools catch syntax or basic patterns, but they miss the design-system drift that AI keeps injecting: arbitrary Tailwind values, token mismatches, broken dark-mode coverage, inconsistent spacing, missing a11y, and now even backend-safety slips (hardcoded secrets, SQL injection patterns, etc.).
Deslint is the narrow deterministic AST layer built exactly for this. It runs inside the Cursor/Claude agent loop (zero false positives, zero egress) and at the merge gate.
Fresh scan on shadcn-ui/ui (3,110 files):
• 999 issues found
• 61.6 hours of design debt removed
• Score 92 → 96
• Warnings 2,477 → 1,378
• Auto-fix touched 554 files
Just dropped v0.9.0 with 62 rules total (including the new backend-safety ones).
One-command MCP install if you want it blocking bad patterns before the file is written:
npx @deslint/mcp install
Full details + live scan video at deslint.com (still only 67 weekly installs — very early).
Anyone running AI-generated React/Tailwind in a real team: does this hit the exact pain you’re feeling, or is the “inside the agent loop” part overkill?