What problem does it solve?
This Skill provides a structured decision framework and implementation checklist to keep Next.js App Router frontend work aligned with server-first architecture, Prisma-backed data access, and consistent UI patterns.
Core Features & Use Cases
- Server Components-first: default to server components and expose interactive client pieces only when necessary.
- Prisma on Node runtime: ensure all Prisma usage runs in a Node runtime context, not Edge, with explicit runtime hints where applicable.
- Shared validation & UI conventions: enforce a single Zod schema for server and client validation, and a Tailwind/shadcn/ui driven UI layer across frontend/ and routes.
Quick Start
Set up a Next.js App Router project that enforces server-first boundaries, places Prisma calls on the server, and applies the provided workflow to new pages and forms.