nextjs-app-router-patterns
Next.js App Router Patterns
Overview
Reference guide for idiomatic Next.js 14+ App Router patterns. Apply these when building pages, layouts, and data flows to fully leverage server components, streaming, and the caching system.
Server vs Client Component Decision Tree
Does the component need...
├── Browser APIs (window, localStorage, navigator)?
│ └── YES → "use client"
├── Event listeners (onClick, onChange, onSubmit)?
│ └── YES → "use client"
├── useState, useEffect, useRef, or custom hooks?
│ └── YES → "use client"
├── Only data fetching and rendering?
│ └── YES → Server Component (default) ✓
├── Third-party library that uses hooks or browser APIs?
More from generaljerel/chalk-skills
python-clean-architecture
Clean architecture patterns for Python services — service layer, repository pattern, domain models, dependency injection, error hierarchy, and testing strategy
23create-handoff
Generate a handoff document after implementation work is complete — summarizes changes, risks, and review focus areas for the review pipeline. Use when done coding and ready to hand off for review.
16create-review
Bootstrap a local AI review pipeline and generate a paste-ready review prompt for any reviewer agent. Use after creating a handoff or when ready to get an AI code review.
15fix-findings
Fix findings from the active review session — reads reviewer findings files, applies fixes by priority, and updates the resolution log. Use after pasting reviewer output into findings files.
15fix-review
When the user asks to fix, address, or work on PR review comments — fetch review comments from a GitHub pull request and apply fixes to the local codebase. Requires gh CLI.
15review-changes
End-to-end review pipeline — creates a handoff, generates a review (self-review or paste-ready for another provider), then offers to fix findings. Use when you want to review your changes before pushing.
13