bundles/frontend/skills/tailwind/SKILL.md
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
npx skillsauth add shipshitdev/library tailwindInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Comprehensive performance optimization guide for Tailwind CSS v4 applications. Contains 44 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.
Reference these guidelines when:
| Priority | Category | Impact | Prefix |
|----------|----------|--------|--------|
| 1 | Build Configuration | CRITICAL | build- |
| 2 | CSS Generation | CRITICAL | gen- |
| 3 | Bundle Optimization | HIGH | bundle- |
| 4 | Utility Patterns | HIGH | util- |
| 5 | Component Architecture | MEDIUM-HIGH | comp- |
| 6 | Theming & Design Tokens | MEDIUM | theme- |
| 7 | Responsive & Adaptive | MEDIUM | resp- |
| 8 | Animation & Transitions | LOW-MEDIUM | anim- |
build-vite-plugin - Use Vite Plugin Over PostCSSbuild-css-import - Use CSS Import Over @tailwind Directivesbuild-content-detection - Leverage Automatic Content Detectionbuild-node-version - Use Node.js 20+ for Optimal Performancebuild-postcss-simplify - Remove Redundant PostCSS Pluginsbuild-cli-package - Use Correct CLI Packagegen-css-first-config - Use CSS-First Configuration Over JavaScriptgen-avoid-theme-bloat - Avoid Excessive Theme Variablesgen-oklch-colors - Use OKLCH Color Space for Vivid Colorsgen-utility-directive - Use @utility for Custom Utilitiesgen-dynamic-utilities - Use Dynamic Utility Valuesgen-css-variable-syntax - Use Parentheses for CSS Variable Referencesbundle-remove-unused-plugins - Remove Built-in Pluginsbundle-avoid-preprocessors - Avoid Sass/Less Preprocessorsbundle-css-minification - Enable CSS Minification in Productionbundle-avoid-cdn-production - Avoid Play CDN in Productionbundle-split-critical-css - Extract Critical CSS for Initial Renderutil-renamed-utilities - Use Renamed Utility Classesutil-important-modifier - Use Trailing Important Modifierutil-variant-stacking - Use Left-to-Right Variant Stackingutil-explicit-colors - Use Explicit Border and Ring Colorsutil-opacity-modifier - Use Slash Opacity Modifierutil-gradient-via-none - Use via-none to Reset Gradient Stopscomp-avoid-apply-overuse - Avoid Overusing @applycomp-reference-directive - Use @reference for CSS Module Integrationcomp-utility-file-scope - Understand Utility File Scopecomp-smart-sorting - Leverage Smart Utility Sortingcomp-container-customize - Customize Container with @utilitycomp-custom-variant - Use @custom-variant for Custom Variant Definitionstheme-semantic-tokens - Use Semantic Design Token Namestheme-dark-mode-class - Use Class-Based Dark Mode for Controltheme-prefix-variables - Use Prefix for Variable Namespacingtheme-runtime-variables - Leverage Runtime CSS Variablestheme-color-scheme - Set color-scheme for Native Dark Modetheme-inline-static - Use @theme inline and @theme static for Variable Controlresp-mobile-first - Use Mobile-First Responsive Designresp-container-queries - Use Container Queries for Component-Level Responsivenessresp-custom-breakpoints - Define Custom Breakpoints in @themeresp-hover-capability - Pair Hover with Active for Touch-Friendly Interactionsresp-logical-properties - Use Logical Properties for RTL Supportanim-gpu-accelerated - Use GPU-Accelerated Transform Propertiesanim-starting-style - Use @starting-style for Entry Animationsanim-gradient-interpolation - Use OKLCH Gradient Interpolationanim-3d-transforms - Use Built-in 3D Transform UtilitiesRead individual reference files for detailed explanations and code examples:
| File | Description | |------|-------------| | references/_sections.md | Category definitions and ordering | | assets/templates/_template.md | Template for new rules | | metadata.json | Version and reference information |
development
Create an isolated git worktree from the correct base branch and check it out into a clean, gitignored directory. Use when the user asks to make a worktree, spin up a parallel/isolated workspace, work on something without disturbing the current checkout, branch off the current work, or run multiple agents on the same repo at once. Picks the base branch smartly — the current feature branch when you are on one, otherwise the develop integration branch — so worktrees continue your in-progress work by default instead of forking from the wrong place.
development
Verify a release was fully promoted through develop, staging, and master/main, then prune merged local and remote branches and stale git worktrees. Squash-merge aware — uses GitHub PR merge state as the merge oracle, not commit ancestry. Use when the user asks to clean up branches after a deploy, prune worktrees, remove merged branches, tidy up after promoting develop to staging to master, or confirm nothing stale was left behind before pruning.
development
Structured "done coding, now what?" workflow: verify tests pass, detect the repository environment (normal repo vs worktree, named branch vs detached HEAD), present exactly the right merge / PR / keep / discard options, and execute the chosen path including safe worktree cleanup. Use when implementation is complete and the branch needs to be integrated, published, or abandoned.
tools
Capture a client or stakeholder feature request, turn it into a planner-ready PRD epic with scoped sub-issues, check for duplicate work, and place approved issues on a GitHub Projects kanban. Use when a user invokes feature intake, asks to turn a rough client requirement into GitHub issues, or wants an idea written as a PRD and pushed to a board.