cva-best-practices

Build and review typed component variants with cva. Use when defining cva components, exposing variant props, composing styles, handling class conflicts, or generating variant galleries. For version upgrades, use migration guidance instead.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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 lean, technical, and actionable with a concrete code example and a verification checkpoint, organized into well-headed sections that link out to authoritative docs. Main weaknesses are the version pin and a few sections that stay at the prose-directive level rather than giving executable snippets.

Suggestions

Move the 'verified against cva@1.0.0-beta.12' version pin into a dedicated 'Version / migration' or deprecated-style note so time-sensitive info does not penalize conciseness.

Add a second short executable snippet under 'Keep props inferred' showing the VariantProps + native-prop combining pattern, since that section is currently prose-only.

Consider extracting the three Tailwind conflict strategies ('cn', 'cva/tailwindcss', 'tailwind-merge') into a reference file, keeping only the recommended default inline to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Dense and assumes programming competence without padding, but pins a time-sensitive version ('verified against cva@1.0.0-beta.12') outside a deprecated/old-patterns section, which the guideline penalizes.	4 / 5
Actionability	Provides concrete imports, API names, and one complete executable code block (the twMerge defineConfig example), with mostly executable guidance; a few sections remain prose directives rather than copy-paste snippets.	4 / 5
Workflow Clarity	A logical topical sequence (check package → define variants → infer props → join classes → compose → galleries) with an explicit verify step at the end ('Verify changed class outputs against the installed package and type-check consuming components').	4 / 5
Progressive Disclosure	Well-organized into clearly headed sections, each closing with clearly signaled one-level-deep external doc links; no bundle files exist to evaluate further, and structure is good with only minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

92%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 concise, third-person, and clearly answers both what the skill does and when to use it, with concrete cva-specific trigger phrases and helpful boundary guidance. It is a strong, well-targeted description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Build and review typed component variants', 'defining cva components', 'exposing variant props', 'composing styles', 'handling class conflicts', 'generating variant galleries' — giving comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both 'what' (Build and review typed component variants with cva) and 'when' ('Use when defining cva components, exposing variant props...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('cva components', 'variant props', 'composing styles', 'class conflicts', 'variant galleries') that users would plausibly say, though a few synonymous phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	A clear cva-specific niche with distinct triggers and explicit boundary guidance ('For version upgrades, use migration guidance instead'), keeping conflict risk minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: joe-bell/cva
Path: skills/cva-best-practices/SKILL.md
Commit: 638844f

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.