shadcn lint
@shadcn/lint is an 'agent-first' linter for Tailwind v4 design systems from shadcn, the creator of shadcn/ui. You declare which components own their styling and what may change; when a coding agent breaks a rule, the error explains what is wrong and suggests the allowed fix (a size, variant, or theme token) read from your own components and theme, so the agent can correct it in one pass. It ships as an ESLint and Oxlint plugin and works with any Tailwind v4 project, shadcn/ui not required.
Released 2026-09-14 and passed 2,200 GitHub stars within a week; frequent 0.1.x releases (0.1.5 on 2026-09-21). The project reports testing its rules with coding agents across 150+ task runs, with nearly every task reaching zero violations in a single correction round.
As of
- Rules: no-restyle, no-raw-colors, no-arbitrary-values, no-inline-styles, no-unknown-classes, and a rule for dynamic classes the linter cannot read
- Error messages generated from your source: lists the actual sizes/variants a component defines and the file they live in
- Per-component contracts (e.g. allow layout/margin but keep spacing and shape inside the Button) without changing the component API
- Available as both an ESLint 9 and an Oxlint plugin
- Agent-driven setup via a prompt pointing at SETUP.md; pairs with an AGENTS.md instruction to run lint and fix errors
- Works with existing Tailwind v4 design systems; shadcn/ui is optional
Frontend teams using Tailwind v4 (with or without shadcn/ui) that let coding agents like Claude Code, Codex, or Cursor write UI and want design-system rules enforced with feedback the agent can act on.
Projects not on Tailwind v4, CSS-in-JS or non-utility styling setups, or teams without a defined component design system to encode as rules.
@shadcn/lint is MIT-licensed and free; install with `npm install -D @shadcn/lint` alongside ESLint 9.30+ or Oxlint 1.80+ on Node.js 20.19+. No hosted service or paid tier.
@shadcn/lint is a sharp, narrowly scoped idea executed well: it turns design-system guardrails into lint errors written for models instead of humans, which is exactly the feedback loop agent-written frontend code has been missing. It is young and Tailwind v4-only, but for shadcn/Tailwind shops using coding agents it is a low-cost, high-leverage addition.
Is shadcn lint free?
Yes - shadcn lint is Open Source. @shadcn/lint is MIT-licensed and free; install with `npm install -D @shadcn/lint` alongside ESLint 9.30+ or Oxlint 1.80+ on Node.js 20.19+. No hosted service or paid tier.
Is shadcn lint open source?
Yes - shadcn lint is open source. @shadcn/lint is MIT-licensed and free; install with `npm install -D @shadcn/lint` alongside ESLint 9.30+ or Oxlint 1.80+ on Node.js 20.19+. No hosted service or paid tier.
Who is shadcn lint best for?
Frontend teams using Tailwind v4 (with or without shadcn/ui) that let coding agents like Claude Code, Codex, or Cursor write UI and want design-system rules enforced with feedback the agent can act on.
Who is shadcn lint not ideal for?
Projects not on Tailwind v4, CSS-in-JS or non-utility styling setups, or teams without a defined component design system to encode as rules.
What are the best shadcn lint alternatives?
The closest shadcn lint alternatives on ai.dosa.dev are Pieces for Developers, agenttrace, Vibe Kanban - all listed under Developer Productivity & Workflow.
Who makes shadcn lint?
shadcn lint is developed by shadcn. It is listed in the Developer Productivity & Workflow category on ai.dosa.dev.
Favorite this tool to revisit it later, or Zap it to contribute to the public vote count.
Content on this page is AI-generated. Please verify details with the vendor's website for accuracy.