init

Initialize Tailwind CSS v4

If $ARGUMENTS is empty or not provided:

Initialize Tailwind CSS v4 in the current directory.

Usage: /tailwind-init [project-path]. /tailwind-init (current dir) or /tailwind-init ./my-app (specific dir).

What it does: detect project type → check for existing Tailwind → choose integration method → install deps → create CSS entry file with v4 syntax → configure the selected build integration.

v4 key changes: no tailwind.config.js (configure in CSS via @theme); single @import "tailwindcss";; auto-detects templates (@source only for custom paths).

Proceed after binding the current directory as the initialization operation root described below.

---

If $ARGUMENTS is provided:

Initialize Tailwind CSS v4 in: $ARGUMENTS.

Initialization Operation Root

Parse at most one positional project path from the invocation arguments. Bind the requested project path to <INIT_TARGET> as one concrete normalized absolute directory. When no path was provided, bind the invocation's current directory. Stop before any mutation when the path does not exist, is not a directory, or extra positional arguments remain. Bind <INIT_TARGET> once and do not re-derive or broaden it later.

Treat <INIT_TARGET> as the application and integration mutation scope for the entire workflow. Execute application discovery, file edits, integration configuration, and direct tool validation with <INIT_TARGET> as the working directory. Resolve every application path, including the member package.json, CSS entries, build configuration, and .gitignore, against <INIT_TARGET>. The only permitted ancestor discovery and mutation are the read-only package-ownership search and owning lockfile update described under Package Manager Selection. Do not treat the package root as a broader application mutation scope, and do not inspect or change the invocation directory unless it is <INIT_TARGET> or the owning package root.

Loop Initialization