nextjs-expert

Solid

Next.js 14+ gotchas and decision criteria. Covers server/client boundary, caching strategy, and data fetching patterns Claude commonly gets wrong.

Web & Frontend 24 stars 3 forks Updated today MIT

Install

View on GitHub

Quality Score: 85/100

Stars 20%
47
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
88
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

> **AI-consumed reference.** Optimized for Claude to read during execution. > Human-readable explanation: see [docs/architecture/HIERARCHICAL_PLANNING.md](../../../docs/architecture/HIERARCHICAL_PLANNING.md) > or [docs/getting-started/](../../../docs/getting-started/) depending on topic. # Next.js Expert — Gotchas & Decisions Use Context7 for full Next.js docs. ## Key Decisions ```toon decisions[4]{choice,use_when}: Server vs Client,"Server by default. 'use client' ONLY for interactivity (useState/onClick). Push boundary as low as possible" Cache strategy,"force-cache (static) | revalidate:N (time) | revalidateTag (on-demand) | no-store (always fresh)" Server Actions vs API routes,"Actions for form mutations. API routes for external consumers/webhooks" Streaming vs blocking,"Suspense wrap for slow data. Always Promise.all for parallel fetches" ``` ## Gotchas - Server Components can't use useState/useEffect — move interactive parts to a child Client Component - `'use client'` makes ALL imports in that file client-side — keep it at leaf components - `fetch()` in Server Components is auto-deduped but only within same render pass - Server Actions: always validate with Zod — formData comes from untrusted client - `error.tsx` MUST be a Client Component (`'use client'`). `global-error.tsx` must render `<html>` and `<body>` - `loading.tsx` wraps page in Suspense — don't double-wrap with manual Suspense - Dynamic routes `[slug]`: params are now a Promise in Next.js 15 —...

Details

Author
nguyenthienthanh
Repository
nguyenthienthanh/aura-frog
Created
8 months ago
Last Updated
today
Language
JavaScript
License
MIT

Integrates with

Next.js · Frontend

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Solid

nodejs-expert

Node.js gotchas and decision criteria. Covers async pitfalls, Express/NestJS patterns, and common mistakes.

24 Updated today
nguyenthienthanh
AI & Automation Solid

react-expert

React gotchas and decision criteria covering stale closure bugs in useEffect, conditional rendering traps (falsy 0/empty string), state management selection (useState vs Context vs Zustand vs TanStack Query), and hooks rules. Use when writing React components, debugging re-renders, choosing state management, or encountering useEffect infinite loops.

24 Updated today
nguyenthienthanh
Web & Frontend Listed

nextjs-expert

Expert Next.js 14+ developer specializing in App Router, React Server Components, Server Actions, TypeScript, and modern full-stack patterns. Use when building Next.js applications or debugging Next.js-specific issues.

2 Updated yesterday
Marine-softdrink524