ref-sp-js-nextlisted

# Next.js ## Purpose Provide portable defaults for maintainable Next.js apps, especially around App Router structure, client and server boundaries, and framework-specific integrations that behave differently from plain React. ## When to use this skill - Creating or reviewing App Router routes, layouts, and metadata. - Deciding whether a component or feature belongs on the server or client side. - Configuring Next.js or framework-sensitive integrations. - Choosing Next-specific libraries such as internationalization solutions. ## Scope Boundaries - Use this skill for Next.js framework rules, routing structure, rendering boundaries, and framework-specific integrations. - Use `ref-sp-js-react` for general React component structure, hooks, local UI state, and React dependency choices that are not specific to Next.js. - Use `ref-sp-js-next-template` when the user is planning or reviewing a whole React and Next app rather than one framework concern. - Use `ref-sp-js-typescript` when the question is primarily about strict type modeling or TypeScript configuration. - Use `ref-sp-js-web-standalone-template` when the requirement is a browser-only app that should stay framework-free and no-build by default. ## Defaults - Prefer App Router for new Next.js work. - Prefer Server Components by default and add `'use client'` only where interactivity or browser-only APIs require it. - Prefer thin route files that delegate reusable UI and logic into feature code. - Prefer strict TypeSc