nextjs

어떤 스킬인가요?

Guidance for Next.js using the official docs at nextjs.org/docs. Use when the user needs Next.js concepts, configuration, routing, data fetching, or API reference details.

설치 방법

프로젝트 폴더에서 아래 명령어를 실행하고, 설치할 에이전트를 선택하세요.

설치 명령을 직접 실행해야 적용됩니다. 지원 에이전트와 필요한 권한·라이선스는 제작자의 안내를 확인하세요.

스킬 원문 파일

## Instructions

- Use this page as the authoritative reference for **app / api-reference / cli / create-next-app**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/cli/create-next-app

## Instructions

- Use this page as the authoritative reference for **app / api-reference / cli / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/cli

## Instructions

- Use this page as the authoritative reference for **app / api-reference / cli / next**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/cli/next

## Instructions

- Use this page as the authoritative reference for **app / api-reference / components / font**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/components/font

## Instructions

- Use this page as the authoritative reference for **app / api-reference / components / form**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/components/form

## Instructions

- Use this page as the authoritative reference for **app / api-reference / components / image**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/components/image

## Instructions

- Use this page as the authoritative reference for **app / api-reference / components / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/components

## Instructions

- Use this page as the authoritative reference for **app / api-reference / components / link**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/components/link

## Instructions

- Use this page as the authoritative reference for **app / api-reference / components / script**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/components/script

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / eslint**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/eslint

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / adapterPath**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/adapterPath

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / allowedDevOrigins**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/allowedDevOrigins

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / appDir**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/appDir

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / assetPrefix**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/assetPrefix

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / authInterrupts**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/authInterrupts

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / basePath**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/basePath

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / browserDebugInfoInTerminal**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/browserDebugInfoInTerminal

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / cacheComponents**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheComponents

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / cacheHandlers**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheHandlers

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / cacheLife**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/cacheLife

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / compress**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/compress

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / crossOrigin**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/crossOrigin

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / cssChunking**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/cssChunking

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / devIndicators**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/devIndicators

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / distDir**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/distDir

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / env**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/env

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / expireTime**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/expireTime

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / exportPathMap**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/exportPathMap

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / generateBuildId**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/generateBuildId

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / generateEtags**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/generateEtags

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / headers**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/headers

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / htmlLimitedBots**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/htmlLimitedBots

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / httpAgentOptions**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/httpAgentOptions

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / images**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/images

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / incrementalCacheHandlerPath**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/incrementalCacheHandlerPath

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / inlineCss**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/inlineCss

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / isolatedDevBuild**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/isolatedDevBuild

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / logging**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/logging

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / mdxRs**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/mdxRs

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / onDemandEntries**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/onDemandEntries

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / optimizePackageImports**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/optimizePackageImports

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / output**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/output

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / pageExtensions**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/pageExtensions

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / poweredByHeader**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/poweredByHeader

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / productionBrowserSourceMaps**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/productionBrowserSourceMaps

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / proxyClientMaxBodySize**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/proxyClientMaxBodySize

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / reactCompiler**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/reactCompiler

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / reactMaxHeadersLength**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/reactMaxHeadersLength

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / reactStrictMode**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/reactStrictMode

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / redirects**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/redirects

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / rewrites**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/rewrites

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / sassOptions**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/sassOptions

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / serverActions**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/serverActions

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / serverComponentsHmrCache**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/serverComponentsHmrCache

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / serverExternalPackages**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/serverExternalPackages

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / staleTimes**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/staleTimes

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / staticGeneration**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/staticGeneration

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / taint**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/taint

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / trailingSlash**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/trailingSlash

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / transpilePackages**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/transpilePackages

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / turbopack**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / turbopackFileSystemCache**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopackFileSystemCache

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / typedRoutes**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/typedRoutes

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / typescript**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/typescript

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / urlImports**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/urlImports

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / useLightningcss**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/useLightningcss

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / viewTransition**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/viewTransition

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / webpack**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/webpack

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / next-config-js / webVitalsAttribution**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/next-config-js/webVitalsAttribution

