# Build Next.js 16 Apps

Next.js 16 migrations include breaking routing, caching, and tooling changes. This skill gives focused workflows, starter assets, and review checklists for modern App Router projects.

## Install

```bash
npx skillstore add calel33/next-js-16-launchpad
```

## Metadata

- - Slug: calel33-next-js-16-launchpad
- - Version: 1.1.0
- - Author: Calel33
- - GitHub username: Calel33
- - License: MIT
- - Repository: https://github.com/Calel33/my-flash-ui-app--1-/tree/main/skills/nextjs16-core
- - Ref: main
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: medium
- - Risk factors: scripts, network, env\_access, external\_commands
- - Quality score: 50
- - Quality tier: warning
- - Public page: https://skillstore.pages.dev/skills/calel33-next-js-16-launchpad
- - Manifest: https://skillstore.pages.dev/api/skills/calel33-next-js-16-launchpad/manifest

## Capabilities

- Explains Next.js 16 setup requirements for Node.js, TypeScript, React, and App Router projects.
- Provides migration guidance for async request APIs, middleware to proxy.ts, and removed config flags.
- Documents Cache Components patterns with use cache, cacheLife, cacheTag, Suspense, and revalidation guidance.
- Includes a starter App Router reference app with pages, dashboard routing, loading, error, and proxy examples.
- Supplies a PowerShell bootstrap script for installing packages and creating a recommended Next.js project.
- Highlights common pitfalls for Turbopack, images, runtime request data, and deployment settings.

## Use Cases

- Start a new App Router project: Create a Next.js 16 baseline with Turbopack, TypeScript, Tailwind, and App Router defaults.
- Plan a version upgrade: Map required changes from Next.js 15 to Next.js 16 before assigning migration work.
- Review caching and routing patterns: Check Cache Components, Suspense boundaries, proxy.ts auth, and data fetching patterns for correctness.

## Prompt Templates

### Create a Next.js 16 starter plan

```
Use next-js-16-launchpad to outline a new Next.js 16 project setup with TypeScript, App Router, Turbopack, Tailwind, and basic folder structure.
```

### Upgrade my project checklist

```
Use next-js-16-launchpad to create a migration checklist for upgrading my Next.js 15 App Router project to Next.js 16.
```

### Review caching architecture

```
Use next-js-16-launchpad to review my Cache Components design, Suspense boundaries, revalidation strategy, and runtime data handling.
```

### Design a production route pattern

```
Use next-js-16-launchpad to design a production dashboard pattern with proxy.ts auth, parallel data fetching, Cache Components, and deployment checks.
```

## Limitations

- The guide targets Next.js 16 and may not fit Pages Router or older Next.js projects.
- The bootstrap script runs package-manager commands and should be reviewed before execution.
- Example API URLs and auth snippets are illustrative and must be replaced for production use.
- The skill does not validate third-party package security or project-specific dependency risk.

## Best Practices

- Review the bootstrap script before running it because it installs packages and creates project files.
- Replace sample API endpoints, cookie names, and JWT examples with production-approved services and secrets handling.
- Use the migration checklist with tests for routing, caching, image handling, and Turbopack build behavior.

## Anti Patterns

- Do not run the PowerShell bootstrap script in a sensitive repository without reviewing the package commands first.
- Do not copy sample auth snippets directly into production without validation, rotation, and secure cookie settings.
- Do not enable Cache Components around cookies, headers, or other runtime request data.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T19:59:34.404\+00:00
- - Summary: Static analysis reported many command, network, environment, and sensitive-data patterns, but most are Markdown examples or public starter-code samples. No prompt injection, credential exfiltration, obfuscation, or confirmed malicious intent was found. The skill should publish with a medium warning because the included PowerShell bootstrap script and documented commands execute package-manager operations when users run them.

## Stats

- - Views: 246
- - Downloads: 28
- - Favorites: 0
- - Popularity score: 0