tdg-personal/nuxt4-patterns
Nuxt 4 app patterns for hydration safety, performance, route rules, lazy loading, and SSR-safe data fetching with useFetch and useAsyncData.
73
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
54%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 has strong trigger terms and is highly distinctive for Nuxt 4 development, but it reads more like a topic list than an actionable skill description. It lacks a 'Use when...' clause and doesn't describe concrete actions the skill performs (e.g., 'generates', 'configures', 'reviews').
Suggestions
Add a 'Use when...' clause, e.g., 'Use when building or debugging Nuxt 4 apps, especially for SSR issues, hydration mismatches, or data fetching with useFetch/useAsyncData.'
Replace the topic-list style with concrete action verbs describing what the skill does, e.g., 'Guides implementation of SSR-safe data fetching, configures route rules, and resolves hydration mismatches in Nuxt 4 applications.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Nuxt 4) and several specific areas (hydration safety, performance, route rules, lazy loading, SSR-safe data fetching) with concrete API references (useFetch, useAsyncData), but these are more topic areas than concrete actions—it doesn't describe what it actually does (e.g., 'generates components', 'configures route rules'). | 2 / 3 |
Completeness | Describes the 'what' at a topic level but completely lacks any 'Use when...' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause should cap completeness at 2, and since the 'what' is also more topical than actionable, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes strong natural keywords a user would say: 'Nuxt 4', 'hydration', 'SSR', 'useFetch', 'useAsyncData', 'lazy loading', 'route rules', 'performance'. These cover a good range of terms developers would naturally use when seeking help with Nuxt 4 patterns. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of 'Nuxt 4' with specific APIs like useFetch and useAsyncData creates a clear niche that is unlikely to conflict with other skills. It's distinctly about Nuxt 4 SSR patterns rather than general Vue or web development. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted skill that delivers concise, actionable Nuxt 4 patterns with good code examples. Its main weakness is the lack of explicit validation/debugging workflows—particularly for hydration mismatches, which are notoriously hard to diagnose—and the absence of progressive disclosure through external references for deeper topics.
Suggestions
Add a brief debugging workflow for hydration mismatches (e.g., how to identify the mismatch in dev tools, fix, and verify the fix), which would improve workflow clarity.
Consider linking to separate reference files for advanced topics like custom lazy hydration strategies or complex route rule configurations to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It avoids explaining what Nuxt, SSR, or hydration are—concepts Claude already knows—and instead delivers specific, actionable rules. Every bullet point adds novel, non-obvious guidance (e.g., 'Do not use route.fullPath to drive SSR-rendered markup' with a clear reason). | 3 / 3 |
Actionability | The skill provides executable code examples for data fetching, route rules, and lazy loading patterns. The guidance is specific and copy-paste ready, with concrete composable names, option flags (lazy, server, pick), and template patterns rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The review checklist at the end provides some validation structure, and the sections are logically sequenced. However, there are no explicit validation/verification steps or feedback loops for debugging hydration mismatches or verifying route rule behavior—the skill describes what to do but not how to verify it worked or recover from errors. | 2 / 3 |
Progressive Disclosure | The content is well-organized into clear sections with good headers, but it's entirely self-contained with no references to external files for deeper dives. At ~100 lines it's manageable, but the route rules and data fetching sections could benefit from linking to more detailed reference material for edge cases. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents