Tailwind Design System
Guidelines for building a consistent, scalable design system using Tailwind CSS and utility-first principles.
Core Principles
- •Utility-First: Build components using atomic styles for maximum speed and consistency.
- •Design Tokens: Centralize colors, spacing, and typography in
tailwind.config.js. - •Mobile-First: Always build for mobile first using the
md:,lg:, etc., breakpoints.
Best Practices
- •Component Extraction: Use the
@applydirective sparingly; prefer component composition in React. - •Dynamic Classes: Avoid string interpolation for class names; use full class names for purge compatibility.
- •Arbitrary Values: Use
[]for one-off values while maintaining the design system's discipline.
Usage
- •Reference when implementing new UI designs or landing pages.
- •Use for refactoring "messy" CSS into clean Tailwind utilities.
- •Apply when debugging responsive layout issues or theme inconsistencies.