plugins/nextjs-expert/skills/nextjs-stack/SKILL.md
Next.js 16+ complete stack with App Router, Prisma 7, Better Auth, shadcn/ui, TanStack Form, Zustand. Use as the master reference combining all framework skills. Do NOT use for: core framework API details — routing, caching, Server Components internals, proxy.ts (use nextjs-16 and its references).
npx skillsauth add fusengine/agents nextjs-stackInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Master skill combining all framework documentation for modern Next.js development.
Before ANY implementation, use TeamCreate to spawn 3 agents:
After implementation, run fuse-ai-pilot:sniper for validation.
| Layer | Technology | Skill Reference |
|-------|------------|-----------------|
| Framework | Next.js 16 (App Router) | nextjs-16 |
| Database ORM | Prisma 7 | prisma-7 |
| Authentication | Better Auth 1.2 | better-auth |
| UI Components | shadcn/ui 3.8.0 | nextjs-shadcn |
| Forms | TanStack Form | nextjs-tanstack-form |
| State | Zustand | nextjs-zustand |
| Styling | Tailwind CSS 4 | tailwindcss |
| i18n | next-intl 4.0 | nextjs-i18n |
Detailed guidance lives in references/ to keep this file scannable — load only what the task needs:
| File | Load when… | |------|------------| | references/stack-decisions.md | Justifying a technology choice (Better Auth vs NextAuth, Prisma vs Drizzle, TanStack Form vs RHF, Zustand vs Redux, shadcn/ui vs MUI) | | references/solid-architecture.md | Setting up or reviewing the project's module/folder structure | | references/integration-points.md | Wiring two parts of the stack together (auth+DB, forms+UI, state+RSC, i18n+routing) | | references/quick-reference.md | Looking up which sub-skill file covers a specific feature (App Router, Prisma schema, Better Auth OAuth, …) | | references/best-practices.md | Doing a final review pass before shipping | | references/getting-started.md | Bootstrapping a brand-new project step by step |
For framework-specific detail, go directly to the sub-skill: nextjs-16, prisma-7, better-auth, nextjs-shadcn, nextjs-tanstack-form, nextjs-zustand, nextjs-i18n, solid-nextjs.
testing
Copy self-audit and ban-lists — filler verbs/hype adjectives, slop placeholder names, fake-precise numbers, Title Case headlines, humor in error copy ('Oops!'), em-dash crutch, one copy register per page.
development
Logged-in web apps — dashboards, auth flows, settings, onboarding, data tables, command palettes, modals, toasts. Register `product`: density and glance-speed over marketing polish, no hero/CTA-tricks, every data surface covers empty/loading/error explicitly, tables and dataviz follow preattentive-processing rules.
development
Marketing sites, landing pages, campaign pages — register `brand` (design IS the product). Structure comes from the register's POV + a macrostructure pick, never from copying an inspiration site's section flow. Hero discipline, deviated section order, asymmetric grids, and a silhouette lookalike-test gate before ship.
development
Token-strategy core — OKLCH color rules, neutral tinting, accent-commitment levels, type scale, 8pt spacing grid, touch targets, and the canonical output format of design-system.md (the file the harness gates on). This is routing step 1 of design-method/SKILL.md — read it before design-web/design-webapp/design-ios/design-android, before picking or auditing a single color/type/spacing value.