nuxt4-patterns

Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.

Quality

85%

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

87%

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

A lean, actionable Nuxt 4 pattern reference with executable code and clean section organization; its only weak spot is workflow clarity, since it is a pattern catalogue rather than a sequenced workflow with validation feedback loops.

Suggestions

Add a short ordered debugging workflow for hydration mismatches (e.g. reproduce -> compare SSR vs client markup -> isolate browser-only logic -> verify with the checklist) with an explicit validate/retry loop to lift workflow clarity.

Optionally split the Route Rules or Data Fetching reference tables into a referenced file if the skill grows, to keep the overview scannable.

Dimension	Reasoning	Score
Conciseness	Lean bullet-oriented guidance that assumes Claude's Nuxt competence and avoids explaining basic concepts; every section adds non-obvious pattern guidance, matching the 'lean and efficient' anchor of 3 rather than the padded prose of a 2.	3 / 3
Actionability	Provides concrete, copy-paste-ready code for useAsyncData/useFetch, routeRules in nuxt.config.ts, and Lazy component usage with v-if/hydrate-on-visible, matching the 'fully executable code/commands' anchor of 3.	3 / 3
Workflow Clarity	This is a pattern reference rather than a sequenced multi-step workflow; a Review Checklist provides some checkpoints, but there are no explicit validation/feedback loops for error recovery, so it sits at the 'checkpoints missing or implicit' anchor of 2 rather than the full workflow anchor of 3.	2 / 3
Progressive Disclosure	A self-contained single SKILL.md with no bundle files, organized into clearly navigable sections (When to Activate, Hydration Safety, Data Fetching, Route Rules, Lazy Loading, Review Checklist) and no nested references, matching the well-organized-sections anchor of 3.	3 / 3
	Total	11 / 12 Passed

Description

82%

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 specific, well-keyworded description with a clear Nuxt 4 niche, but it omits an explicit 'Use when' trigger clause, which caps completeness at 2.

Suggestions

Append an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when building or debugging Nuxt 4 SSR apps with hydration mismatches, route rules, or useFetch/useAsyncData data fetching.'

Consider adding user-facing phrasing variants (e.g. 'Nuxt hydration errors', 'Nuxt route rules') to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names multiple concrete capability areas — 'hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData' — matching the 'lists multiple specific concrete actions' anchor rather than the partial coverage of a 2.	3 / 3
Completeness	It clearly states what the skill covers but has no 'Use when...' clause or equivalent explicit trigger guidance; per the rubric guideline a missing explicit trigger caps completeness at 2, so it does not reach the explicit what-and-when anchor of 3.	2 / 3
Trigger Term Quality	Uses natural terms a Nuxt developer would actually say ('useFetch', 'useAsyncData', 'route rules', 'lazy loading', 'hydration', 'SSR-safe'), giving good coverage rather than the sparse keyword set of a 2.	3 / 3
Distinctiveness Conflict Risk	The Nuxt 4 niche plus distinctive triggers (useFetch/useAsyncData, route rules, hydration) make it unlikely to fire for an unrelated skill, matching the clear-niche anchor of 3 rather than the overlapping-skill risk of a 2.	3 / 3
	Total	11 / 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: 3 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.