fec-tailwind-design-system
Installation
SKILL.md
#Tailwind Design System
Suitable for front-end tasks hosting product design systems, component variations, and theme rules with Tailwind CSS. Load references/tailwind-system-patterns.md when specific configuration, variant, class organization and migration details are needed.
Purpose
Make the tokens, themes, component variations, and responsive styles in the Tailwind project maintainable instead of scattering one-off utility classes into business code.
Procedure
- Identify the current situation: Confirm Tailwind version, configuration location, dark mode strategy, component library, CSS variables, design token and class merging tool.
- Establish token boundaries: color, spacing, rounded corners, shadow, font, z-index and breakpoints are first derived from the project token or
theme.extend. - Design component variants: Basic components such as buttons, input boxes, cards, pop-up windows, and tables use centralized variant APIs to express size, semantics, status, and density.
- Control class complexity: Repeated combinations are precipitated into components, slots, variants or local helpers; do not copy long class strings to multiple pages.
- Handle themes and dark modes: Explicit
class,data-themeor CSS variable schemes to avoid first render flickering and contrast regression. - Access responsiveness: mobile-first organization utility; leave complex layouts to responsive layout workflow, don’t just rely on stacked breakpoint prefixes to try your luck.
- Verify style results: check hover, active, focus-visible, disabled, loading, selected, invalid, dark and different breakpoints.