npx claudepluginhub xoai/sageThis skill uses the workspace's default tool permissions.
**Layer 3 — Stack Composition**
Scaffolds opinionated full-stack Next.js projects with App Router, TypeScript, Tailwind v4, shadcn/ui, Biome, Bun, better-auth, and Vercel deployment via guided steps.
Provides Next.js patterns for App Router/Pages Router, rendering (SSR/SSG/ISR, server/client components), data fetching/caching, dynamic routing/middleware, performance (images/fonts/bundles), NextAuth, and Jest/Playwright testing.
Provides patterns for Next.js 14+ App Router including Server Components, streaming, parallel routes, data fetching, caching, and Server Actions. Use for new apps, migrations, and full-stack features.
Share bugs, ideas, or general feedback.
Layer 3 — Stack Composition
Integration patterns for the most common Next.js fullstack combination: Next.js App Router + Tailwind CSS + Prisma ORM + Auth.js.
Individual framework docs tell you how each tool works in isolation. They don't tell you how they work TOGETHER. Where does the Prisma client go in a Next.js project? How does Auth.js middleware interact with App Router layouts? What happens when Tailwind's utility classes meet server components?
These integration points — the seams between frameworks — are where most bugs live. Each framework team documents their own tool. Nobody documents the gaps between tools. That's what this pack does.
| Type | Files | Coverage |
|---|---|---|
| Integration patterns | 4 | Prisma + Next.js, Auth.js + Next.js, Tailwind + Next.js, Full-stack project structure |
| Anti-patterns | 3 | Prisma client instantiation, auth in wrong layer, Tailwind in server components |
| Constitution | 1 | 5 stack integration principles |
This pack requires web, react, and nextjs to be
installed. It activates when the codebase-scan detects Next.js, Tailwind CSS,
and Prisma in the project dependencies.