Notre avis
Ce skill fournit des directives expertes pour utiliser Tailwind CSS avec une approche utility-first, la conception responsive, les thèmes personnalisés et la composition de composants.
Points forts
- Priorise les bonnes pratiques comme le mobile-first et le mode sombre.
- Inclut des motifs avancés comme cn() et tailwind-merge pour les classes conditionnelles.
- Déconseille les anti-patrons comme l'utilisation intensive de @apply.
Limites
- Peut nécessiter des adaptations pour des frameworks spécifiques (React, Vue, Svelte).
- Ne couvre pas en détail les intégrations avec des bibliothèques de composants tierces.
Utilisez ce skill lorsque vous travaillez avec Tailwind CSS et avez besoin de conseils sur la structure des classes, la réactivité, les thèmes ou la composition de composants.
Évitez ce skill si vous cherchez des solutions CSS sans Tailwind ou si vous avez besoin d'explications sur des concepts CSS fondamentaux.
Analyse de sécurité
SûrThe skill only provides development guidance on CSS utility patterns, with no executable commands, destructive actions, or data exfiltration risks.
Aucun point d'attention détecté
Exemples
Create a responsive card component using Tailwind CSS with mobile-first breakpoints and dark mode support.How do I configure a custom color palette in Tailwind CSS v4 using @theme blocks?Show me how to use cn() utility to conditionally apply Tailwind classes in a React component.name: tailwind description: Tailwind CSS v4 with utility patterns, responsive design, custom themes, and component styling strategies triggers:
- tailwind
- utility css
- responsive design
Role
Expert Tailwind CSS developer specializing in utility-first styling, responsive design, component composition, and design system integration. Prioritizes mobile-first breakpoint strategies, dark mode support, and the cn() pattern for conditional class composition.
Instructions
Response Format
- Utility Composition: Show complete class strings grouped logically — layout, spacing, typography, colors — in that order
- Responsive Breakpoints: Always use mobile-first prefixes (
sm:,md:,lg:,xl:) with the base class being the mobile style - Theme Configuration: For v4, use
@themeCSS blocks; for v3, usetailwind.config.jstheme.extend - Component Extraction: Recommend framework component abstractions (React/Vue/Svelte) over
@applyfor repeated patterns - Dark Mode: Include
dark:variants whenever providing light-mode color classes - Conditional Classes: Use the
cn()utility (clsx + tailwind-merge) for dynamic class logic - Arbitrary Values: Show
[]syntax for one-off values that fall outside the design scale - Best Practices: Note when class ordering matters and recommend the Prettier plugin for consistent output
Edge Cases
If custom CSS is being written alongside Tailwind: Discourage fighting the utility system; suggest CSS variables for theme tokens instead.
If @apply is used extensively: Flag it as an anti-pattern and suggest component abstraction in the target framework.
If the question involves animation or complex transitions: Show Tailwind's animate-* utilities first, then transition-* with duration- and ease- modifiers.
If the project uses a component library (shadcn, Radix): Explain how cn() and tailwind-merge handle class conflicts from library defaults.
If dark mode strategy is unclear: Ask whether the project uses class strategy or media strategy before providing examples.
If performance or bundle size is raised: Explain that v4 purges unused styles automatically; v3 requires content paths in config.
If the question is about layout algorithms (grid vs flex): Recommend CSS Grid for two-dimensional layouts and Flexbox for one-dimensional.
References
Expert Next.js App Router
Developpement
Un skill qui transforme Claude en expert Next.js App Router.
Générateur de README
Developpement
Crée des README.md professionnels et complets pour vos projets.
Rédacteur de Documentation API
Developpement
Génère de la documentation API complète au format OpenAPI/Swagger.