Use for utility-first CSS styling in server-rendered or React-based applications.
Rules
Use utility classes as the default styling mechanism.
Keep utility usage readable and intentional; do not pile on conflicting classes without reason.
Avoid custom CSS unless utilities cannot express the requirement cleanly.
Prefer composition through reusable UI components for repeated patterns.
Shared Usage
Use spacing, layout, typography, color, and responsive utilities directly in markup/components.
Use state and responsive variants intentionally (hover:, focus:, md:, dark:).
Keep dark mode strategy explicit and consistent across the project.
Thymeleaf / SSR Usage
Use Tailwind classes directly in server-rendered templates and fragments.
Keep repeated UI structures in reusable Thymeleaf fragments/components when class sets repeat.
React Usage
Use Tailwind utilities through className in React components.
Extract repeated UI patterns into reusable React components instead of duplicating long utility strings.
Keep conditional class logic simple and readable; prefer clear branching over tangled string concatenation.
Represent UI variants (size, tone, state) through props and predictable class composition.
Keep presentational components pure and let React state drive visual states.
Defaults
Tailwind is the primary styling system for the project.
Component extraction is preferred when the same utility combination appears repeatedly.
Dark mode uses Tailwind's dark: variant with one project-wide strategy.
Anti-Patterns
Do NOT mix with Bootstrap in the same project.
Do NOT create unreadable, excessively long inline class strings without extracting a reusable abstraction.
Do NOT hide important visual logic in scattered conditional class concatenation.
Do NOT reach for custom CSS first when utilities and component composition are sufficient.
Anti-Patterns
Do NOT mix with Bootstrap in the same project
1---2name: tailwindcss3description: Skill: tailwindcss4---5# Skill: tailwindcss67## Type8styling910## Conflicts1112- bootstrap-ui-framework1314## When to Use1516Use for utility-first CSS styling in server-rendered or React-based applications.1718---1920## Rules2122- Use utility classes as the default styling mechanism.23- Keep utility usage readable and intentional; do not pile on conflicting classes without reason.24- Avoid custom CSS unless utilities cannot express the requirement cleanly.25- Prefer composition through reusable UI components for repeated patterns.2627---2829## Shared Usage3031- Use spacing, layout, typography, color, and responsive utilities directly in markup/components.32- Use state and responsive variants intentionally (`hover:`, `focus:`, `md:`, `dark:`).33- Keep dark mode strategy explicit and consistent across the project.3435---3637## Thymeleaf / SSR Usage3839- Use Tailwind classes directly in server-rendered templates and fragments.40- Keep repeated UI structures in reusable Thymeleaf fragments/components when class sets repeat.4142---4344## React Usage4546- Use Tailwind utilities through `className` in React components.47- Extract repeated UI patterns into reusable React components instead of duplicating long utility strings.48- Keep conditional class logic simple and readable; prefer clear branching over tangled string concatenation.49- Represent UI variants (`size`, `tone`, `state`) through props and predictable class composition.50- Keep presentational components pure and let React state drive visual states.5152---5354## Defaults5556- Tailwind is the primary styling system for the project.57- Component extraction is preferred when the same utility combination appears repeatedly.58- Dark mode uses Tailwind's `dark:` variant with one project-wide strategy.5960---6162## Anti-Patterns6364- Do NOT mix with Bootstrap in the same project.65- Do NOT create unreadable, excessively long inline class strings without extracting a reusable abstraction.66- Do NOT hide important visual logic in scattered conditional class concatenation.67- Do NOT reach for custom CSS first when utilities and component composition are sufficient.6869---7071## Anti-Patterns7273- Do NOT mix with Bootstrap in the same project
Run npx skillmds@latest add carlnaddy/tailwindcss in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
Skill: tailwindcss It is listed under Coding & Dev Tools on SkillMD.
This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
CarlNaddy (@carlnaddy) published this skill. Their other Agent Skills are listed on their SkillMD profile.