tailwindcss · mindrally — Claude Code skill: utility-first styling rules
Tells the agent how to write TailwindCSS: utility classes in markup, mobile-first breakpoints, dark mode through the dark: variant.
npx skills add Mindrally/skills --skill tailwindcss -a claude-codeWhat tailwindcss does
This skill makes the agent treat TailwindCSS as the default styling layer. Classes go straight into HTML or JSX, the @apply directive stays out of production, and spacing plus colour come from the framework scales instead of arbitrary values. Responsive work starts at the small screen and moves up through the sm:, md:, lg:, xl: and 2xl: prefixes.
Repeated class sets get pulled into a component rather than copied across files. There are integration notes for React and Next.js, including the cn() helper for conditional classes and pairing with Shadcn UI and Radix UI. Vue projects apply classes in the template with :class binding, Alpine.js uses x-bind:class.
The no-@apply-in-production rule is the sharp edge here. If your stylesheets lean on @apply layers, the agent will push code the other way, so it is worth checking before you install. Custom themes belong in the Tailwind config, not in one-off class edits.
What it helps with
- lay out a responsive grid across breakpoints without hand-written media queries
- add dark mode with the dark: variant
- extract repeated class sets into a component
- wire conditional classes in React through cn()
- build a layout from flex and grid utilities
Example prompts for the agent
- Build this product card with Tailwind, mobile first, then md: and lg:
- Rewrite these styles from @apply to utility classes inside the JSX
- Add dark mode to this block with dark: and check the contrast
How to install tailwindcss
1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill tailwindcss -a claude-code2Manually: put the files in place
~/.claude/skills/tailwindcss/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/tailwindcss/
1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill tailwindcss -a codex2Manually: put the files in place
.agents/skills/tailwindcss/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill tailwindcss -a cursor2Manually: put the files in place
.cursor/skills/tailwindcss/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Mindrally/skills tailwindcss2Manually: put the files in place
.github/skills/tailwindcss/SKILL.md1Skills CLI (Vercel)
npx skills add Mindrally/skills --skill tailwindcss -a gemini-cli2Platform CLI
gemini skills install https://github.com/Mindrally/skills --path tailwindcssManually: put the files in place
.devin/skills/tailwindcss/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Mindrally/skills --skill tailwindcss -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about tailwindcss
How do I install tailwindcss in Claude?
Run npx skills add Mindrally/skills --skill tailwindcss -a claude-code. The skill file lands at ~/.claude/skills/tailwindcss/SKILL.md.
What does the tailwindcss skill do?
It gives the agent a set of TailwindCSS rules: utility classes in markup, mobile-first design, spacing and typography from the framework scales, dark mode via dark:.
Why does the skill avoid @apply?
Its rules keep @apply out of production, so styles stay utility-first inside the template. On a project built around @apply layers the agent will write against your existing code.
Source text
SKILL.md · Apache-2.0
--- name: tailwindcss description: Expert in TailwindCSS utility-first styling with responsive design patterns metadata: maintainer: Mindrally source: https://github.com/Mindrally/skills --- # TailwindCSS You are an expert in TailwindCSS utility-first CSS framework with deep knowledge of responsive design and component styling. ## Core Principles - Use Tailwind utility classes extensively in your templates - Never use @apply directive in production - Follow utility-first approach for all styling - Use responsive design with a mobile-first approach ## Usage Guidelines - Apply Tailwind classes directly in HTML/JSX - Leverage Tailwind's built-in responsive prefixes (sm:, md:, lg:, xl:, 2xl:) - Use Tailwind's color palette and spacing scale consistently - Implement dark mode using Tailwind's dark: variant ## Component Styling - Use consistent spacing using Tailwind's spacing scale - Apply consistent typography using Tailwind's font utilities - Leverage flexbox and grid utilities for layouts - Use Tailwind's transition utilities for animations ## Best Practices - Group related utilities logically - Use component extraction for repeated patterns - Leverage Tailwind's configuration for custom themes - Use JIT mode for optimal performance ## Integration Patterns ### With React/Next.js - Use className prop for applying Tailwind classes - Leverage cn() utility for conditional classes - Integrate with Shadcn UI and Radix UI components ### With Vue - Apply Tailwind classes in template sections - Use :class binding for conditional styling ### With Alpine.js - Combine with x-bind:class for reactive styling ## Responsive Design - Design mobile-first, then add larger breakpoint styles - Use container class for consistent max-widths - Leverage responsive variants for all utilities - Test across multiple screen sizes
© Mindrally · Apache-2.0 · Mindrally/skills
Similar skills
Everything for Frontend and UI →tailwindcss by other authors comes first.