CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A dense, highly actionable Vite reference with executable code throughout and well-signaled sections. Its main limitation is that all content is inlined in one large file with no progressive disclosure to supporting bundle files.

Suggestions

Move the bulky reference tables (Essential Plugins, Key Config Options) and per-topic deep dives into files under references/ and link to them from SKILL.md to improve progressive disclosure.

Tighten the "How It Works" explanatory sentences to the Vite-specific mechanics that Claude would not already infer, trimming general dev-server/bundler rationale.

Consider splitting the Common Pitfalls and Anti-Patterns blocks into a dedicated reference file, keeping SKILL.md as a concise overview with a Quick Reference index.

DimensionReasoningScore

Conciseness

The body is largely lean and code-forward with no basic-concept padding, but sections like "How It Works" include explanatory sentences ("Transforms happen on-demand per module request, which is why cold starts are fast") that could be trimmed, placing it just below a 5.

4 / 5

Actionability

Provides copy-paste-ready TypeScript across config, plugin authoring, HMR, proxy, manualChunks, optimizeDeps, SSR externals, and library mode, covering the common cases fully executably.

5 / 5

Workflow Clarity

As a patterns catalog it has no single destructive/batch workflow to cap, and it includes clear sequenced procedures with checkpoints (e.g., the `vite --profile` -> Speedscope flow and "verify with `vite build && vite preview` before deploying"), but it is not a tightly sequenced validated workflow throughout.

4 / 5

Progressive Disclosure

Well-organized with clear headers, tables, a Quick Reference index, and Related Skills, but all ~440 lines live in a single monolithic SKILL.md with no bundle files or offloaded reference materials, so it stops short of the one-level-deep reference structure of a 5.

4 / 5

Total

17

/

20

Passed

Description

87%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, comprehensive description that explicitly pairs a detailed what-with-a-when trigger clause. It is held just below perfect only because the capability list reads as topic nouns rather than concrete actions and the trigger omits a few natural synonyms.

DimensionReasoningScore

Specificity

Lists nine specific Vite domains ("config, plugins, HMR, env variables, proxy setup, SSR, library mode, dependency pre-bundling, and build optimization"), giving comprehensive coverage, but they are framed as topic areas rather than concrete verb-action phrases, keeping it just below a 5.

4 / 5

Completeness

It explicitly states both what ("Vite build tool patterns including...") and when ("Activate when working with vite.config.ts, Vite plugins, or Vite-based projects.") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

The "Activate when working with vite.config.ts, Vite plugins, or Vite-based projects" clause includes the natural config filename and plugin trigger, but omits common synonyms a user might say (e.g., dev server, HMR, bundler), so it sits above the 3 anchor but short of comprehensive 5 coverage.

4 / 5

Distinctiveness Conflict Risk

Vite-specific triggers (vite.config.ts, Vite plugins) carve a clear niche with minimal conflict risk against adjacent skills like nextjs-turbopack or frontend-patterns.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.