ref-sp-js-next-templatelisted

# React + Next App ## Purpose Provide app-level defaults for planning and reviewing a whole React and Next.js application without duplicating the lower-level framework guidance that belongs in `ref-sp-js-react`, `ref-sp-js-next`, and `ref-sp-js-typescript`. ## When to use this skill - Scaffolding a new React and Next.js app. - Reviewing whether an existing React and Next app has a coherent baseline stack and folder structure. - Deciding whether a requirement deserves a full app or can stay a simpler standalone browser tool. - Choosing app-level defaults such as package manager, TypeScript baseline, and top-level structure. ## Scope Boundaries - Use this skill for whole-app setup, baseline stack decisions, and top-level app structure. - Use `ref-sp-js-react` for component internals, hooks, local UI state, and general React dependency choices. - Use `ref-sp-js-next` for App Router structure, client and server boundaries, framework integrations, and Next-specific library choices. - Use `ref-sp-js-typescript` for strict type modeling, runtime boundaries, and `tsconfig` design. - Use `ref-sp-js-web-standalone-template` when the requirement can stay a no-build browser app instead of becoming a full React and Next project. ## Defaults - Prefer Next.js App Router plus strict TypeScript as the baseline for a whole React and Next app. - Prefer Yarn for dependency management and script execution in Node-based React and Next apps. - Keep the top-level app structure small and feat