Skip to content

Fix Next.js + Tailwind v4 PostCSS requirement#156

Open
policyengine[bot] wants to merge 1 commit into
mainfrom
bot/learnings-policyengine-ads-dashboard
Open

Fix Next.js + Tailwind v4 PostCSS requirement#156
policyengine[bot] wants to merge 1 commit into
mainfrom
bot/learnings-policyengine-ads-dashboard

Conversation

@policyengine

@policyengine policyengine Bot commented May 9, 2026

Copy link
Copy Markdown
Contributor

Summary

Fixes a documentation error in the frontend-builder-spec skill: Next.js projects using Tailwind v4 require postcss.config.mjs with the @tailwindcss/postcss plugin.

What was wrong

The spec incorrectly stated:

  • "MUST NOT have a postcss.config.js or postcss.config.mjs — Tailwind v4 does not require PostCSS"

This contradicted both:

  1. The correct setup documented in policyengine-ui-kit-consumer-skill
  2. The actual requirements of Next.js + Tailwind v4 integration

What changed

  • Added required PostCSS setup to the Tailwind CSS section
  • Updated package dependencies to include @tailwindcss/postcss and postcss
  • Added postcss.config.mjs to project structure
  • Removed the incorrect prohibition from the "What NOT to do" section

Context

Discovered while reviewing policyengine-ads-dashboard PR #2 (Vite → Next.js 16 migration). The migration correctly included PostCSS config, which would have been blocked by the old documentation.

🤖 Generated with Claude Code

Next.js requires postcss.config.mjs with @tailwindcss/postcss plugin.
The previous documentation incorrectly stated PostCSS was not needed.

Fixes based on policyengine-ads-dashboard migration (PR #2).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant