Skip to content

Update Tailwind v4+ guidelines #321

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Nov 5, 2025
Merged

Update Tailwind v4+ guidelines #321

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0d83ad8
docs: update Tailwind v4+ guidelines with configuration guidelines
pushpak1300 Oct 28, 2025
f2e4f6d
Revert 4.1 change
pushpak1300 Oct 28, 2025
4c0e7a1
Update core.blade.php
taylorotwell Nov 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions .ai/tailwindcss/4/core.blade.php
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,13 @@

- Always use Tailwind CSS v4 - do not use the deprecated utilities.
- `corePlugins` is not supported in Tailwind v4.
- In Tailwind v4, configuration is CSS-first using the `@theme` directive — no separate `tailwind.config.js` file is needed.
@verbatim<code-snippet name="Extending Theme in CSS" lang="css">
@theme {
--color-brand: oklch(0.72 0.11 178);
}
</code-snippet>
@endverbatim
- In Tailwind v4, you import Tailwind using a regular CSS `@import` statement, not using the `@tailwind` directives used in v3:
@verbatim
<code-snippet name="Tailwind v4 Import Tailwind Diff" lang="diff">
Expand Down