tailwind-enforcement

Enforce Tailwind CSS classes over inline styles in HTML and template files.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/youhei-ushio/dotclaude-public --skill tailwind-enforcement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-enforcement
Source: https://github.com/youhei-ushio/dotclaude-public/tree/main/skills/global/tailwind-enforcement
Command: npx skills add https://github.com/youhei-ushio/dotclaude-public --skill tailwind-enforcement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures that developers adhere to Tailwind CSS conventions, maintaining design consistency and reducing maintenance overhead.

Core Features & Use Cases

  • Enforce Class Usage: Prompts developers to use Tailwind CSS classes instead of inline styles.
  • Dynamic Style Handling: Allows exceptions for dynamic color values and complex styles.
  • Applicability: Suitable for any project using HTML, templates, JSX, Vue SFC, Blade, or Livewire components.

Quick Start

Run the tailwind-enforcement skill before saving your code to ensure Tailwind CSS best practices are followed.

Frequently Asked Questions about tailwind-enforcement

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

FAQPage Schema
How do I enforce Tailwind CSS classes instead of inline styles in my project?

To enforce Tailwind CSS classes, you can run a check before saving code that prompts developers to replace inline styles with utility classes, ensuring consistent UI styling and reduced maintenance overhead.

Does the Tailwind CSS style enforcement work with Vue and Blade templates?

Yes, Tailwind CSS style enforcement works with Vue and Blade templates, as well as HTML, JSX, and Livewire components, scanning local files to ensure styling conventions are followed across mixed web frameworks.

What is the best way to handle dynamic inline styles when enforcing Tailwind CSS?

The best way to handle dynamic inline styles is to allow exceptions for dynamic color values and complex styles, ensuring the enforcement check does not block necessary runtime-driven styling while still promoting static utility class usage.

Do I need additional dependencies to check Tailwind CSS usage in my files?

No, you do not need additional dependencies to check Tailwind CSS usage, as the enforcement process operates directly on the local file system without requiring extra packages or complex configurations.

Why should I remove inline styles and use Tailwind CSS utility classes instead?

You should remove inline styles and use Tailwind CSS utility classes to maintain design consistency across your project, reduce maintenance overhead, and ensure that all UI components follow a unified styling approach.

When should I not use Tailwind CSS utility classes for styling?

You should not use Tailwind CSS utility classes when dealing with complex dynamic values that cannot be predefined, such as runtime-calculated colors, which require inline style exceptions to function correctly.