tailwind

Audit Tailwind CSS codebases for spacing, sizing, and responsive anti-patterns.

1|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/ruchernchong/claude-kit --skill tailwind-ruchernchong
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tailwind
Source: https://github.com/ruchernchong/claude-kit/tree/main/skills/tailwind
Command: npx skills add https://github.com/ruchernchong/claude-kit --skill tailwind-ruchernchong

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tailwind projects often drift into anti-patterns that reduce consistency and increase maintenance costs. This Skill audits Tailwind usage to enforce spacing direction, size-* usage, gap preference, and 8px grid alignment.

Core Features & Use Cases

  • Enforces bottom-only spacing by discouraging mt-* and pt-* in favor of mb-* and pb-* or gap utilities.
  • Encourages use of size-* for equal width/height and promotes using h-* / w-* only when dimensions differ.
  • Guides mobile-first responsive design and consistent 8px grid across components.

Use Case: A frontend team standardizes Tailwind usage across a large React/Next.js/Vue project to ensure predictable spacing and sizing.

Quick Start

Run the Tailwind audit against your codebase to identify anti-patterns and apply fixes according to the rules above.

Frequently Asked Questions about tailwind

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit Tailwind CSS for inconsistent spacing and sizing?▼

To audit Tailwind CSS for inconsistent spacing and sizing, run an audit against your codebase to identify anti-patterns, enforcing bottom-only spacing, size-* usage, gap preferences, and 8px grid alignment for improved consistency and maintainability.

What are common Tailwind CSS anti-patterns for spacing and responsive design?▼

Common Tailwind CSS anti-patterns include using mt-* and pt-* instead of bottom-only mb-* or pb-* spacing, misusing h-* and w-* when size-* is preferred, and neglecting mobile-first responsive design and 8px grid alignment across components.

Does this Tailwind CSS lint workflow work with React, Vue, and Next.js projects?▼

Yes, this Tailwind CSS lint workflow is applicable to frontend projects built with React, Vue, and Next.js, guiding teams to standardize spacing direction, sizing utilities, and mobile-first responsive rules across the entire codebase.

How do I enforce a consistent 8px grid and mobile-first design in Tailwind?▼

Enforce a consistent 8px grid and mobile-first design in Tailwind by auditing your codebase to identify rule violations, guiding developers to apply standardized spacing, sizing utilities, and responsive prefixes correctly across all components.

When should I use size-* versus h-* and w-* utilities in Tailwind CSS?▼

Use size-* utilities in Tailwind CSS when an element requires equal width and height, and reserve h-* and w-* utilities only when the dimensional values differ, ensuring consistent sizing practices and reducing codebase maintenance overhead.