nuxt
Nuxt application development and maintenance. Use for project structure, pages and routing, data fetching, SSR-safe state, middleware, plugins, server routes, runtime config, route rules, layers, built-in components, hydration, upgrades, and testing.
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- nuxt
- license
- MIT
- description
- Nuxt application development and maintenance. Use for project structure, pages and routing, data fetching, SSR-safe state, middleware, plugins, server routes, runtime config, route rules, layers, built-in components, hydration, upgrades, and testing.
02 资源文件 7
- 参考文档references/middleware-plugins.md2.7 KB
- 参考文档references/nuxt-components.md3.0 KB
- 参考文档references/nuxt-composables.md4.5 KB
- 参考文档references/nuxt-config.md3.7 KB
- 参考文档references/project-setup.md3.0 KB
- 参考文档references/routing.md3.3 KB
- 参考文档references/server.md3.3 KB
03 SKILL.md 正文
Nuxt
Use Nuxt-owned primitives for Nuxt lifecycle, rendering, routing, and server behavior. Hand module-specific behavior to the matching module skill instead of reproducing its API here.
Start here
- Inspect
package.json, the lockfile,nuxt.config.*, and the directory layout before choosing an API. Nuxt features move, so verify the installed version instead of assuming the latest release. - Open only the reference that owns the task.
- Prefer the smallest Nuxt primitive that preserves SSR, hydration, and generated types.
- Run
nuxt prepareafter config, module, alias, or generated-type changes, then verify the affected runtime path.
Reference map
- Project structure, upgrades, deployment mode, and testing: project-setup.md
- Data fetching, state, request context, cookies, head, and hydration: nuxt-composables.md
- Pages, layouts, navigation, route metadata, and errors: routing.md
- Route middleware, app plugins, and runtime hooks: middleware-plugins.md
- API routes, server middleware, validation, caching, and Nitro: server.md
- Built-in components, assets, images, and lazy hydration: nuxt-components.md
- Nuxt config, runtime config, route rules, layers, modules, Vite, and Nitro options: nuxt-config.md
Ownership boundaries
- Use the
nuxt-modulesskill for authoring or publishing a Nuxt module. - Use the relevant module skill for Nuxt UI, Nuxt Content, Nuxt Studio, NuxtHub, Nuxt Image, Nuxt Scripts, Nuxt SEO, or another installed module.
- Use official VueUse guidance for VueUse composables. When names overlap, Nuxt owns Nuxt lifecycle and SSR semantics; see nuxt-composables.md.
- Use Vue guidance for component-local reactivity that has no Nuxt lifecycle or rendering concern.
Baseline
<script setup lang="ts">
const { data: products, status, error } = await useFetch('/api/products')
useSeoMeta({
title: 'Products',
description: 'Browse the product catalog.',
})
</script>
<template>
<main>
<p v-if="status === 'pending'">Loading…</p>
<p v-else-if="error">Could not load products.</p>
<ProductList v-else :products="products ?? []" />
</main>
</template>
useFetch integrates the request with Nuxt's SSR payload, while useSeoMeta participates in Nuxt's head lifecycle. Reach for lower-level primitives only when the task needs behavior these do not provide.
04 同仓库更多 Skills
web-perf
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.
unlighthouse
Run Google Lighthouse on every page of a site with the unlighthouse CLI, and fail CI on low scores with unlighthouse-ci. Use when a task mentions unlighthouse, unlighthouse-ci, site-wide Lighthouse scans, performance budgets in CI, unlighthouse.config.ts, defineUnlighthouseConfig, scanner.exclude, dynamic sampling, the authenticate hook, or a scan that never exits, skips pages, or refuses to clear its output folder.
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
fixing-accessibility
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
better-accessibility
Reviews and fixes keyboard and focus behavior, ARIA, accessible names, forms, screen-reader announcements, motion and zoom in your project against WCAG 2.2.
web-perf
Audit, diagnose, or optimize website loading and interaction performance, Core Web Vitals, and Lighthouse performance scores.