Frontend · Claude Code (via permissions.deny)
Tailwind CSS v4 .claudeignore
A .claudeignore for Tailwind CSS v4: the paths Claude Code should stay out of, with matching permissions.deny rules.
- Path
- .claudeignore
- Loads
- Pattern list
- Format
- gitignore syntax
- Used by
- Claude Code (via permissions.deny)
What this file tells the agent
Claude Code reads files while it works. This .claudeignore keeps the list of Tailwind CSS v4 paths it should stay out of (build output, large binaries, logs and secrets). Copy the sensitive ones into permissions.deny in .claude/settings.json, which Claude Code enforces.
- Configure themes directly in globals.css using `@theme` and `@import 'tailwindcss';`.
- Never generate or modify legacy `tailwind.config.js` or `tailwind.config.ts` files.
- Use CSS custom properties for dynamic color palettes.
- Enforce consistent utility ordering: layout -> spacing -> typography -> background -> borders -> interactivity.
Code to avoid, and what to write instead
The rule steers the agent away from the left and toward the right.
// Discouraged in v4: Obsolete tailwind.config.js
module.exports = {
theme: {
extend: { colors: { brand: "#f97316" } }
}
};@import "tailwindcss";
@theme {
--color-brand-primary: #f97316;
--font-display: "Geist Sans", sans-serif;
}Install it in one command
- 01
Go to your project root
The file goes at .claudeignore, relative to the root.
- 02
Download the file
Run the command on the right. It downloads this preset and writes the file.
- 03
Make sure it gets used
Claude Code does not enforce .claudeignore by itself. Copy the sensitive paths into permissions.deny in .claude/settings.json, which it does enforce.
$ curl -fsSL "https://www.devscratchpad.tech/api/raw/claudeignore/tailwind-v4" -o ".claudeignore"
writes .claudeignore
.claudeignore
To write the file from your own code instead, use Read your code or Convert Legacy Rules in the editor above.
More for Tailwind CSS v4
Other formats
Other .claudeignore presets
Questions
- Does Claude Code honor .claudeignore?
- Not by itself. Claude Code enforces permission rules, so copy the sensitive paths into permissions.deny in .claude/settings.json, for example Read(./.env). Keep .claudeignore in the repository root as the reviewable list.
- What should I put in .claudeignore?
- Exclude large build caches, minified bundles, lockfiles, and environment files containing sensitive credentials.