What do you want to do?
3 use cases
-
Block arbitrary Tailwind values in agent-written UI
Flag off-scale Tailwind values so agents use your theme's spacing, colors, and sizes instead.
- Lint
- Software and DevOps
- Intermediate
View prompt
Use the GitHub repo shadcn-ui/lint to set up the no-arbitrary-values rule in <project-path>. Follow the README ESLint setup for React, then run the lint command. Expected output: a list of arbitrary Tailwind values in the project, or zero errors. Verify that the rule reports a test class such as p-[13px] in one component file.
-
Lock component styling with per-component contracts
Let pages change some styles on a component while keeping its size, shape, and font fixed.
- Lint
- Software and DevOps
- Advanced
View prompt
Use the GitHub repo shadcn-ui/lint to add a no-restyle contract for <component-name> in <project-path>. Write the contract in the ESLint config, then run the lint command. Expected output: the contract allows the listed classes and reports the others. Verify that one disallowed class on <component-name> produces the custom message from the config.
-
Make coding agents fix Lint errors before finishing
Give the agent a Lint command and an instruction to run it and fix errors after every change.
- Lint
- Software and DevOps
- Intermediate
View prompt
Use the GitHub repo shadcn-ui/lint to set up the lint loop in <project-path>. Install the package, add the lint script, and add the README instruction to AGENTS.md. Expected output: npm run lint exits cleanly on the current code. Verify that a deliberate arbitrary value in one file makes the command report an error.
How to use Lint
- Check you have what it needs: Node.js 20.19 or later; A Tailwind v4 project (shadcn/ui is not required); ESLint 9.30 or later, or Oxlint 1.80 or later.
- Open shadcn-ui/lint on GitHub and read the README and license.
- Run
npm install -D @shadcn/lint eslint @typescript-eslint/parserin the project. - Create eslint.config.mjs with the shadcn plugin and the rule "shadcn/no-arbitrary-values": "error", as shown in the React ESLint setup.
- Run
npx eslint .and confirm it reports any existing arbitrary values. - Fix the reported files or add the Lint command to package.json as the Lint script.
These steps come from our top use case, Block arbitrary Tailwind values in agent-written UI, which also has a copy-paste agent prompt.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeAbout this repo
- Who it is forFront-end developers and teams using coding agents to write React, Vue, or Svelte UI on a Tailwind v4 project.
- Why it is hot
- LanguageTypeScript
- Sourcegithub.com/shadcn-ui/lint · Back to Hot repos
Requirements
- Node.js 20.19 or later
- A Tailwind v4 project (shadcn/ui is not required)
- ESLint 9.30 or later, or Oxlint 1.80 or later
- A React, Vue, or Svelte project
Maintain Lint? Add the Featured on Deduped badge
Paste this into your README:
[](https://dedupedai.com/use-cases/shadcn-ui-lint/?ref=badge)
Questions about Lint
What is Lint?
A linter for Tailwind design systems that lets you define allowed styling and gives coding agents fix suggestions drawn from your own components and theme. It is an open-source project on GitHub: https://github.com/shadcn-ui/lint.
Who is Lint for?
Front-end developers and teams using coding agents to write React, Vue, or Svelte UI on a Tailwind v4 project.
What can I do with Lint?
3 use cases so far, for example: Block arbitrary Tailwind values in agent-written UI; Lock component styling with per-component contracts; Make coding agents fix Lint errors before finishing. Each has steps and a copy-paste agent prompt.
What do I need to run Lint?
Node.js 20.19 or later; A Tailwind v4 project (shadcn/ui is not required); ESLint 9.30 or later, or Oxlint 1.80 or later; A React, Vue, or Svelte project.
What are alternatives to Lint?
Other hot AI repos in Software and DevOps: Harness2, iFixAi, Orca, Diagram Design, AI Memory.
Is Lint safe to run?
Deduped does not own, audit or vouch for it. Read the README and license, run it on your own systems first and review every command before you run it.