Skip to content

Commit 885aa0f

Browse files
committed
Remove redundant Tailwind CSS guidelines and update skill description
When we first added skill support, skill triggering wasn't reliable enough, so we added a core.blade.php guideline that duplicated instructions already in the Tailwind CSS skill — things like always use search-docs and activate tailwindcss-development for Tailwind tasks. This burned extra context tokens on every request. We now have an eval system for testing and improving skill descriptions, so they trigger reliably. This means the redundant guideline file is no longer needed. Approach - Remove the redundant core.blade.php guideline that duplicated the Tailwind CSS skill's own instructions - Refine the skill description to be more specific about Tailwind CSS scoping, validated through trigger evals
1 parent 81e0ed4 commit 885aa0f

File tree

3 files changed

+3
-8
lines changed

3 files changed

+3
-8
lines changed

.ai/tailwindcss/3/skill/tailwindcss-development/SKILL.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
name: tailwindcss-development
3-
description: "Styles applications using Tailwind CSS v3 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes."
3+
description: "Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS."
44
license: MIT
55
metadata:
66
author: laravel
@@ -18,7 +18,7 @@ Activate this skill when:
1818

1919
## Documentation
2020

21-
Use `search-docs` for detailed Tailwind CSS v3 patterns and documentation.
21+
Use `search-docs` for detailed Tailwind CSS v3 patterns and documentation to get the correct classes for utilities.
2222

2323
## Basic Usage
2424

.ai/tailwindcss/4/skill/tailwindcss-development/SKILL.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
name: tailwindcss-development
3-
description: "Styles applications using Tailwind CSS v4 utilities. Activates when adding styles, restyling components, working with gradients, spacing, layout, flex, grid, responsive design, dark mode, colors, typography, or borders; or when the user mentions CSS, styling, classes, Tailwind, restyle, hero section, cards, buttons, or any visual/UI changes."
3+
description: "Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS."
44
license: MIT
55
metadata:
66
author: laravel

.ai/tailwindcss/core.blade.php

Lines changed: 0 additions & 5 deletions
This file was deleted.

0 commit comments

Comments
 (0)