nextjs▌

Complete SEO setup for Next.js 16+ apps with metadata, sitemaps, robots.txt, and Core Web Vitals guidance. \n \n Covers essential files (root metadata, dynamic sitemaps, robots configuration) with ready-to-use TypeScript examples for App Router \n Includes rendering strategy comparison (SSG, SSR, ISR, CSR) and Core Web Vitals targets (LCP, INP, CLS) for performance optimization \n Provides quick audit checklist, common mistakes to avoid, and dynamic metadata patterns for product pages and canoni

Specialized workflow for building React and Next.js 14+ applications with modern patterns including App Router, Server Components, TypeScript, and Tailwind CSS.

Evaluates Next.js App Router code against best practices for Server Components, Client Components, Server Actions, caching strategies, and production-readiness criteria. Produces actionable findings categorized by severity with concrete code examples. Delegates to typescript-software-architect-review agent for architectural analysis.

You are an expert in creating highly optimized and maintainable Next.js solutions adhering to best practices in performance, security, and clean architecture principles.

Comprehensive Next.js performance optimization covering Core Web Vitals, modern React patterns, and production-grade techniques. \n \n Covers Core Web Vitals optimization (LCP, INP, CLS), image/font optimization with next/image and next/font , and caching strategies using unstable_cache and revalidateTag \n Guides conversion of Client Components to Server Components, implementation of Suspense streaming for progressive loading, and bundle size reduction through code splitting \n Includes Next.js

Generate production-ready Chrome Web Store marketing screenshots (1280x800 PNG) for browser extensions.

Comprehensive performance optimization guide for Next.js 16 App Router applications, maintained by the Next.js Community. Contains 40 rules across 8 categories, prioritized by impact to guide automated refactoring and code generation.

$22

Build production-grade Next.js applications or systematically migrate existing frontends to Next.js + shadcn/ui following strict design principles and best practices.

Server Components by default, client interactivity on demand, with structured data fetching and caching strategies. \n \n Server Components handle data fetching and static content; Client Components ('use client') manage forms, state, and event handlers. Split responsibilities when both are needed. \n Data fetching uses static caching by default, with ISR (time-based revalidation) and dynamic (no-store) options for different freshness requirements. \n Routing relies on file conventions (page.tsx