vue-patterns

Vue.js 3 Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns. Activates for Vue, Nuxt, Vite, or Pinia projects. Use when building or reviewing Vue 3, Nuxt, or Pinia code — Composition API, reactivity, or router navigation.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

72%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 highly actionable, well-structured Vue patterns reference with executable examples throughout. Its main weaknesses are the absence of a procedural workflow with validation checkpoints and a lack of progressive disclosure into separate bundle files for a skill this large.

Suggestions

Split large topical blocks (Nuxt patterns, testing, performance) into reference files under ./references/ and link to them from the body so SKILL.md stays a concise overview.

For state-management and routing sections that involve multi-step decisions, add an explicit sequenced workflow (e.g., choose pattern → implement → verify reactivity) with a validation checkpoint.

Trim concept-level rationale Claude already knows (mixins vs composables, basic one-way data flow) and de-duplicate the reactive-props-destructure guidance between section 10 and the Anti-Patterns table.

Dimension	Reasoning	Score
Conciseness	Mostly lean — dense tables and executable code blocks — with minor over-explanation of concepts Claude already knows (e.g., the mixins-vs-composables rationale and "Never mutate props — emit events instead") and some redundancy between the Vue 3.5 section and the Anti-Patterns table.	4 / 5
Actionability	Provides copy-paste-ready, executable examples across the common cases — Pinia setup store, composable, router guards, component tests, Nuxt useAsyncData — with specific, complete code rather than pseudocode.	5 / 5
Workflow Clarity	This is a patterns reference rather than a procedural workflow; numbered sections and "When to Use What" decision tables give structure, but there is no sequenced multi-step process with validation checkpoints for the user to follow.	3 / 5
Progressive Disclosure	Good section/header organization exists, but the 466-line body inlines substantial content (Nuxt patterns, testing, performance) that could live in separate reference files, and no bundle references are signaled — only a Related Skills cross-link.	3 / 5
	Total	15 / 20 Passed

Description

88%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, specific description that answers both what and when with concrete trigger terms and largely third-person voice. Minor room to add file-extension/alias triggers (.vue, SFC) and tighten the slight overlap with frontend-patterns.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — "Composition API patterns, component architecture, reactivity best practices, Pinia state management, Vue Router navigation, and Nuxt SSR patterns" — giving comprehensive, specific coverage rather than vague claims.	5 / 5
Completeness	Explicitly answers both what (the enumerated pattern areas) and when ("Activates for Vue, Nuxt, Vite, or Pinia projects. Use when building or reviewing Vue 3, Nuxt, or Pinia code …") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong natural keyword coverage (Vue, Nuxt, Vite, Pinia, Vue 3) with synonyms, but omits common variations a user might say such as ".vue files", "single-file components", or "SFC" that appear only in the body.	4 / 5
Distinctiveness Conflict Risk	The Vue/Nuxt/Vite/Pinia niche is clearly distinct from most skills, with only minor overlap risk against a general frontend-patterns skill noted in Related Skills.	4 / 5
	Total	18 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/vue-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.