Nuxt 4+ development guidance covering server routes, file-based routing, middleware, composables, and configuration patterns.
Works with
Organized reference files for API endpoints, server middleware, routing, middleware/plugins, Nuxt composables, components, and configuration
Includes h3 v1 helpers for validation, WebSocket, and SSE; Nitro v2 patterns; and typed router support
Highlights Nuxt 4 breaking changes (NuxtPage vs Nuxt, getRouterParam, useRequestURL) with migration examples
Cross-
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionnuxtExecute the skills CLI command in your project's root directory to begin installation:
Fetches nuxt from onmax/nuxt-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate nuxt. Access via /nuxt in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
1
total installs
1
this week
619
GitHub stars
0
upvotes
Run in your terminal
1
installs
1
this week
619
stars
Progressive guidance for Nuxt 4+ projects (v4.3+) with latest patterns and conventions.
Working with:
Read specific files based on current work:
For Vue composables: See vue skill composables.md (VueUse, Composition API patterns)
For UI components: use nuxt-ui skill
For database/storage: use nuxthub skill
For content-driven sites: use nuxt-content skill
For creating modules: use nuxt-modules skill
For project scaffolding/CI: use ts-library skill
Consider loading these reference files based on your task:
DO NOT load all files at once. Load only what's relevant to your current task.
// server/api/hello.get.ts
import { z } from 'zod'
export default defineEventHandler(async (event) => {
const { name } = await getValidatedQuery(event, z.object({
name: z.string().default('world'),
}).parse)
return { message: `Hello ${name}` }
})
You are working with Nuxt 4+. Key differences:
| Old (Nuxt 2/3) | New (Nuxt 4) |
|---|---|
<Nuxt /> |
<NuxtPage /> |
context.params |
getRouterParam(event, 'name') |
window.origin |
useRequestURL().origin |
| String routes | Typed router with route names |
| Separate layouts/ | Parent routes with <slot> |
If you're unsure about Nuxt 4 patterns, read the relevant guidance file first.
When to fetch latest docs:
Official sources:
Main skill: ~300 tokens. Each sub-file: ~800-1500 tokens. Only load files relevant to current task.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: nuxt is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in nuxt — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
nuxt has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend nuxt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added nuxt from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
nuxt fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in nuxt — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
nuxt has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend nuxt for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: nuxt is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 75