nuxt
Use before changing Nuxt code. Routes to the smallest relevant guide for `useFetch`/`useAsyncData`, SSR and hydration, `definePageMeta`/`useSeoMeta`, `runtimeConfig`, Nitro server routes, plugins, errors, Nuxt UI, Nuxt Content, installed Nuxt modules, or module authoring.
How do I install this agent skill?
npx skills add https://nuxt-skill.onmax.me --skill nuxtIs this agent skill safe to install?
No partner audit is available yet. Read the source before installing.
What does this agent skill do?
Nuxt Skill Router
Decide what Nuxt owns before editing, then open the smallest relevant Nuxt, Vue, or module guide.
Loading rules
- Repository-global instructions and required workflows win first.
- Inspect the exact surface you are changing: page, layout, component, composable, server handler, plugin, config file, or module-owned file.
- If a generic Vue or raw HTML fix looks plausible, read Abstraction Disambiguation first. Most Nuxt mistakes are the right behavior built on the wrong primitive.
- Switch to Vue Best Practices only when Nuxt no longer owns the abstraction.
- Use module guides only for module-owned APIs, config, runtime behavior, and files.
Routing
Open one guide that matches the task. Open more only when that guide points you there or the task clearly crosses boundaries.
| Task shape or symptom | Example request | Open first |
|---|---|---|
Writing or refactoring a Nuxt module (defineNuxtModule, hooks, public APIs) | "Add a Nuxt module option, hook, or runtime extension" | Module Authoring Conventions |
| Tables, forms, modals, dropdowns, page shells, or other UI that Nuxt UI already ships | "This modal/table/dropdown was hand-built in raw HTML" | Nuxt UI Primitives |
| Nuxt Content collections, structured data records, or navigation built from content | "Build the docs sidebar from the content folder" | Content Modeling and Navigation |
| SSR, initial page load, route params, or data fetched for first render | "This page fetches twice on first load" | Data Fetching and SSR |
Hydration warnings, ClientOnly, browser-only APIs, time/randomness, or SSR/CSR mismatch | "Why do I get a hydration mismatch from Date.now()?" | Hydration and SSR Consistency |
| Page options, middleware, layout selection, title, meta tags, canonical URLs, or OG data | "Change canonical URL and OG tags" | Page Meta, Head, and Layout |
Global/local errors, clearError, showError, or recovery flows | "clearError is not behaving as expected" | Error Surfaces and Recovery |
nuxt.config.*, runtimeConfig, env wiring, or public/private config exposure | "Expose only the public runtimeConfig key" | Server Routes, h3 Patterns, and Runtime Config |
server/api/**, server/routes/**, defineEventHandler, route rules, caching, or Nitro plugins | "This server/api handler cache or route rule is wrong" | Nitro and h3 Server Patterns |
| Secrets, privileged API calls, request isolation, or server/client boundary confusion | "Should this secret live in runtime config or client code?" | Architecture Boundaries |
| Plugins, injections, app boot logic, or global runtime initialization | "Register a global helper when the app starts" | Plugins and Runtime Boot |
| Performance regressions, rendering strategy, lazy loading, or payload/bundle cost | "This page ships too much JavaScript" | Performance and Rendering |
| Upgrades, deprecations, compatibility fixes, or version-boundary work | "Upgrade this app from Nuxt 3 to Nuxt 4" | Migrations and Compatibility |
| The remaining work is components, composables, reactivity, props/emits, or SFC structure | "Split this component and keep the props typed" | Vue Best Practices |
Project-specific guidance
This hosted skill covers Nuxt itself. Module APIs (Nuxt UI, Nuxt Content, NuxtHub, and others) change between versions, so check the installed module's docs before relying on exact props or options.
For guidance that matches the modules and versions installed in a project, add the Nuxt module there:
npx nuxi module add nuxt-skill-hub
nuxt prepare then writes a local skill that also includes each installed module's skill.
Finish
Before concluding a change that touches more than one surface, read Verification and Finish.
- Check paired surfaces: page and head, server and client, global and local errors.
- Verify framework behavior, not only visible output.
- Keep module guidance scoped to the owning module.
Generated by nuxt-skill-hub. Do not edit this file manually.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/nuxt-skill.onmax.me/nuxt">View nuxt on skillZs</a>