Skip to content
TrustedSkillsbeta
Back to all skills

Busirocket Tailwindcss V4

Listed
busirocket·vlatest·frontend

Generates Tailwind CSS v4 code snippets for rapid prototyping and development, boosting frontend efficiency.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add busirocket/agents-skills --skill busirocket-tailwindcss-v4 -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

busirocket

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    SKILL.md frontmatter is missing description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned busirocket/agents-skills at d5e3054ad2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
5 files, 296 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides guidance and code examples for setting up and maintaining Tailwind CSS v4 projects, focusing on best practices. It helps agents understand how to structure styles, choose between Tailwind utilities and custom CSS, and avoid common pitfalls like style drift. The skill offers specific rules and patterns to improve frontend efficiency and consistency when using Tailwind CSS v4.

When to use it

  • Setting up a new Tailwind CSS v4 project.
  • Writing component styles using Tailwind utilities.
  • Deciding whether to use Tailwind utilities or custom CSS for styling.
  • Maintaining consistent styling across your project and avoiding "style drift."

Key capabilities

  • Provides guidance on setting up Tailwind CSS v4 with a single global CSS import (tailwind-setup).
  • Offers strategies for preferring Tailwind utilities and extracting components when class strings become difficult to read (tailwind-class-strategy).
  • Explains how to avoid style drift by keeping custom CSS truly global (resets, tokens) and favoring consistent tokens (tailwind-avoid-drift).
  • Details the importance of CSS import order (tailwind-css-ordering).

Example prompts

  • "How do I set up Tailwind CSS v4 in my project?"
  • "What's the best way to handle component styling with Tailwind utilities?"
  • "I have a long and complex class string. What should I do?"

Tips & gotchas

  • The skill provides detailed explanations and code examples within individual rule files (e.g., rules/tailwind-setup.md). Refer to these files for specific guidance.
  • Prioritize Tailwind utilities in your className whenever possible.
  • Avoid large custom CSS files; use them primarily for global resets or tokens.