tailwind-design-system

Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

Executable and well-structured, with a complete v4 config and migration table, but the inline Quick Start is heavier than necessary and one of two reference files is orphaned with no navigation pointing to it.

Suggestions

Add a clearly signaled link to references/advanced-patterns.md (e.g., an "Advanced patterns" section) so both bundle files are discoverable.

Trim the Quick Start @theme block — show a representative subset of tokens and a single animation, then point to references for the full set, to reduce duplicated light/dark token bulk.

Optionally move the full dark-mode token overrides into a reference file, keeping the body's dark-mode example minimal.

Dimension	Reasoning	Score
Conciseness	Prose is lean and assumes competence, but the Quick Start embeds a large full @theme block — including a ~25-line dark-mode token set duplicating light-mode tokens and four keyframes — that is more than an overview needs and could be tightened.	2 / 3
Actionability	The @theme CSS block, @custom-variant dark-mode directive, and v3→v4 migration table are concrete, executable, and copy-paste ready.	3 / 3
Workflow Clarity	This is a reference/config skill rather than a destructive multi-step workflow; its Quick Start → Core Concepts → references sequence is unambiguous, so it meets the simple-skill allowance for a top score.	3 / 3
Progressive Disclosure	details.md is signaled one level deep ("Read that file when the navigation tier above is insufficient"), but the second bundle file advanced-patterns.md is never referenced from the body, and the large inline Quick Start could partly live in references.	2 / 3
	Total	10 / 12 Passed

Description

100%

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: third-person, concise, with explicit what-and-when triggers tied to a well-scoped Tailwind v4 design-system niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "design tokens, component libraries, and responsive patterns" built with Tailwind CSS v4 — matching the anchor for listing several specific actions.	3 / 3
Completeness	Explicitly states what it does and follows with a "Use when creating component libraries, implementing design systems, or standardizing UI patterns" trigger clause, answering both what and when.	3 / 3
Trigger Term Quality	Natural terms users would say ("component libraries", "design systems", "UI patterns") are present and the Tailwind v4 qualifier sharpens them; coverage is good rather than exhaustive but clears the high anchor.	3 / 3
Distinctiveness Conflict Risk	The Tailwind CSS v4 + design-system niche with its specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: wshobson/agents
Commit: 5cc2549

Reviewed: 2 days 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.