tailwind-patterns
Quick reference for Tailwind CSS utility patterns, responsive design, and configuration. Triggers on: tailwind, utility classes, responsive design, tailwind config, dark mode css, tw classes.
92
91%
Does it follow best practices?
Impact
89%
1.56xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid description with explicit trigger terms and a clear domain focus on Tailwind CSS. Its main weakness is that the 'what' portion is somewhat high-level ('quick reference for... utility patterns, responsive design, and configuration') rather than listing specific concrete actions the skill performs. Overall it performs well for skill selection purposes.
Suggestions
Add more specific concrete actions, e.g., 'Provides class syntax for layouts, spacing, typography, colors, and dark mode. Helps configure tailwind.config.js with custom themes and plugins.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Tailwind CSS) and mentions some areas like 'utility patterns, responsive design, and configuration,' but doesn't list specific concrete actions (e.g., 'apply flex layouts,' 'configure custom themes,' 'set up dark mode toggles'). | 2 / 3 |
Completeness | Answers both 'what' (quick reference for Tailwind CSS utility patterns, responsive design, and configuration) and 'when' (explicit 'Triggers on:' clause listing specific trigger terms). | 3 / 3 |
Trigger Term Quality | Includes a good set of natural trigger terms: 'tailwind', 'utility classes', 'responsive design', 'tailwind config', 'dark mode css', 'tw classes' — these cover common variations a user would naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Tailwind CSS specifically, with distinct triggers like 'tailwind config', 'tw classes', and 'utility classes' that are unlikely to conflict with general CSS or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted quick-reference skill that is concise, actionable, and well-organized. It provides copy-paste ready HTML examples for all common Tailwind patterns without over-explaining concepts Claude already knows. The only minor weakness is the reference to a bundle file that doesn't exist in the provided bundle, slightly undermining progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and reference-style. No unnecessary explanations of what Tailwind is or how CSS works. Tables and code snippets are compact and every token earns its place. | 3 / 3 |
Actionability | All examples are copy-paste ready HTML/JS snippets with real Tailwind classes. The responsive breakpoints table, layout patterns, card, button, form input, and dark mode config are all directly executable. | 3 / 3 |
Workflow Clarity | This is a single-purpose reference skill, not a multi-step workflow. The content is clearly organized into logical sections (breakpoints, layouts, components, modifiers, spacing) making it unambiguous to follow. | 3 / 3 |
Progressive Disclosure | The skill references `./references/component-patterns.md` for additional patterns, which is good one-level-deep disclosure. However, no bundle files were provided, so the reference path cannot be verified, and the main content could benefit from slightly clearer navigation signaling between quick-reference sections and the deeper resource. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
3ae408c
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.