vite-patterns

Vite build tool patterns including config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization. Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

92%

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

A high-quality, actionable Vite reference with executable examples, explicit verification checkpoints, and genuinely useful footguns rather than filler. Its main weakness is progressive disclosure: everything lives in one large SKILL.md with no detail files to defer to.

Suggestions

Split the bulky reference material — the Essential Plugins table, Anti-Patterns catalog, and Build Optimization/Performance sections — into separate files (e.g. references/plugins.md, references/anti-patterns.md) and link to them one level deep from a concise overview in SKILL.md.

Add a short 'Quick start' or 'Most common configs' block near the top that points to the deeper sections, so the overview reads as a navigation hub rather than a wall of detail.

Move the full plugin authoring and HMR API detail into a referenced file, keeping only the minimal inline example and a pointer, to reduce the surface a reader must scan before reaching the relevant pattern.

Dimension	Reasoning	Score
Conciseness	The body is lean for the breadth it covers: it assumes Claude's competence, avoids explaining what Vite or ESM are, and every section earns its place with non-obvious footguns and callouts (e.g. the type-check gap, the loadEnv('') trap) rather than padded background.	3 / 3
Actionability	It provides fully executable TypeScript config snippets, specific commands ('vite --profile', 'vite build && vite preview'), concrete defaults in tables, and copy-paste-ready plugin and proxy examples — matching the anchor for fully executable, specific guidance.	3 / 3
Workflow Clarity	Sequenced processes are clearly laid out — the profiling flow (start --profile, interact, press p+enter, load in Speedscope), the library-mode numbered footguns, and the explicit 'verify with vite build && vite preview before deploying' checkpoint — with a .gitignore checklist for complex setup.	3 / 3
Progressive Disclosure	The file is a single ~440-line monolith with no bundle files and only one external link; it is well-organized by headers but content that could live in separate references (the plugin table, anti-patterns, full examples) is inline rather than split into one-level-deep files.	2 / 3
	Total	11 / 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, third-person description that names concrete capability areas and pairs them with an explicit 'Activate when' trigger clause. It is concise yet comprehensive and clearly distinguishable from other build-tool skills.

Dimension	Reasoning	Score
Specificity	The description enumerates many concrete capability areas — 'config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization' — matching the anchor that lists multiple specific concrete actions rather than vague language.	3 / 3
Completeness	It answers both 'what' (the enumerated pattern areas) and 'when' via the explicit 'Activate when working with...' clause, satisfying the anchor for clearly answering both with explicit triggers.	3 / 3
Trigger Term Quality	Natural terms users would say appear in the trigger clause — 'vite.config.ts', 'Vite plugins', 'Vite-based projects' — giving good coverage of the phrasings a user reaches for when they need this skill.	3 / 3
Distinctiveness Conflict Risk	The skill is scoped to a clear niche — the Vite build tool and its config file — with distinct, Vite-specific triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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: affaan-m/ECC
Commit: 754b8dd

Reviewed: 4 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.