nuxt-nuxt-skill-hub-prepare-eexist

name	nuxt-nuxt-skill-hub-prepare-eexist
description	Always-on Nuxt disambiguation layer for this project. Use it to choose the right Nuxt pack first, then switch to Vue or module guidance only when Nuxt no longer owns the abstraction.

Nuxt Skill Index

This file keeps the highest-frequency Nuxt decisions in context. Use it to avoid generic Vue fallbacks, then route into the right Nuxt pack, Vue guidance, or module delta skill.

Activation Flow

1. Explore the project first: inspect the real page, component, route, server handler, collection, or module surface you are changing.
2. Use the routing sections in this file and load the smallest matching Nuxt pack.
3. If the remaining work is mainly Vue component, composable, reactivity, or SFC work, open Vue Best Practices.
4. If module authoring is part of the task, load Module Authoring Conventions before changing defineNuxtModule, runtime extensions, hooks, or release scaffolding.

High-Frequency Nuxt Decisions

• If the task touches SSR, initial page load, or route-driven data, prefer useFetch or useAsyncData before onMounted plus $fetch.
• If the task changes page options, layout selection, route middleware, or page-level behavior, check definePageMeta before adding ad hoc wiring.
• If the task changes title, meta tags, canonical URLs, or OG data, check useHead or useSeoMeta before page-meta or template markup.
• If content lives in JSON or YAML records, or the UI needs generated docs navigation, choose data collections and collection-navigation primitives before manual assembly.
• If the UI surface is page chrome, a table, a form, a modal, a command palette, or a dropdown, prefer a Nuxt UI primitive before raw HTML or custom listeners.
• If runtime config, tokens, secrets, or privileged API calls are involved, keep them server-side and expose only a server route or the minimum public config.
• If hydration, browser-only APIs, time, randomness, or cookies are involved, use SSR-safe primitives first and isolate browser-only work behind ClientOnly or onMounted.
• If the fix touches errors, fallback UI, or recovery flow, check both global and local surfaces before concluding the work is complete.
• If the solution looks correct but uses generic Vue or hand-rolled HTML, confirm Nuxt, Nuxt Content, or Nuxt UI does not already own that abstraction.

Precedence

• Repository-global instructions and required workflows win first.
• This file keeps the common Nuxt forks in context.
• Nuxt packs provide deeper framework guidance.
• Vue guidance covers component, composable, and SFC patterns after the Nuxt decision is settled.

How to use this skill map

1. Explore the current surface first: page, layout, component, server handler, content collection, or module-owned file.
2. Load the first matching Nuxt pack from the routing table below.
3. If the remaining work is mainly Vue component or composable implementation, switch to Vue Best Practices.
4. Open deeper Nuxt packs only when the first pack points you there.

Common forks in the road

Task shape or symptom	Load first	Why
SSR, initial page load, route params, or hydration-sensitive data	Data Fetching and SSR	Prefer useFetch or useAsyncData over setup-time $fetch or onMounted fetches.
Page options, route middleware, layout selection, title, meta tags, or OG data	Page Meta, Head, and Layout	Separate page behavior from document metadata and layout structure before editing.
A generic Vue fix or raw HTML implementation looks tempting	Abstraction Disambiguation	Check whether Nuxt, Nuxt Content, or Nuxt UI already owns the abstraction.
The remaining work is mostly .vue components, composables, reactivity, or SFC structure	Vue Best Practices	Switch to Vue-specific guidance after the Nuxt ownership and routing decisions are already settled.
Global errors, local fallback UI, clearError, showError, or recovery flows	Error Surfaces and Recovery	Nuxt error handling often needs both global and local surfaces to be correct.
Secrets, runtime config, privileged API calls, or server/client boundary confusion	Architecture Boundaries	Move sensitive logic server-side first, then pair with config and route rules as needed.
Before finishing a fix that spans multiple files or surfaces

Vue guidance

Use Vue Best Practices when the task is mainly Vue component, composable, reactivity, props/emits, or SFC work and Nuxt no longer owns the abstraction.

Start with these must-read Vue references:

• reactivity
• sfc
• component-data-flow
• composables

All Nuxt packs

Pack	Focus	Typical triggers
Abstraction Disambiguation	Choose Nuxt-owned abstractions before generic Vue, raw HTML, or ad hoc glue code.	A generic Vue or HTML fix looks plausible You need to decide whether Nuxt, Nuxt Content, or Nuxt UI already owns the surface
Page Meta, Head, and Layout	Separate page behavior, document metadata, and layout structure before editing.	Pages, layouts, middleware, or page options Title, meta tags, canonical URLs, or OG metadata
Error Surfaces and Recovery	Cover both global and local error boundaries and use the right recovery utilities.	Global error pages or local error boundaries Recovery flows, clearError, showError, or fallback UI
Verification and Finish	Verify the intended framework behavior and re-check paired surfaces before concluding work.	The fix spans more than one surface You are about to finish a Nuxt change and need to confirm the right abstraction
Data Fetching and SSR	Deduplication, payload correctness, and request-safe loading.	Pages, layouts, or composables fetching initial data SSR-visible content or hydration-sensitive state
Hydration and SSR Consistency	SSR/CSR determinism, client-only boundaries, and mismatch prevention.	Hydration warnings or client-only rendering State that differs between server and browser
Architecture Boundaries

Module guides

No module skills discovered. Use Nuxt guidance plus official module docs when module-specific guidance is missing.

Before Completion

• Did I choose a Nuxt primitive where a generic Vue or raw HTML solution would be tempting?
• Did I check whether the fix needs a second surface such as global or local, or server or client?
• Did I choose the right concept pair: page meta vs head, data collection vs page collection, component primitive vs custom markup?
• Did I verify the framework behavior that matters, not just the visible output?

Primary Packs

Start with Abstraction Disambiguation, Page Meta, Head, and Layout, Error Surfaces and Recovery, Verification and Finish, Data Fetching and SSR when the task matches one of those common routes.

---

Generated by nuxt-skill-hub. Do not edit this file manually.