- Refine and expand best practices for: - AI SDK - Date-fns - Next.js - Radix UI - React - React Hook Form - Stripe - Tailwind CSS - TypeScript - Zustand - Improve guidelines with more specific and actionable recommendations - Enhance type safety and performance suggestions across different technologies
13 lines
537 B
Plaintext
13 lines
537 B
Plaintext
---
|
|
description: Best practices for styling with Tailwind CSS
|
|
globs: **/*.{ts,tsx,css}
|
|
alwaysApply: false
|
|
---
|
|
|
|
- Use utility-first approach for rapid development and maintainability
|
|
- Implement responsive design using Tailwind's built-in breakpoints
|
|
- Utilize the `@apply` directive for creating custom utility classes
|
|
- Leverage Tailwind's JIT mode for improved performance and smaller bundle sizes
|
|
- Utilize `tailwind-merge` for efficient class merging and overriding
|
|
- Leverage `tailwindcss-animate` for easy animation implementation
|