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.

1.56x

Quality

83%

Does it follow best practices?

Impact

89%

1.56x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an efficient, well-organized pattern catalog with concrete code examples and tables. Its main weakness is a broken reference to a non-existent './references/component-patterns.md' file and some illustrative code fragments rather than complete blocks.

Suggestions

Create './references/component-patterns.md' (or remove the dangling reference) so the 'Additional Resources' pointer resolves to real content.

Complete the layout-pattern and dark-mode code blocks (close tags, wrap in full elements) so snippets are fully copy-pasteable.

Add a one-line note per major section stating when to choose that pattern (e.g. flex vs grid) to nudge selection beyond pure lookup.

Dimension	Reasoning	Score
Conciseness	The body is lean tables and code snippets with almost no prose, assuming Claude's competence and explaining nothing about what Tailwind is; every section earns its place.	5 / 5
Actionability	Provides concrete, copy-paste-ready HTML for card, button, and form input plus value tables, but several layout and dark-mode snippets are illustrative fragments with unclosed tags rather than complete blocks.	4 / 5
Workflow Clarity	As a single-purpose reference skill, the single action (look up the relevant pattern) is unambiguous and the content is organized into clearly labeled sections; no destructive or batch operations require validation.	5 / 5
Progressive Disclosure	Well-structured with clear section headers and a one-level-deep, clearly signaled reference to './references/component-patterns.md', but that referenced file does not exist in the bundle, a navigation gap beyond a minor organization issue.	4 / 5
	Total	18 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is clear, third-person, and explicitly covers both what the skill provides and when to invoke it with concrete trigger phrases. It is slightly topic-oriented rather than action-oriented and has minor overlap risk with general CSS skills.

Dimension	Reasoning	Score
Specificity	Names the Tailwind domain plus a few specific areas ('utility patterns, responsive design, and configuration') but these are topics rather than concrete actions, leaving coverage incomplete.	3 / 5
Completeness	Explicitly states both what it does ('Quick reference for Tailwind CSS utility patterns, responsive design, and configuration') and when to use it via a concrete 'Triggers on:' clause.	5 / 5
Trigger Term Quality	'Triggers on: tailwind, utility classes, responsive design, tailwind config, dark mode css, tw classes' offers good natural keyword coverage including the 'tw' abbreviation, missing only a few synonyms.	4 / 5
Distinctiveness Conflict Risk	Tailwind-specific triggers ('tailwind config', 'tw classes') give it a clear niche with minimal conflict risk, though minor overlap with generic CSS/styling skills remains.	4 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: NeverSight/skills_feed
Path: data/skills-md/0xdarkmatter/claude-mods/tailwind-patterns/SKILL.md
Commit: 2f57aec

Reviewed: about 21 hours ago

Table of Contents

Discovery Implementation Validation

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.