## Instructions

- Use this page as the authoritative reference for **app / api-reference / config / typescript**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/config/typescript

## Instructions

- Use this page as the authoritative reference for **app / api-reference / directives / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/directives

## Instructions

- Use this page as the authoritative reference for **app / api-reference / directives / use-cache-private**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/directives/use-cache-private

## Instructions

- Use this page as the authoritative reference for **app / api-reference / directives / use-cache-remote**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/directives/use-cache-remote

## Instructions

- Use this page as the authoritative reference for **app / api-reference / directives / use-cache**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/directives/use-cache

## Instructions

- Use this page as the authoritative reference for **app / api-reference / directives / use-client**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/directives/use-client

## Instructions

- Use this page as the authoritative reference for **app / api-reference / directives / use-server**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/directives/use-server

## Instructions

- Use this page as the authoritative reference for **app / api-reference / edge**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/edge

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / default**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/default

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / dynamic-routes**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/dynamic-routes

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / error**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/error

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / forbidden**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/forbidden

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / instrumentation-client**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/instrumentation-client

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / instrumentation**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/instrumentation

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / intercepting-routes**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/intercepting-routes

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / layout**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/layout

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / loading**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/loading

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / mdx-components**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/mdx-components

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / metadata / app-icons**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/app-icons

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / metadata / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/metadata

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / metadata / manifest**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/manifest

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / metadata / opengraph-image**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/opengraph-image

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / metadata / robots**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/robots

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / metadata / sitemap**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/metadata/sitemap

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / not-found**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/not-found

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / page**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/page

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / parallel-routes**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/parallel-routes

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / proxy**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/proxy

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / public-folder**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/public-folder

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / route-groups**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/route-groups

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / route-segment-config**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/route-segment-config

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / route**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/route

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / src-folder**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/src-folder

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / template**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/template

## Instructions

- Use this page as the authoritative reference for **app / api-reference / file-conventions / unauthorized**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/file-conventions/unauthorized

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / after**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/after

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / cacheLife**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/cacheLife

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / cacheTag**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/cacheTag

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / connection**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/connection

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / cookies**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/cookies

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / draft-mode**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/draft-mode

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / fetch**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/fetch

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / forbidden**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/forbidden

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / generate-image-metadata**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/generate-image-metadata

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / generate-metadata**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/generate-metadata

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / generate-sitemaps**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/generate-sitemaps

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / generate-static-params**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/generate-static-params

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / generate-viewport**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/generate-viewport

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / headers**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/headers

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / image-response**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/image-response

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / next-request**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/next-request

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / next-response**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/next-response

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / not-found**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/not-found

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / permanentRedirect**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/permanentRedirect

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / redirect**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/redirect

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / refresh**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/refresh

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / revalidatePath**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/revalidatePath

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / revalidateTag**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/revalidateTag

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / unauthorized**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/unauthorized

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / unstable_cache**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/unstable_cache

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / unstable_noStore**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/unstable_noStore

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / unstable_rethrow**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/unstable_rethrow

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / updateTag**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/updateTag

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-link-status**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-link-status

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-params**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-params

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-pathname**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-pathname

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-report-web-vitals**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-report-web-vitals

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-router**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-router

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-search-params**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-search-params

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-selected-layout-segment**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-selected-layout-segment

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / use-selected-layout-segments**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/use-selected-layout-segments

## Instructions

- Use this page as the authoritative reference for **app / api-reference / functions / userAgent**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/functions/userAgent

## Instructions

- Use this page as the authoritative reference for **app / api-reference / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference

## Instructions

- Use this page as the authoritative reference for **app / api-reference / turbopack**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/api-reference/turbopack

## Instructions

- Use this page as the authoritative reference for **app / getting-started / cache-components**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/cache-components

## Instructions

- Use this page as the authoritative reference for **app / getting-started / caching-and-revalidating**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/caching-and-revalidating

## Instructions

- Use this page as the authoritative reference for **app / getting-started / css**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/css

