Next.js

Workflow

1. Confirm Next.js version, router mode, and deployment target.
2. Define routing architecture and data boundaries before implementation.
3. Choose rendering and caching strategy per route.
4. Implement mutation and state patterns with minimal complexity.
5. Optimize performance budgets and asset delivery.
6. Validate SEO, accessibility, and security posture.
7. Ship with reproducible CI/CD and observability.
8. Document migration steps for router/runtime/tooling changes.

Preflight (Ask / Check First)

• App Router, Pages Router, or mixed mode in current codebase.
• Hosting platform constraints and edge/runtime requirements.
• Server-side data sources and caching expectations.
• Authentication/session strategy and sensitive-data boundaries.
• Performance goals (LCP, INP, TTFB) and SEO priorities.
• Monorepo tooling and package manager standards.