optimize

Optimize Tailwind CSS

If $ARGUMENTS is empty or not provided:

Analyze Tailwind CSS output and provide optimization recommendations.

Usage: /tailwind-optimize [path] [options]

• /tailwind-optimize — quick analysis
• /tailwind-optimize ./apps/storefront — analyze one project or subtree
• /tailwind-optimize ./src/app.css — analyze a specific Tailwind entry
• /tailwind-optimize --report — detailed report
• /tailwind-optimize --fix — apply safe optimizations

Analyzes: bundle size (dev vs prod, gzipped) · source coverage (@source paths cover all templates) · unused classes (in CSS but not templates) · CSS variable bloat · build performance.

Proceed with optimization analysis.

---

If $ARGUMENTS is provided:

Parse arguments:

• Path — directory or file (default: current directory)
• --report — detailed markdown report
• --fix — apply safe optimizations
• --verbose — show all findings

Bind the requested or implicitly derived path to <OPTIMIZE_TARGET> as a concrete normalized path. If no path was supplied, bind the current directory. Stop with a clear error when the target does not exist. Resolve the containing project or package root to <PROJECT_ROOT> for build configuration and local dependency lookup, but never use <PROJECT_ROOT> as a replacement discovery target.

Bind <SUPPORTED_SOURCE_EXTENSIONS> once to the project's complete source set and use it for target validation, directory discovery, @source verification, <TEMPLATE_FILES>, class inventory, reporting, and fixes. The baseline set is:

js, jsx, ts, tsx, html, htm, templ, vue, svelte, astro, php, blade.php, erb, hbs, md, mdx, ejs, twig, liquid, njk, nunjucks, pug, jade, haml, slim, razor, and cshtml.

This baseline is not an allowlist. Tailwind scans non-ignored plain-text source files, so add every other text source selected by an @source rule or the chosen build integration. Exclude CSS, binary files, lockfiles, node_modules, and ignored paths using Tailwind's source-detection rules. Never omit a target-associated source merely because its extension is absent from the baseline.

When <OPTIMIZE_TARGET> is a directory, limit CSS entries, generated artifacts, and templates to that subtree. When it is a CSS file, bind that file directly to <CSS_ENTRY> and derive <TEMPLATE_FILES> only from its @source rules and the selected integration's content scope. When it is a supported template file, use that file as the complete <TEMPLATE_FILES> set and locate only the Tailwind entry associated with its containing integration. For any other file type, stop with a clear unsupported-target error. Retain the complete <TEMPLATE_FILES> set for every later analysis and fix; do not widen discovery to ..