## Instructions

- Use this page as the authoritative reference for **app / getting-started / deploying**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/deploying

## Instructions

- Use this page as the authoritative reference for **app / getting-started / error-handling**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/error-handling

## Instructions

- Use this page as the authoritative reference for **app / getting-started / fetching-data**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/fetching-data

## Instructions

- Use this page as the authoritative reference for **app / getting-started / fonts**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/fonts

## Instructions

- Use this page as the authoritative reference for **app / getting-started / images**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/images

## Instructions

- Use this page as the authoritative reference for **app / getting-started / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started

## Instructions

- Use this page as the authoritative reference for **app / getting-started / installation**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/installation

## Instructions

- Use this page as the authoritative reference for **app / getting-started / layouts-and-pages**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/layouts-and-pages

## Instructions

- Use this page as the authoritative reference for **app / getting-started / linking-and-navigating**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/linking-and-navigating

## Instructions

- Use this page as the authoritative reference for **app / getting-started / metadata-and-og-images**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/metadata-and-og-images

## Instructions

- Use this page as the authoritative reference for **app / getting-started / project-structure**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/project-structure

## Instructions

- Use this page as the authoritative reference for **app / getting-started / proxy**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/proxy

## Instructions

- Use this page as the authoritative reference for **app / getting-started / route-handlers**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/route-handlers

## Instructions

- Use this page as the authoritative reference for **app / getting-started / server-and-client-components**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/server-and-client-components

## Instructions

- Use this page as the authoritative reference for **app / getting-started / updating-data**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/updating-data

## Instructions

- Use this page as the authoritative reference for **app / getting-started / upgrading**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/getting-started/upgrading

## Instructions

- Use this page as the authoritative reference for **app / guides / analytics**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/analytics

## Instructions

- Use this page as the authoritative reference for **app / guides / authentication**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/authentication

## Instructions

- Use this page as the authoritative reference for **app / guides / backend-for-frontend**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/backend-for-frontend

## Instructions

- Use this page as the authoritative reference for **app / guides / caching**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/caching

## Instructions

- Use this page as the authoritative reference for **app / guides / ci-build-caching**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/ci-build-caching

## Instructions

- Use this page as the authoritative reference for **app / guides / content-security-policy**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/content-security-policy

## Instructions

- Use this page as the authoritative reference for **app / guides / css-in-js**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/css-in-js

## Instructions

- Use this page as the authoritative reference for **app / guides / custom-server**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/custom-server

## Instructions

- Use this page as the authoritative reference for **app / guides / data-security**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/data-security

## Instructions

- Use this page as the authoritative reference for **app / guides / debugging**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/debugging

## Instructions

- Use this page as the authoritative reference for **app / guides / draft-mode**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/draft-mode

## Instructions

- Use this page as the authoritative reference for **app / guides / environment-variables**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/environment-variables

## Instructions

- Use this page as the authoritative reference for **app / guides / forms**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/forms

## Instructions

- Use this page as the authoritative reference for **app / guides / incremental-static-regeneration**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/incremental-static-regeneration

## Instructions

- Use this page as the authoritative reference for **app / guides / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides

## Instructions

- Use this page as the authoritative reference for **app / guides / instrumentation**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/instrumentation

## Instructions

- Use this page as the authoritative reference for **app / guides / internationalization**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/internationalization

## Instructions

- Use this page as the authoritative reference for **app / guides / json-ld**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/json-ld

## Instructions

- Use this page as the authoritative reference for **app / guides / lazy-loading**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/lazy-loading

## Instructions

- Use this page as the authoritative reference for **app / guides / local-development**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/local-development

## Instructions

- Use this page as the authoritative reference for **app / guides / mcp**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/mcp

## Instructions

- Use this page as the authoritative reference for **app / guides / mdx**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/mdx

## Instructions

- Use this page as the authoritative reference for **app / guides / memory-usage**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/memory-usage

## Instructions

- Use this page as the authoritative reference for **app / guides / migrating / app-router-migration**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/migrating/app-router-migration

## Instructions

- Use this page as the authoritative reference for **app / guides / migrating / from-create-react-app**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/migrating/from-create-react-app

