## Next.js - Treat the repository's current Next.js and React versions, routing model, rendering model, and package manager as authoritative. - Preserve server and client component boundaries. Add `use client` only when browser APIs, state, effects, or client-only libraries require it. - Keep secrets, privileged data access, and server-only modules out of client bundles. - Preserve established route, layout, middleware, authentication, authorization, caching, revalidation, and error-handling conventions. - Validate request parameters, payloads, headers, cookies, and external responses at runtime. - Do not create new frontend TypeScript type or interface names ending in `Dto` or `DTO`. Use domain- or purpose-specific names such as `User`, `UserInput`, `UserRequest`, or `UserResponse`; do not rename existing types solely to enforce this rule outside the approved scope. - Use the approved KRI frontend and UI contracts when the project profile includes them; do not copy shared implementations into an application. - Avoid incidental routing-model or rendering-strategy migrations. - Run the repository's focused lint, type-check, test, and production build commands as applicable.