CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tailwind-css-patterns

Comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/04-develop/01-ui-skills-dot-com/tailwind-css-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

46%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 delivers abundant concrete, executable Tailwind examples, but fails on token efficiency and structure: roughly two-thirds of it re-teaches utilities Claude already knows, and everything is crammed into one 800-line file with no progressive disclosure. A handful of examples also use deprecated or non-existent classes, slightly undercutting the otherwise strong actionability.

Suggestions

Cut or drastically compress sections covering basics Claude already knows (Spacing, Typography, Colors, Interactive States, basic flex/grid) and retain only the genuinely non-obvious v4.1+ material (@theme, @utility, container queries, CSS-first config, @tailwindcss/vite integration).

Split the body into one-level-deep reference files (e.g., references/components.md, references/configuration.md, references/accessibility.md) and keep SKILL.md as a concise overview with clearly signaled links, instead of inlining ~800 lines.

Fix inaccurate or deprecated guidance — remove `content-visibility-auto`/`contain-layout` (not real Tailwind classes), replace `bg-opacity-50` with the v4 `bg-blue-500/50` syntax, drop `jit: true` — and move all version-specific/legacy patterns into a clearly marked deprecated section so version drift doesn't mislead.

DimensionReasoningScore

Conciseness

The ~800-line body extensively documents basics Claude already knows — `p-4`/`m-4` padding, `flex items-center justify-between`, hover/focus states, `text-4xl font-bold` — with whole sections (Spacing, Typography, Colors, Interactive States) that add no new knowledge, matching anchor 2's 'several unnecessary explanations or padded sections'. Only the v4.1-specific material (@theme, @utility, container queries, @tailwindcss/vite) genuinely earns its tokens, and version-sensitive details (v4.1, `bg-opacity-50`, `jit: true`) are scattered outside any deprecated/legacy framing except the one config section.

2 / 5

Actionability

Most guidance is concrete, copy-paste-ready code: complete card, navbar, form, modal, and React Button component examples with real utility classes. It drops below anchor 5 because some examples are not executable/accurate — `content-visibility-auto` and `contain-layout` are not real Tailwind classes (the CSS section defines `@utility content-auto` instead, a mismatch), `bg-opacity-50` is deprecated in v4, and `jit: true` is not a valid modern config key.

4 / 5

Workflow Clarity

As a pattern catalog there is no multi-step workflow to sequence, and the 'When to Use' section plus task-organized sections give adequate navigation, but there are no validation checkpoints or decision guidance (e.g., which configuration approach to choose when, or how to verify output) beyond a bare numbered Best Practices list. This matches anchor 3: structure present but checkpoints/guidance implicit rather than explicit.

3 / 5

Progressive Disclosure

The skill is a monolithic ~800-line SKILL.md with no bundle files at all; large chunks that clearly belong in separate references (component patterns, configuration reference, accessibility guidance) are fully inlined, which is the core failure of anchor 2. Section headers are good (above 'minimal structure'), but with zero one-level-deep references and everything inline, it cannot reach anchor 3's 'references present' or anchor 4's 'appropriately placed' bar.

2 / 5

Total

11

/

20

Passed

Description

83%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.

A strong description with an explicit 'Use when...' trigger clause, clear niche scoping to Tailwind CSS, and a specific enumeration of covered areas. Its main weaknesses are buzzword padding ('Comprehensive', 'modern CSS best practices') and a few missing natural trigger terms like dark mode and mobile-first.

DimensionReasoningScore

Specificity

The description enumerates several specific coverage areas — "responsive design, layout utilities, flexbox, grid, spacing, typography, colors" — going well beyond naming the domain, though these are topic nouns rather than concrete action verbs and are padded with buzzwords ("Comprehensive", "modern CSS best practices"). It sits above anchor 3 (only 1-2 concrete items) but the buzzword padding and missing areas (dark mode, animations) keep it below anchor 5.

4 / 5

Completeness

It explicitly answers both questions: the "what" is stated concretely ("Tailwind CSS utility-first styling patterns including..." with a specific topic list) and the "when" is an explicit "Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow" clause with concrete trigger phrases, matching the anchor 5 example pattern.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "Tailwind CSS", "responsive design", "flexbox", "grid", "styling React/Vue/Svelte components", "design systems" — terms users would naturally say. A few common variations are missing (e.g., "dark mode", "utility classes" beyond "utility-first", "mobile-first"), so it falls short of the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"Tailwind CSS" is a clear, distinctive niche trigger unlikely to fire for unrelated skills. However, the broad tail phrases "modern CSS best practices" and "optimizing CSS workflow" create minor overlap risk with generic CSS/design-system skills, keeping it just below the minimal-conflict anchor 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (814 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/tailwind-css-patterns/SKILL.md

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.