## Instructions

- Use this page as the authoritative reference for **app / guides / migrating / from-vite**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/migrating/from-vite

## Instructions

- Use this page as the authoritative reference for **app / guides / migrating / index / index**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/migrating

## Instructions

- Use this page as the authoritative reference for **app / guides / multi-tenant**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/multi-tenant

## Instructions

- Use this page as the authoritative reference for **app / guides / multi-zones**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/multi-zones

## Instructions

- Use this page as the authoritative reference for **app / guides / open-telemetry**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/open-telemetry

## Instructions

- Use this page as the authoritative reference for **app / guides / package-bundling**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/package-bundling

## Instructions

- Use this page as the authoritative reference for **app / guides / prefetching**.
- Follow the official Next.js docs for supported APIs and patterns.
- Keep examples aligned with the section indicated by the path (App Router / Pages Router / Architecture / Community).

## Parameters

- Identify the key inputs or configuration options referenced by this page.
- Use the official docs to verify required vs optional fields.
- Prefer exact naming and casing from the documentation.

## Returns

- Describe expected behavior or output for the documented feature.
- If the page is conceptual, summarize the expected result or effect.

## Common Errors

- Mismatched configuration keys or invalid values.
- Using App Router APIs inside Pages Router (or vice versa).
- Skipping required runtime or environment setup.

## Best Practices

- Use official patterns and recommended defaults.
- Keep routing and data-fetching patterns consistent across the app.
- Validate changes against the official docs and examples.

## Scenarios

### Typical usage

- Identify the common use case for this page/topic.
- Apply the official steps and validate expected behavior.

### Troubleshooting

- Cross-check config and runtime requirements.
- Review the official page for edge cases and constraints.

Reference: https://nextjs.org/docs/app/guides/prefetching

                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

---
name: nextjs
description: Guidance for Next.js using the official docs at nextjs.org/docs. Use when the user needs Next.js concepts, configuration, routing, data fetching, or API reference details.
license: Complete terms in LICENSE.txt
---

## When to use this skill

Use this skill whenever the user wants to:
- Follow Next.js documentation topics (App Router, Pages Router, architecture, community)
- Implement Next.js routing, data fetching, caching, or deployment
- Use official APIs and configuration options from the docs

## How to use this skill

1. **Identify the topic** from the user request.
2. **Open the matching example file** in `examples/`.
3. **Follow the official Next.js docs** linked in the file.

## Mapping Rules (one-to-one with https://nextjs.org/docs)

The `examples/` directory mirrors the official docs structure:

- `examples/index.md` → https://nextjs.org/docs
- `examples/app/...` → https://nextjs.org/docs/app/...
- `examples/pages/...` → https://nextjs.org/docs/pages/...
- `examples/architecture/...` → https://nextjs.org/docs/architecture/...
- `examples/community/...` → https://nextjs.org/docs/community/...

**Path rule:**
- Remove numeric prefixes from doc folders and filenames (e.g., `01-app` → `app`).
- `index.mdx` pages map to `index.md` inside the corresponding directory.

## Resources
- Docs: https://nextjs.org/docs

## Keywords
Next.js, App Router, Pages Router, routing, data fetching, caching, server components, client components, middleware, deployment, configuration

## 国内适配

- 支持中文文档和中文注释
- 示例代码兼容国内开发环境
- 提供中文 FAQ 和常见问题解答

## 能力边界

### ✅ 适用场景
- 当你需要使用此技能对应的技术栈时
- 当项目需要遵循最佳实践时
- 当需要快速上手或深入理解核心概念时

### ⚠️ 需要注意
- 复杂业务逻辑需要结合具体场景调整
- 性能优化需要根据实际数据量评估

### ❌ 不适用场景
- 不相关的技术栈或框架
- 需要完全自定义的特殊场景

## 使用流程

### Step 1: 环境准备
确保开发环境已安装必要的依赖和工具。

### Step 2: 配置初始化
根据项目需求进行基础配置。

### Step 3: 核心功能使用
按照示例代码实现核心功能。

### Step 4: 测试验证
运行测试确保功能正常。

### Step 5: 部署上线
完成开发后进行部署和监控。