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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontailwindExecute the skills CLI command in your project's root directory to begin installation:
Fetches tailwind from pproenca/dot-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate tailwind. Access via /tailwind in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
28
total installs
28
this week
95
GitHub stars
0
upvotes
Run in your terminal
28
installs
28
this week
95
stars
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:
For a complete guide with all rules expanded, see AGENTS.md.
| File | Description |
|---|---|
| AGENTS.md | Complete compiled guide with all rules |
| references/_sections.md | Category definitions and ordering |
| assets/templates/_template.md | Template for new rules |
| metadata.json | Version and reference information |
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
pproenca/dot-skills
pproenca/dot-skills
anthropics/claude-code
mblode/agent-skills
github/awesome-copilot
leonxlnx/taste-skill
I recommend tailwind for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Solid pick for teams standardizing on skills: tailwind is focused, and the summary matches what you get after install.
tailwind reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in tailwind — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
tailwind is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for tailwind matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in tailwind — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for tailwind matched our evaluation — installs cleanly and behaves as described in the markdown.
tailwind reduced setup friction for our internal harness; good balance of opinion and flexibility.
tailwind fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 44