Claude Skill

tailwind-css

Imported from paulrberg/agent-skills/skills/tailwind-css.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download PaulRBerg-agent-skills-skills_tailwind-css-47581b8.zip · 4 KB

Install

skills CLI npx skills add https://github.com/PaulRBerg/agent-skills/tree/main/skills/tailwind-css
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install paulrberg-agent-skills@llmmart
Git git clone https://github.com/PaulRBerg/agent-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole paulrberg/agent-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Tailwind CSS

Follow the installed Tailwind version and the repository's tokens, components, class-merging utility, CSS entrypoint, and nearby UI. They take precedence over this skill. Do not add packages, change integration, or migrate versions without a request and local need.

Routing

Do not apply v4 syntax to an older installation. Preserve responsive, interaction, accessible, and dark-mode behavior. Do not redesign beyond the request.

Completion

Define the intended visual and state change. Reuse local conventions. Keep classes statically discoverable.

If source registration or generated mappings change, run the real Tailwind build and confirm the expected utilities. Run required repository checks and inspect the changed states at one representative viewport for a small style edit. Broaden to narrow/wide viewports, themes, and interactions when responsive rules or shared styling changed. When markup is transformed by JavaScript or a component library, inspect the final DOM too. Textual class review alone is insufficient. Repeat checks only when subsequent edits affect their evidence.

Finish with ### 🎨 Tailwind — ✅ styling updated (or ### 🎨 Tailwind — 🔎 inspected, no files written) and code-check and rendered-inspection evidence. Use prose for one inspected state and a compact table for several. Add ### ⚠️ Remaining only when needed. Keep source UI copy and diagnostics undecorated.

Files (agent-skills)
  • agents
    • openai.yaml 42 B
      Loading…
  • references
    • coding-preferences.md 1.5 KB
      Loading…
    • eslint.md 400 B
      Loading…
    • tailwind-v4-rules.md 1.9 KB
      Loading…
    • tailwind-variants.md 1.2 KB
      Loading…
    • tw-animate-css.md 548 B
      Loading…
  • SKILL.md 2 KB
    ---
    name: tailwind-css
    user-invocable: false
    description:
      "Use for Tailwind v4 styling: add/fix classes, configure or migrate Tailwind, use tailwind-variants, or
      tw-animate-css."
    ---
    
    # Tailwind CSS
    
    Follow the installed Tailwind version and the repository's tokens, components, class-merging utility, CSS entrypoint,
    and nearby UI. They take precedence over this skill. Do not add packages, change integration, or migrate versions
    without a request and local need.
    
    ## Routing
    
    - Apply [coding preferences](references/coding-preferences.md) only where the project is silent.
    - For v4 configuration, migration, directives, or generated classes, use [v4 rules](references/tailwind-v4-rules.md) and
      the matching official docs.
    - Read [tailwind-variants](references/tailwind-variants.md), [tw-animate-css](references/tw-animate-css.md), or
      [ESLint](references/eslint.md) only when that integration exists locally or the request adds it.
    
    Do not apply v4 syntax to an older installation. Preserve responsive, interaction, accessible, and dark-mode behavior.
    Do not redesign beyond the request.
    
    ## Completion
    
    Define the intended visual and state change. Reuse local conventions. Keep classes statically discoverable.
    
    If source registration or generated mappings change, run the real Tailwind build and confirm the expected utilities. Run
    required repository checks and inspect the changed states at one representative viewport for a small style edit. Broaden
    to narrow/wide viewports, themes, and interactions when responsive rules or shared styling changed. When markup is
    transformed by JavaScript or a component library, inspect the final DOM too. Textual class review alone is insufficient.
    Repeat checks only when subsequent edits affect their evidence.
    
    Finish with `### 🎨 Tailwind — ✅ styling updated` (or `### 🎨 Tailwind — 🔎 inspected, no files written`) and
    code-check and rendered-inspection evidence. Use prose for one inspected state and a compact table for several. Add
    `### ⚠️ Remaining` only when needed. Keep source UI copy and diagnostics undecorated.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.