nuxt
Skill28 starsChanged 30 days agoMITView on GitHub
Nuxt 4 full-stack Vue framework. app directory layout, file-based routing, layouts and middleware, useFetch and useAsyncData, useState, server routes on Nitro, rendering modes and route rules, modules and layers, deployment, plus Nitro v3 and Nuxt 5 preparation. Use when working in a project with nuxt.config.ts, server/ routes, Nuxt modules, or when writing a Nuxt module.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- Contentrain/studiotheir own version, first seen Nov 8, 2026
- antfu/skillstheir own version, first seen Nov 5, 2026
- onmax/nuxt-skillstheir own version, first seen Nov 1, 2026
- vercel-labs/emulatetheir own version, first seen Oct 29, 2026
- G1Joshi/Agent-Skillstheir own version, first seen Oct 13, 2026
- kirklin/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use nitro.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillnitro
Build and deploy universal JavaScript servers with Nitro v3. Use when working with nitro.config.ts, defineNitroConfig, defineHandler, defineConfig, server.ts entry, filesystem routing, route rules, useStorage, defineCachedHandler, useDatabase, definePlugin, runtime hooks, Vercel/Cloudflare deployment, or migrating from Nitro v2/nitropack.
Also in 4 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- antfu/skills★ 6.1ksame name
- vercel-labs/emulate★ 2ksame name
- onmax/nuxt-skills★ 724same name
- JetBrains/skills★ 386same name
- yamcodes/arkenv★ 151same name
- konnga/skill-buddy★ 128same name
- G1Joshi/Agent-Skills★ 15same name
- skills-club/skills-live★ 13same name
- Contentrain/studio★ 4same name
- SnowBeatRain/skills★ 3same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository16 other files it gives its agents.
- antfuSkill
- build-toolingSkill
- designSkill
- find-skillsSkill
- vitepressSkill
- vue-a11ySkill
- vue-ciSkill
- vue-clean-componentsSkill
- vue-dataSkill
- vue-debugSkill
- vue-formsSkill
- vue-performanceSkill
- vue-reviewSkill
- vueSkill
- vue-uiSkill
- vue-upgradeSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 0 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read nuxt.config.ts: compatibilityVersion, modules, experimental flags, srcDir.
- Very specific: line 13
Check the layout. Nuxt 4 puts app code in app/ (~ and @ point there).
- Very specific: line 14
Check how server utilities are imported.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Nuxt
Versions checked on 2026-10-15: Nuxt 4.6.1 (Node ^22.22.3 || ^24.15.0 || >=26). Nuxt 3 reached end of life on 2026-07-31. Nuxt 5 is planned for Q4 2026 and exists only as nightly builds. Nuxt 4 server code runs on nitropack 2.x; Nitro v3 (nitro) is in public beta.
Before writing code
- Read
nuxt.config.ts:compatibilityVersion, modules,experimentalflags,srcDir. - Check the layout. Nuxt 4 puts app code in
app/(~and@point there);server/,shared/,public/,modules/andlayers/stay at the root (~~,@@). A Nuxt 3 style layout withoutapp/still works. - Check how server utilities are imported. Since 4.6 they can come from
nuxt/server; a project uses either that or auto-imports, not both (NUXT_E8012). - A Nuxt 3 project is migration work first: see the
vue-upgradeskill.
Rules
- Fetch in pages and components with
useFetchoruseAsyncDataso the result travels in the SSR payload. Use$fetchin event handlers. Calling$fetchdirectly in setup fetches twice. - Nuxt 4 data refs are shallow: replace
data.valueinstead of mutating nested fields, or opt intodeep: true. - Give
useAsyncDatastable, unique keys. Calls with the same key share state. - Shared state across components uses
useState, never a module-levelref(it leaks between SSR requests). - Browser-only code goes in
onMounted,<ClientOnly>or a.clientplugin. - Secrets live in
runtimeConfig(server only). OnlyruntimeConfig.publicreaches the browser. - Validate input in server routes; throw
createErrorwith a status code instead of returning error objects.
Reference map
| Topic | Start here |
| Nuxt 4 docs: structure, config, routing, data fetching, server, rendering, layers, hooks | nuxt-guide |
| Nuxt 3 to 4 changes | nuxt4-migration |
| Writing and publishing Nuxt modules | modules-guide |
| Nitro v3 (beta), for standalone Nitro and Nuxt 5 | nitro-guide |
| 4.5 and 4.6 changes, Nuxt 5 prep | vue-upgrade skill, nuxt guide |
Related: vue for components, vue-data for data-fetching patterns, vue-ui for Nuxt UI, design for UnoCSS.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.