nextjs-stack
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.
What this skill does
# Next.js Complete Stack Master skill combining all framework documentation for modern Next.js development. ## Agent Workflow (MANDATORY) Before ANY implementation, use `TeamCreate` to spawn 3 agents: 1. **fuse-ai-pilot:explore-codebase** - Analyze project structure and existing patterns 2. **fuse-ai-pilot:research-expert** - Verify latest docs for all stack technologies 3. **mcp__context7__query-docs** - Check integration compatibility After implementation, run **fuse-ai-pilot:sniper** for validation. --- ## Overview ### When to Use - Starting a new Next.js 16 project from scratch - Need the complete recommended technology stack - Building production applications with authentication - Implementing forms, state management, and UI components - Understanding how all parts fit together ### Technology Stack | 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` | --- ## Stack Decisions ### Why These Technologies | Choice | Reason | |--------|--------| | **Better Auth** over NextAuth.js | TypeScript-first, plugin system, self-hosted | | **Prisma 7** over Drizzle | Mature ecosystem, migrations, studio | | **TanStack Form** over React Hook Form | Modern API, server actions, type safety | | **Zustand** over Redux/Context | Minimal boilerplate, SSR-friendly | | **shadcn/ui** over MUI/Chakra | Copy/paste ownership, Radix primitives | ### Forbidden Patterns - **NextAuth.js** - Use Better Auth instead - **Pages Router** - Use App Router for new projects - **React Hook Form** - Use TanStack Form - **Client Components by default** - Server Components first --- ## SOLID Architecture ### Project Structure ``` src/ ├── app/ # Route handlers only │ ├── [locale]/ # i18n routing │ ├── api/ # API routes │ └── layout.tsx # Root layout ├── modules/ │ ├── cores/ # Shared infrastructure │ │ ├── i18n/ # Internationalization │ │ ├── shadcn/ # UI components │ │ ├── lib/ # Utilities (cn, etc.) │ │ └── db/ # Prisma client │ ├── auth/ # Authentication module │ └── [feature]/ # Feature modules └── proxy.ts # Route protection ``` ### Module Pattern Each feature module contains: - **src/services/** - Business logic - **src/hooks/** - React hooks - **src/components/** - UI components - **src/interfaces/** - TypeScript types --- ## Integration Points ### Authentication + Database Better Auth integrates with Prisma adapter for user storage. Schema in `prisma/schema.prisma` includes User, Session, Account, Verification tables. ### Forms + UI + Validation TanStack Form with Zod validation using shadcn/ui Field components. Server Actions for form submission. ### State + Server Components Zustand stores for client state only. Server Components fetch data directly. No global state for server data. ### i18n + Routing next-intl with `[locale]` segment. proxy.ts handles locale detection and redirects. --- ## Quick Reference ### Next.js 16 | Feature | Reference | |---------|-----------| | App Router | `nextjs-16/app-router.md` | | Server Components | `nextjs-16/server-components.md` | | Caching | `nextjs-16/caching.md`, `cache-components.md` | | proxy.ts | `nextjs-16/proxy.md` | ### Prisma 7 | Feature | Reference | |---------|-----------| | Schema | `prisma-7/schema.md` | | Client | `prisma-7/client.md` | | Migrations | `prisma-7/migrations.md` | | TypedSQL | `prisma-7/typed-sql.md` | ### Better Auth | Feature | Reference | |---------|-----------| | Setup | `better-auth/installation.md` | | OAuth | `better-auth/providers/` | | Plugins | `better-auth/plugins/` | | Prisma adapter | `better-auth/adapters/prisma.md` | --- ## Best Practices 1. **Server Components default** - Add `'use client'` only when needed 2. **Colocate code** - Keep related code in feature modules 3. **Type everything** - Full TypeScript, no any 4. **Fetch where used** - No prop drilling for data 5. **Validate at boundary** - Zod schemas for all inputs 6. **Cache explicitly** - Use `use cache` directive --- ## Getting Started 1. Review `nextjs-16` for App Router fundamentals 2. Set up `prisma-7` for database 3. Add `better-auth` for authentication 4. Install `nextjs-shadcn` components 5. Configure `nextjs-i18n` if multilingual 6. Add `nextjs-zustand` for client state
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.