tailwind-best-practices

Enforce Tailwind CSS token usage and styling conventions for Mastra Playground UI.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/sutin1234/tanstack-start-agent-skills --skill tailwind-best-practices-sutin1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-best-practices
Source: https://github.com/sutin1234/tanstack-start-agent-skills/tree/main/.agents/skills/tailwind-best-practices
Command: npx skills add https://github.com/sutin1234/tanstack-start-agent-skills --skill tailwind-best-practices-sutin1234

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Tailwind best-practices provide a centralized, enforceable guide to prevent styling drift and ensure consistent visuals across Mastra Playground UI. It helps teams align on token usage, component styling patterns, and design-token compliance, reducing rework and visual inconsistencies.

Core Features & Use Cases

  • Token-based styling guidelines to prevent drift across components and pages.
  • No arbitrary values and no overriding DS components, with defined exceptions.
  • Central references and examples to accelerate compliant implementation.

Quick Start

Review the tailwind-best-practices reference when styling components in packages/playground-ui and packages/playground.

Frequently Asked Questions about tailwind-best-practices

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

FAQPage Schema
How do I maintain design system consistency when writing Tailwind CSS?

Maintain Tailwind CSS design system consistency by enforcing token-based styling, avoiding arbitrary values, and restricting className overrides to prevent visual drift. Use centralized references to codify color and spacing conventions for scalable UI implementation.

What are the best practices for preventing styling drift in Tailwind components?

Preventing styling drift in Tailwind components requires applying design-token compliance, avoiding arbitrary value overrides, and restricting modifications to design system components. Centralized references support automated checks to ensure consistent styling patterns.

Can I use arbitrary values for spacing and colors in Tailwind design systems?

No, using arbitrary values for spacing and colors in Tailwind design systems is restricted to ensure visual consistency. The guidelines enforce token-based styling conventions and define specific exceptions to prevent drift across components and pages.

How do I refactor Tailwind CSS to align with design token conventions?

Refactor Tailwind CSS by replacing hardcoded arbitrary values with defined design tokens for colors and spacing. Review the centralized references to apply compliant component styling patterns and ensure restricted className overrides during the process.

Does this Tailwind best practices guide work for reviewing UI component code?

Yes, this Tailwind best practices guide works for reviewing UI component code by applying token usage checks and color conventions. It supports automated checks and scalable implementation when writing or refactoring styling code in packages.