tailwind-best-practices

Enforce Tailwind CSS styling guidelines for the Mastra Playground UI.

2|1|Updated Sep 19, 2025
One-click install
npx skills add https://github.com/akashic-devkit/akashic-devkit --skill tailwind-best-practices-akashic-devkit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tailwind-best-practices
Source: https://github.com/akashic-devkit/akashic-devkit/tree/main/.agents/skills/tailwind-best-practices
Command: npx skills add https://github.com/akashic-devkit/akashic-devkit --skill tailwind-best-practices-akashic-devkit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces consistent styling with Tailwind CSS, preventing design drift and maintaining the integrity of the Mastra Playground UI's design system.

Core Features & Use Cases

  • Enforces Design Tokens: Ensures only approved design tokens are used for colors, spacing, etc.
  • Governs ClassName Usage: Restricts arbitrary Tailwind values and prevents overriding of design system component styles.
  • Use Case: When a developer is adding a new button component, this Skill can review the proposed Tailwind classes to ensure they adhere to the established design tokens and component usage guidelines, preventing visual inconsistencies.

Quick Start

Review the provided code snippet for adherence to Tailwind CSS best practices.

Frequently Asked Questions about tailwind-best-practices

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

FAQPage Schema
How do I enforce Tailwind CSS consistency across my UI components?

Tailwind CSS consistency is enforced by validating className usage and restricting arbitrary values, ensuring all components adhere to approved design tokens and preventing design drift across the UI.

What are the best practices for applying design tokens in Tailwind CSS?

Best practices for applying Tailwind CSS design tokens involve using only approved tokens for colors and spacing, and governing className usage to prevent overriding base component styles. This maintains visual integrity throughout the application.

How do I prevent design drift when adding new Tailwind components?

Preventing design drift when adding new Tailwind components requires reviewing proposed classes against established design tokens and component usage guidelines. This validation step stops visual inconsistencies before they enter the codebase.

Can I use arbitrary Tailwind values for custom spacing in a design system?

Using arbitrary Tailwind values for custom spacing is generally restricted within a strict design system. Governing className usage prevents these overrides, ensuring spacing adheres strictly to approved design tokens for visual consistency.

Does this Tailwind styling validation apply to all packages in the repository?

This Tailwind styling validation specifically applies to styling code within `packages/playground-ui` and `packages/playground`. It is triggered by tasks involving Tailwind classes, component styling, or design tokens in those packages.