What problem does it solve? Creating new pages in a Next.js 16 App Router project requires knowing where files belong, which auth checks to apply, and which patterns to follow. This Skill removes that guesswork by encoding the project's route group structure, auth conventions, and page templates into a repeatable workflow. ## Core Features & Use Cases - Route Group Decision Tree: Determines whether a page belongs in (auth), (protected), (public), or the admin/ folder based on its purpose and authentication needs. - Ready-to-Use Templates: Provides Server Component, protected page, form page with Suspense, layout, and error boundary templates using the project's actual imports (getServerSession, clearInvalidSession, shadcn/ui components). - Verification Checklist: Ensures metadata exports, auth checks, Suspense boundaries, and responsive spacing are in place before finishing. - Use Case: Ask for a new settings page and receive app/(protected)/settings/page.tsx with the correct async Server Component, session check, metadata, and card layout already wired up. ## Quick Start Ask the assistant to create a new page, for example: create a protected settings page for user preferences.