[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FEW7AXRMNDWJHD9PV6YEW7":3,"skill-same:01M7FEW7AXRMNDWJHD9PV6YEW7":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7FEW7AXRMNDWJHD9PV6YEW7","nextjs-app-router-patterns",null,"Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR\u002FSSG, or optimizing React Server Components.","heynemann\u002Fdotfiles-stow","heynemann","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F60965?v=4","01M7DFBD9ZDB2J2QE7R4AR0PES","Bernardo Heynemann","01M7FERV0J6GMQ0RHEH6EHGYRW",0,"MIT","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fnextjs-app-router-patterns\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: nextjs-app-router-patterns\ndescription: Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR\u002FSSG, or optimizing React Server Components.\n---\n\n# Next.js App Router Patterns\n\nComprehensive patterns for Next.js 14+ App Router architecture, Server Components, and modern full-stack React development.\n\n## When to Use This Skill\n\n- Building new Next.js applications with App Router\n- Migrating from Pages Router to App Router\n- Implementing Server Components and streaming\n- Setting up parallel and intercepting routes\n- Optimizing data fetching and caching\n- Building full-stack features with Server Actions\n\n## Core Concepts\n\n### 1. Rendering Modes\n\n| Mode                  | Where        | When to Use                               |\n| --------------------- | ------------ | ----------------------------------------- |\n| **Server Components** | Server only  | Data fetching, heavy computation, secrets |\n| **Client Components** | Browser      | Interactivity, hooks, browser APIs        |\n| **Static**            | Build time   | Content that rarely changes               |\n| **Dynamic**           | Request time | Personalized or real-time data            |\n| **Streaming**         | Progressive  | Large pages, slow data sources            |\n\n### 2. File Conventions\n\n```\napp\u002F\n├── layout.tsx       # Shared UI wrapper\n├── page.tsx         # Route UI\n├── loading.tsx      # Loading UI (Suspense)\n├── error.tsx        # Error boundary\n├── not-found.tsx    # 404 UI\n├── route.ts         # API endpoint\n├── template.tsx     # Re-mounted layout\n├── default.tsx      # Parallel route fallback\n└── opengraph-image.tsx  # OG image generation\n```\n\n## Quick Start\n\n```typescript\n\u002F\u002F app\u002Flayout.tsx\nimport { Inter } from 'next\u002Ffont\u002Fgoogle'\nimport { Providers } from '.\u002Fproviders'\n\nconst inter = Inter({ subsets: ['latin'] })\n\nexport const metadata = {\n  title: { default: 'My App', template: '%s | My App' },\n  description: 'Built with Next.js App Router',\n}\n\nexport default function RootLayout({\n  children,\n}: {\n  children: React.ReactNode\n}) {\n  return (\n    \u003Chtml lang=\"en\" suppressHydrationWarning>\n      \u003Cbody className={inter.className}>\n        \u003CProviders>{children}\u003C\u002FProviders>\n      \u003C\u002Fbody>\n    \u003C\u002Fhtml>\n  )\n}\n\n\u002F\u002F app\u002Fpage.tsx - Server Component by default\nasync function getProducts() {\n  const res = await fetch('https:\u002F\u002Fapi.example.com\u002Fproducts', {\n    next: { revalidate: 3600 }, \u002F\u002F ISR: revalidate every hour\n  })\n  return res.json()\n}\n\nexport default async function HomePage() {\n  const products = await getProducts()\n\n  return (\n    \u003Cmain>\n      \u003Ch1>Products\u003C\u002Fh1>\n      \u003CProductGrid products={products} \u002F>\n    \u003C\u002Fmain>\n  )\n}\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Best Practices\n\n### Do's\n\n- **Start with Server Components** - Add 'use client' only when needed\n- **Colocate data fetching** - Fetch data where it's used\n- **Use Suspense boundaries** - Enable streaming for slow data\n- **Leverage parallel routes** - Independent loading states\n- **Use Server Actions** - For mutations with progressive enhancement\n\n### Don'ts\n\n- **Don't pass serializable data** - Server → Client boundary limitations\n- **Don't use hooks in Server Components** - No useState, useEffect\n- **Don't fetch in Client Components** - Use Server Components or React Query\n- **Don't over-nest layouts** - Each layout adds to the component tree\n- **Don't ignore loading states** - Always provide loading.tsx or Suspense\n","# Next.js App Router Patterns\n\nComprehensive patterns for Next.js 14+ App Router architecture, Server Components, and modern full-stack React development.\n\n## When to Use This Skill\n\n- Building new Next.js applications with App Router\n- Migrating from Pages Router to App Router\n- Implementing Server Components and streaming\n- Setting up parallel and intercepting routes\n- Optimizing data fetching and caching\n- Building full-stack features with Server Actions\n\n## Core Concepts\n\n### 1. Rendering Modes\n\n| Mode                  | Where        | When to Use                               |\n| --------------------- | ------------ | ----------------------------------------- |\n| **Server Components** | Server only  | Data fetching, heavy computation, secrets |\n| **Client Components** | Browser      | Interactivity, hooks, browser APIs        |\n| **Static**            | Build time   | Content that rarely changes               |\n| **Dynamic**           | Request time | Personalized or real-time data            |\n| **Streaming**         | Progressive  | Large pages, slow data sources            |\n\n### 2. File Conventions\n\n```\napp\u002F\n├── layout.tsx       # Shared UI wrapper\n├── page.tsx         # Route UI\n├── loading.tsx      # Loading UI (Suspense)\n├── error.tsx        # Error boundary\n├── not-found.tsx    # 404 UI\n├── route.ts         # API endpoint\n├── template.tsx     # Re-mounted layout\n├── default.tsx      # Parallel route fallback\n└── opengraph-image.tsx  # OG image generation\n```\n\n## Quick Start\n\n```typescript\n\u002F\u002F app\u002Flayout.tsx\nimport { Inter } from 'next\u002Ffont\u002Fgoogle'\nimport { Providers } from '.\u002Fproviders'\n\nconst inter = Inter({ subsets: ['latin'] })\n\nexport const metadata = {\n  title: { default: 'My App', template: '%s | My App' },\n  description: 'Built with Next.js App Router',\n}\n\nexport default function RootLayout({\n  children,\n}: {\n  children: React.ReactNode\n}) {\n  return (\n    \u003Chtml lang=\"en\" suppressHydrationWarning>\n      \u003Cbody className={inter.className}>\n        \u003CProviders>{children}\u003C\u002FProviders>\n      \u003C\u002Fbody>\n    \u003C\u002Fhtml>\n  )\n}\n\n\u002F\u002F app\u002Fpage.tsx - Server Component by default\nasync function getProducts() {\n  const res = await fetch('https:\u002F\u002Fapi.example.com\u002Fproducts', {\n    next: { revalidate: 3600 }, \u002F\u002F ISR: revalidate every hour\n  })\n  return res.json()\n}\n\nexport default async function HomePage() {\n  const products = await getProducts()\n\n  return (\n    \u003Cmain>\n      \u003Ch1>Products\u003C\u002Fh1>\n      \u003CProductGrid products={products} \u002F>\n    \u003C\u002Fmain>\n  )\n}\n```\n\n## Detailed patterns and worked examples\n\nDetailed pattern documentation lives in `references\u002Fdetails.md`. Read that file when the navigation tier above is insufficient.\n\n## Best Practices\n\n### Do's\n\n- **Start with Server Components** - Add 'use client' only when needed\n- **Colocate data fetching** - Fetch data where it's used\n- **Use Suspense boundaries** - Enable streaming for slow data\n- **Leverage parallel routes** - Independent loading states\n- **Use Server Actions** - For mutations with progressive enhancement\n\n### Don'ts\n\n- **Don't pass serializable data** - Server → Client boundary limitations\n- **Don't use hooks in Server Components** - No useState, useEffect\n- **Don't fetch in Client Components** - Use Server Components or React Query\n- **Don't over-nest layouts** - Each layout adds to the component tree\n- **Don't ignore loading states** - Always provide loading.tsx or Suspense\n",{"name":5,"description":7},"main","e4d0a0940fd53fc8a3a1e1dcb967c0a18ea8ba0f","omp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fnextjs-app-router-patterns","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow","https:\u002F\u002Fgithub.com\u002Fheynemann","http:\u002F\u002Fwww.thumbor.org","CTO @ Flutter Brazil | Former Meta & Coinbase","2026-10-29 20:46:15",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add heynemann\u002Fdotfiles-stow --skill nextjs-app-router-patterns",{"tool":38,"command":39},"bunx","bunx skills add heynemann\u002Fdotfiles-stow --skill nextjs-app-router-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add heynemann\u002Fdotfiles-stow --skill nextjs-app-router-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fnextjs-app-router-patterns\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fdetails.md","REFERENCE","参考文档",9939,"https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Fdoordash\u002Fskills-sh\u002F.agents\u002Fskills\u002Fnextjs-app-router-patterns\u002Freferences\u002Fdetails.md",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFA0PAN04C2DVK6A7CXK6K","unity-scriptableobjects","Architect Unity 6.3 LTS data and decoupling with ScriptableObjects: config\u002Fdata assets, shared runtime variables, event channels, and runtime sets\u002Fregistries. Use when designing data-driven systems, replacing singletons\u002Fmanagers, creating .asset data with CreateAssetMenu, or when the user mentions ScriptableObject, SO architecture, or data assets.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-scriptableobjects\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7FF9SPKA8BC4EGCHJGGJK5P","unity-package-management","Adds, removes, upgrades, and discovers Unity (UPM) packages from outside the Editor. Use for headless or CI package installs, verifying package IDs and versions, or choosing which packages a game needs. The Unity CLI doesn't manage packages.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-package-management\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7FF9KBCKR352R6ZSY2BB2J3","unity-input-system","Wire player input in Unity 6.3 LTS with the Input System package: Input Actions, action maps, the PlayerInput component, and reading values via callbacks or polling. Use when the project has a .inputactions asset or com.unity.inputsystem, or when the user mentions the Unity Input System, InputAction, action maps, PlayerInput, control schemes, or rebinding.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-input-system\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7FF9FREKNGB4PQP8ZHTN1D8","unity-ecs-patterns","Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-ecs-patterns\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7FF99B1DV7RDAY98QVFFMA9","unity-csharp-scripting","Write Unity 6.3 LTS C# gameplay scripts: the MonoBehaviour lifecycle (Awake\u002FOnEnable\u002FStart\u002FUpdate\u002FFixedUpdate\u002FLateUpdate), GameObject and component access, coroutines, and Inspector serialization. Use when creating or editing .cs scripts in a Unity project, or when the user mentions MonoBehaviour, Start\u002FUpdate, GetComponent, SerializeField, coroutines, or \"Unity script\".","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-csharp-scripting\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7FF8ZK7PAPR4QZ44SY9ZDAJ","unity-cli","Controls the Unity Editor and projects from the command line, driving a running Editor to edit scenes and assets or run C#. Use when asked to install or manage Editors, licenses, or projects, set up version control, build, test, configure the Unity MCP server, or run any unity command.","https:\u002F\u002Fgithub.com\u002Fheynemann\u002Fdotfiles-stow\u002Fblob\u002Fmain\u002Fomp\u002F.omp\u002Fprofiles\u002Funity\u002Fskills-sh\u002F.agents\u002Fskills\u002Funity-cli\u002FSKILL.md",[],[]]