Next.js NestJS Integration

Use this skill when a project has both a Next.js app and a NestJS API. The main job is to keep ownership boundaries clear so the web app does not accidentally duplicate backend policy, bypass API contracts, or self-fetch at build time.

When to Apply

Use this skill when:

• Generating or consuming typed clients from a NestJS OpenAPI document
• Deciding whether logic belongs in Next.js Route Handlers/Server Actions or NestJS controllers/services
• Propagating auth/session context from Next.js to NestJS
• Configuring CORS, cookies, Proxy, rewrites, or internal API origins
• Fetching NestJS data from Server Components without calling the Next.js app's own Route Handlers
• Aligning Docker, environment variables, health checks, and deployment topology across apps

Load On Demand

Start with this file. Load detailed files only when the task needs them: