What it is
A linter for Tailwind design systems built for agents rather than humans: it encodes design system rules so an agent writing UI code gets corrected against them.
Why it showed up
2.2k stars, published under the shadcn-ui organisation. It reflects a shift where lint output is consumed by agents, not read by developers.
Who should look at it?
Teams that let agents create or modify Tailwind interfaces should look at this as a feedback loop for UI quality. A design-system linter gives the agent a machine-readable boundary instead of relying on a reviewer to catch every inconsistency.
What to inspect
Check which rules are encoded, how violations are reported, and whether the output points to a concrete correction. The closer the diagnostic is to a normal lint result, the easier it is to add to an agent’s edit-and-check loop.
Watch point
Rules can enforce consistency without proving that a page is useful or accessible. Pair the linter with visual review, interaction tests and product-specific constraints.