tailwind-design-system
Build design systems with Tailwind CSS
Également disponible depuis: wshobson
Creating consistent design systems is complex and time-consuming. This skill provides proven patterns for building scalable component libraries with Tailwind CSS, design tokens, and accessibility built-in.
Télécharger le ZIP du skill
Importer dans Claude
Allez dans Paramètres → Capacités → Skills → Importer un skill
Activez et commencez à utiliser
Tester
Utilisation de "tailwind-design-system". Create a button with Tailwind CSS
Résultat attendu:
- Button component created with CVA variants
- Includes: default, destructive, outline, secondary, ghost, link variants
- Size options: default, sm, lg, icon
- Accessibility features: focus-visible ring, disabled state
- Type-safe with TypeScript interfaces
Utilisation de "tailwind-design-system". Set up dark mode for my app
Résultat attendu:
- ThemeProvider component with system preference detection
- CSS variables configured in globals.css
- Tailwind config extended with darkMode: class
- ThemeToggle component with sun/moon icons
- localStorage persistence for user preference
Audit de sécurité
SûrStatic analysis detected 78 potential issues, all confirmed as false positives. The 'backtick execution' patterns are Markdown code fences (```) for code samples. URLs are documentation references. localStorage usage is standard theme persistence. No executable code or security risks present.
Score de qualité
Ce que vous pouvez construire
Startup Component Library
Build a complete component library from scratch for a new product, including buttons, cards, forms, and dialogs with consistent styling.
Design System Migration
Migrate an existing CSS or styled-components codebase to Tailwind CSS with proper design token structure and component patterns.
Accessible Form Implementation
Create accessible form components with proper validation, error states, and keyboard navigation following WCAG guidelines.
Essayez ces prompts
Create a reusable Button component using Tailwind CSS and CVA. Include variants for primary, secondary, outline, and ghost styles. Add size variants (sm, md, lg) and a disabled state.
Generate a Tailwind CSS configuration file with semantic color tokens. Include primary, secondary, destructive, muted, accent, background, foreground, and border colors. Support both light and dark mode using CSS variables.
Build a Card component using the compound component pattern. Create Card, CardHeader, CardTitle, CardDescription, CardContent, and CardFooter subcomponents. Use forwardRef for proper React composition.
Implement a complete dark mode solution with a ThemeProvider component. Support system preference detection, localStorage persistence, and manual toggle. Include a ThemeToggle button component with sun/moon icons.
Bonnes pratiques
- Use CSS variables for runtime theming and design tokens
- Compose variants with CVA for type-safe component APIs
- Always include focus-visible states for keyboard accessibility
Éviter
- Using arbitrary values like h-[500px] instead of extending the theme
- Hardcoding colors directly in components instead of semantic tokens
- Skipping dark mode styles when building new components