Nextjs
- 17 installs
- 1 repo stars
- Updated July 29, 2026
- full-statck-skills/react-skills
Build Next.js applications using the App Router, CLI, and create-next-app, following official Next.js APIs and patterns.
About
Provides an authoritative reference to Next.js App Router, CLI, and API following official docs. A developer uses it when building or configuring a Next.js application.
- Authoritative reference for App Router, api-reference, cli, and create-next-app
- Follows official Next.js docs for supported APIs and patterns
Nextjs by the numbers
- 17 all-time installs (skills.sh)
- Ranked #1,582 of 2,245 Frontend Development skills by installs in the Skillselion catalog
- Data as of Jul 30, 2026 (Skillselion catalog sync)
npx skills add https://github.com/full-statck-skills/react-skills --skill nextjsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 17 |
|---|---|
| repo stars | ★ 1 |
| Last updated | July 29, 2026 |
| Repository | full-statck-skills/react-skills ↗ |
What it does
Build Next.js applications using the App Router, CLI, and create-next-app, following official Next.js APIs and patterns.
Files
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
Related skills
Vercel React Best PracticesAutomatically apply Vercel’s official React and Next.js performance rules during code generation and review.587k29.6kVercel Composition PatternsGenerate and refactor React components that stay maintainable as complexity grows without boolean prop explosion.267k29.6k
ShadcnAdd, compose, search, fix, and style production-grade React components directly from source without leaving their editor.257k120k
Develop UserscriptsCorrectly write, debug, and package userscripts for Tampermonkey and ScriptCat with proper metadata, GM APIs, and runtime decisions.224k72
Minimalist UiGenerate clean, editorial-style web interfaces with warm monochrome palettes, typographic hierarchy, bento grids and flat components that feel premium and utilita212k69.4kImage To CodeConvert high-fidelity design images into production-ready, visually accurate frontend code that avoids generic AI design pitfalls.177k69.4kFrontend Developmentfrontend