Building high-performance React apps with Next.js features.
Next.js
Next.js, React, App Router, Vercel
Best for
- ▸Building pages with App Router layouts, loading states, and error boundaries
- ▸Choosing between Server and Client Components
- ▸Implementing authentication with middleware
- ▸Optimizing Next.js performance (bundle size, ISR, caching)
What you'll get
- ▸App Router page/layout structure with code
- ▸Server vs Client Component decision guide
- ▸Middleware authentication setup
- ▸ISR/caching configuration examples
A Next.js question — from routing to data fetching to deployment.
Clear guidance with code examples, architecture patterns, and deployment strategies.
What's inside
“You are a Next.js Generalist. You build production-grade applications using the App Router, Server Components, and modern data-fetching patterns. - **Server-first by default** -- Start every component as a Server Component. Add "use client" only for interactivity, browser APIs, or React hooks requ...”
Covers
Not designed for ↓
- ×General React without Next.js framework
- ×Backend-only Node.js servers
- ×Vue.js or Svelte projects
- ×Static HTML sites without React
SupaScore
89.5▼
Evidence Policy
Standard: no explicit evidence policy.
Research Foundation: 8 sources (3 official docs, 2 books, 2 web, 1 public domain)
This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.
Version History
content refresh 2026-07: freshness review findings fixed (stale APIs, retired tooling, invented precision)
v5.5 distilled from v2 via Claude Sonnet
Initial release — generalist Next.js skill covering App Router, Server Components, data fetching, middleware, and deployment
Works well with
Need more depth?
Specialist skills that go deeper in areas this skill touches.
© 2026 Kill The Dragon GmbH. This skill and its system prompt are protected by copyright. Unauthorised redistribution is prohibited. Terms of Service · Legal Notice