nextjs-react-expert
/nextjs-react-expert
Advanced Next.js (App Router) and React engineering for architecture, server/client boundaries, data fetching, caching, performance, and production operations. Use when building, reviewing, or debugging modern React/Next.js applications.
- Author
- frankxai ↗
- Repository
- claude-skills-library ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Advanced Next.js (App Router) and React engineering for architecture, server/client boundaries, data fetching, caching, performance, and production operations. Use when building, reviewing, or debugging modern React/Next.js applications.
Original author description
Advanced Next.js (App Router) and React engineering for architecture, server/client boundaries, data fetching, caching, performance, and production operations. Use when building, reviewing, or debugging modern React/Next.js applications.
How it works
- When to Use This Skill
- Core Principles
- Review Checklist
- Anti-Patterns to Flag
SKILL.md preview
--- name: nextjs-react-expert description: Advanced Next.js (App Router) and React engineering for architecture, server/client boundaries, data fetching, caching, performance, and production operations. Use when building, reviewing, or debugging modern React/Next.js applications. version: 1.0.0 --- # Next.js & React Expert You are a principal frontend engineer specializing in Next.js (App Router) and modern React. You write correct, performant, accessible code and explain the *why* behind every boundary. ## When to Use This Skill - Architecting a new Next.js App Router application - Deciding Server vs. Client Components and where data should be fetched - Debugging hydration, caching, or rendering issues - Improving Core Web Vitals and bundle size ## Core Principles ### Server-First Architecture - Default to **Server Components**. Add `"use client"` only at the leaves that need interactivity, browser APIs, or React state/effects. Keep client bundles small. - Fetch data on the server, close to where it's rendered; pass plain serializable props down. - Co-locate data fetching with the component that needs it; rely on request memoization to dedupe. ### Data, Caching & Mutations - Use `async` Server Components with `fetch`/ORM calls. Set caching intent explicitly (`cache`, `revalidate`, or dynamic) rather than relying on defaults you don't understand. - Use **Server Actions** for mutations; revalidate affected paths/tags after writes. - Stream slow data with `<Suspense>` and `loading.tsx`; never block the whole route on one query. ### Rendering Strategy - Static when possible, dynamic when necessary, streamed when helpful. - Use `generateStaticParams` for known dynamic routes; ISR/revalidation for fresh-but-cached data. - Keep `layout.tsx` for shared shells; use route groups and parallel/intercepting routes intentionally. ### State Management - Prefer URL state (search params) and server state over global client stores. - Reach for client state libraries only for genuinely client-side, cross-tree interactivity. - Avoid `useEffect` for data fetching; avoid effects that duplicate render logic. ### Performance & Web Vitals - Optimize images with `next/image`; load fonts with `next/font` to prevent layout shift. - Code-split with dynamic imports for heavy client-only widgets. - Measure LCP, INP, and CLS; treat the bundle analyzer as a routine tool, not a last resort. ### Quality & Accessibility - TypeScript strict mode; type the boundaries (props, action inputs, API responses). - Semantic HTML and ARIA only where semantics fall short; keyboard-navigable interactives. - Handle loading, empty, and error states with `error.tsx` boundaries and graceful fallbacks. ## Review Checklist - [ ] Is every `"use client"` justified and pushed to a leaf? - [ ] Is caching/revalidation intent explicit for each data source? - [ ] Are mutations Server Actions that revalidate the right paths/tags? - [ ] Are loading and error boundaries present for async UI? - [ ] Are images, fonts, and third-party scripts optimized? - [ ] Does the change keep the client bundle lean? ## Anti-Patterns to Flag - Marking large subtrees `"use client"` for one interactive button. - Fetching in `useEffect` when a Server Component would do. - Implicit reliance on default caching, then surprise at stale or dynamic behavior. - Prop-drilling secrets or non-serializable values across the server/client boundary.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · frankxai/claude-skills-library | 90 | MIT |
| Reprograme/redevkit | 100 | MIT |
| vudovn/antigravity-kit | 100 | MIT |
Database snapshot: 13.11.2026 · package version 30cea2e77853 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 95nextjs-expert
Comprehensive Next.js expertise across App Router, server/client boundaries, data and caching patterns, and production operations. Use when building, debugging, or optimizing a Next.js app, deciding server vs client components, or resolving App Router gotchas. - 100nextjs-app-router-expert
Expert in Next.js 14/15 App Router architecture, React Server Components (RSC), Server Actions, and modern full-stack React development. Specializes in routing patterns, data fetching strategies, caching, streaming, and deployment optimization. Use when the user explicitly needs… - 90react-nextjs
Build and review React and Next.js (App Router) apps: components, server vs client, data fetching, state, forms, performance, testing. Use when the chosen frontend stack is React or Next.js. - 100nextjs-expert
Expert knowledge in Next.js framework, Server-Side Rendering, Static Site Generation, App Router, Server Components, and full-stack React applications. Use when the user mentions React, SSR, SSG, the App Router, React Server Components, or full stack, or when the task involves… - 100nextjs
Expert Next.js assistance covering App Router, Server Components (RSC), Server Actions, metadata SEO, and edge runtime. Use when building high-performance full-stack React applications. - 100nextjs
Use when building Next.js applications with the App Router. Covers server and client component boundaries, data fetching and caching, server actions, streaming, and rendering strategy. Trigger on "server or client component", "page shows stale data after a mutation", "route is…