Nuxt 3

What problem does it solve?

Nuxt 3 codebases often drift into inconsistent folder usage, scattered business logic, and risky refactors where pages, components, and server routes blur responsibilities. This Skill creates a consistent architecture so an agent can reorganize code without breaking SSR behavior, auto-import conventions, or error handling.

Core Features & Use Cases

• Enforces a Nuxt-specific folder contract: routes in pages/, UI components in components/, reusable logic in composables/, and server endpoints in server/api/.
• Standardizes safe data flow: pages stay declarative, composables wrap useFetch/useAsyncData, and server routes delegate business logic to server/utils/.
• Hardens SSR, errors, and security: uses createError()/error.vue patterns, validates config via Nitro, and keeps secrets out of runtimeConfig.public.
• Pinia state guidance: global/shared state goes to stores/, while local UI state remains in composables.

Quick Start

Give your AI agent the instruction: “Analyze my Nuxt 3 repository and produce a phased refactor plan that moves data fetching into composables, moves business logic into server utilities, and aligns folder responsibilities with the Nuxt 3 architecture rules.”