What problem does it solve?
This Skill prevents broken navigation, unexpected 404s, and incorrect access control when adding or modifying Next.js App Router routes and layouts in the repo.
Core Features & Use Cases
- Public marketing routing conventions: Place SEO-visible pages under
src/app/[locale]/(marketing)/... and keep them aligned with i18n/locale structure.
- Auth and private routing separation: Use
src/app/[locale]/(auth)/... for sign-in/sign-up/callback flows and keep authenticated app pages under src/app/veta-app/....
- Supabase session protection & middleware alignment: Ensure unauthenticated users are redirected correctly via
veta-app/**/layout.tsx and that public paths remain accessible through src/lib/supabase/middleware.ts (including PUBLIC_ROUTES and locale handling).
- SEO/non-index handling for dev-only pages: Mark dev-only segments with
robots: { index: false, follow: false } and exclude them from src/app/sitemap.ts.
Quick Start
Tell me whether the new route should be public (marketing/auth) or private (/veta-app), then I’ll place it in the correct src/app/ segment and specify the needed layout, redirects, and middleware/sitemap/robots adjustments.