[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ED1PQ050DPVBS0S1QJ76ZK":3,"skill-same:01M7ED1PQ050DPVBS0S1QJ76ZK":70},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7ED1PQ050DPVBS0S1QJ76ZK","netlify-functions",null,"编写 Netlify Serverless 函数的指南。在创建 API 端点、后台处理、计划任务，或任何使用 Netlify Functions 的服务端逻辑时使用。涵盖现代语法（默认导出 + Config）、TypeScript、路径路由、后台函数、计划函数、流式传输和方法路由。","kael-odin\u002Fcodex-plugins-zh","kael-odin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F166499071?v=4","01M7EBHJT87XN88WT3PEQ8ZGZK","Kael Odin","01M7EBHJVC91GD7PGJN3ZB14SG",37,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: netlify-functions\ndescription: \"编写 Netlify Serverless 函数的指南。在创建 API 端点、后台处理、计划任务，或任何使用 Netlify Functions 的服务端逻辑时使用。涵盖现代语法（默认导出 + Config）、TypeScript、路径路由、后台函数、计划函数、流式传输和方法路由。\"\r\n---\r\n\r\n# Netlify Functions\r\n\r\n## Modern Syntax\r\n\r\nAlways use the modern default export + Config pattern. Never use the legacy `exports.handler` or named `handler` export.\r\n\r\n```typescript\r\nimport type { Context, Config } from \"@netlify\u002Ffunctions\";\r\n\r\nexport default async (req: Request, context: Context) => {\r\n  return new Response(\"Hello, world!\");\r\n};\r\n\r\nexport const config: Config = {\r\n  path: \"\u002Fapi\u002Fhello\",\r\n};\r\n```\r\n\r\nThe handler receives a standard Web API `Request` and returns a `Response`. The second argument is a Netlify `Context` object.\r\n\r\n## File Structure\r\n\r\nPlace functions in `netlify\u002Ffunctions\u002F`:\r\n\r\n```\r\nnetlify\u002Ffunctions\u002F\r\n  _shared\u002F           # Non-function shared code (underscore prefix)\r\n    auth.ts\r\n    db.ts\r\n  items.ts           # -> \u002F.netlify\u002Ffunctions\u002Fitems (or custom path via config)\r\n  users\u002Findex.ts     # -> \u002F.netlify\u002Ffunctions\u002Fusers\r\n```\r\n\r\nUse `.ts` or `.mts` extensions. If both `.ts` and `.js` exist with the same name, the `.js` file takes precedence.\r\n\r\n## Path Routing\r\n\r\nDefine custom paths via the `config` export:\r\n\r\n```typescript\r\nexport const config: Config = {\r\n  path: \"\u002Fapi\u002Fitems\",                    \u002F\u002F Static path\r\n  \u002F\u002F path: \"\u002Fapi\u002Fitems\u002F:id\",            \u002F\u002F Path parameter\r\n  \u002F\u002F path: [\"\u002Fapi\u002Fitems\", \"\u002Fapi\u002Fitems\u002F:id\"], \u002F\u002F Multiple paths\r\n  \u002F\u002F excludedPath: \"\u002Fapi\u002Fitems\u002Fspecial\", \u002F\u002F Excluded paths\r\n  \u002F\u002F preferStatic: true,                \u002F\u002F Don't override static files\r\n};\r\n```\r\n\r\nWithout a `path` config, functions are available at `\u002F.netlify\u002Ffunctions\u002F{name}`. Setting a `path` makes the function available **only** at that path.\r\n\r\nAccess path parameters via `context.params`:\r\n\r\n```typescript\r\n\u002F\u002F config: { path: \"\u002Fapi\u002Fitems\u002F:id\" }\r\nexport default async (req: Request, context: Context) => {\r\n  const { id } = context.params;\r\n  \u002F\u002F ...\r\n};\r\n```\r\n\r\n## Method Routing\r\n\r\n```typescript\r\nexport default async (req: Request, context: Context) => {\r\n  switch (req.method) {\r\n    case \"GET\":    return handleGet(context.params.id);\r\n    case \"POST\":   return handlePost(await req.json());\r\n    case \"DELETE\": return handleDelete(context.params.id);\r\n    default:       return new Response(\"Method not allowed\", { status: 405 });\r\n  }\r\n};\r\n\r\nexport const config: Config = {\r\n  path: \"\u002Fapi\u002Fitems\u002F:id\",\r\n  method: [\"GET\", \"POST\", \"DELETE\"],\r\n};\r\n```\r\n\r\n## Background Functions\r\n\r\nFor long-running tasks (up to 15 minutes). The client receives an immediate `202` response; return values are ignored.\r\n\r\nName the file with a `-background` suffix:\r\n\r\n```\r\nnetlify\u002Ffunctions\u002Fprocess-background.ts\r\n```\r\n\r\nStore results externally (Netlify Blobs, database) for later retrieval.\r\n\r\n## Scheduled Functions\r\n\r\nRun on a cron schedule (UTC timezone):\r\n\r\n```typescript\r\nexport default async (req: Request) => {\r\n  const { next_run } = await req.json();\r\n  console.log(\"Next invocation at:\", next_run);\r\n};\r\n\r\nexport const config: Config = {\r\n  schedule: \"@hourly\", \u002F\u002F or cron: \"0 * * * *\"\r\n};\r\n```\r\n\r\nShortcuts: `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`. Scheduled functions have a **30-second timeout** and only run on published deploys.\r\n\r\n## Streaming Responses\r\n\r\nReturn a `ReadableStream` body for streamed responses (up to 20 MB):\r\n\r\n```typescript\r\nexport default async (req: Request) => {\r\n  const stream = new ReadableStream({ \u002F* ... *\u002F });\r\n  return new Response(stream, {\r\n    headers: { \"Content-Type\": \"text\u002Fevent-stream\" },\r\n  });\r\n};\r\n```\r\n\r\n## Context Object\r\n\r\n| Property | Description |\r\n|---|---|\r\n| `context.params` | Path parameters from config |\r\n| `context.geo` | `{ city, country: {code, name}, latitude, longitude, subdivision, timezone, postalCode }` |\r\n| `context.ip` | Client IP address |\r\n| `context.cookies` | `.get()`, `.set()`, `.delete()` |\r\n| `context.deploy` | `{ context, id, published }` |\r\n| `context.site` | `{ id, name, url }` |\r\n| `context.account.id` | Team account ID |\r\n| `context.requestId` | Unique request ID |\r\n| `context.waitUntil(promise)` | Extend execution after response is sent |\r\n\r\n## Environment Variables\r\n\r\nUse `Netlify.env` (not `process.env`) inside functions:\r\n\r\n```typescript\r\nconst apiKey = Netlify.env.get(\"API_KEY\");\r\n```\r\n\r\n## Resource Limits\r\n\r\n| Resource | Limit |\r\n|---|---|\r\n| Synchronous timeout | 60 seconds |\r\n| Background timeout | 15 minutes |\r\n| Scheduled timeout | 30 seconds |\r\n| Memory | 1024 MB |\r\n| Buffered payload | 6 MB |\r\n| Streamed payload | 20 MB |\r\n\r\n## Framework Considerations\r\n\r\nFrameworks with server-side capabilities (Astro, Next.js, Nuxt, SvelteKit, TanStack Start) typically generate their own serverless functions via adapters. You usually do not write raw Netlify Functions in these projects — the framework adapter handles server-side rendering and API routes. Write Netlify Functions directly when:\r\n\r\n- Using a client-side-only framework (Vite + React SPA, vanilla JS)\r\n- Adding background or scheduled tasks to any project\r\n- Building standalone API endpoints outside the framework's routing\r\n\r\nSee the **netlify-frameworks** skill for adapter setup.\r\n","# Netlify Functions\r\n\r\n## Modern Syntax\r\n\r\nAlways use the modern default export + Config pattern. Never use the legacy `exports.handler` or named `handler` export.\r\n\r\n```typescript\r\nimport type { Context, Config } from \"@netlify\u002Ffunctions\";\r\n\r\nexport default async (req: Request, context: Context) => {\r\n  return new Response(\"Hello, world!\");\r\n};\r\n\r\nexport const config: Config = {\r\n  path: \"\u002Fapi\u002Fhello\",\r\n};\r\n```\r\n\r\nThe handler receives a standard Web API `Request` and returns a `Response`. The second argument is a Netlify `Context` object.\r\n\r\n## File Structure\r\n\r\nPlace functions in `netlify\u002Ffunctions\u002F`:\r\n\r\n```\r\nnetlify\u002Ffunctions\u002F\r\n  _shared\u002F           # Non-function shared code (underscore prefix)\r\n    auth.ts\r\n    db.ts\r\n  items.ts           # -> \u002F.netlify\u002Ffunctions\u002Fitems (or custom path via config)\r\n  users\u002Findex.ts     # -> \u002F.netlify\u002Ffunctions\u002Fusers\r\n```\r\n\r\nUse `.ts` or `.mts` extensions. If both `.ts` and `.js` exist with the same name, the `.js` file takes precedence.\r\n\r\n## Path Routing\r\n\r\nDefine custom paths via the `config` export:\r\n\r\n```typescript\r\nexport const config: Config = {\r\n  path: \"\u002Fapi\u002Fitems\",                    \u002F\u002F Static path\r\n  \u002F\u002F path: \"\u002Fapi\u002Fitems\u002F:id\",            \u002F\u002F Path parameter\r\n  \u002F\u002F path: [\"\u002Fapi\u002Fitems\", \"\u002Fapi\u002Fitems\u002F:id\"], \u002F\u002F Multiple paths\r\n  \u002F\u002F excludedPath: \"\u002Fapi\u002Fitems\u002Fspecial\", \u002F\u002F Excluded paths\r\n  \u002F\u002F preferStatic: true,                \u002F\u002F Don't override static files\r\n};\r\n```\r\n\r\nWithout a `path` config, functions are available at `\u002F.netlify\u002Ffunctions\u002F{name}`. Setting a `path` makes the function available **only** at that path.\r\n\r\nAccess path parameters via `context.params`:\r\n\r\n```typescript\r\n\u002F\u002F config: { path: \"\u002Fapi\u002Fitems\u002F:id\" }\r\nexport default async (req: Request, context: Context) => {\r\n  const { id } = context.params;\r\n  \u002F\u002F ...\r\n};\r\n```\r\n\r\n## Method Routing\r\n\r\n```typescript\r\nexport default async (req: Request, context: Context) => {\r\n  switch (req.method) {\r\n    case \"GET\":    return handleGet(context.params.id);\r\n    case \"POST\":   return handlePost(await req.json());\r\n    case \"DELETE\": return handleDelete(context.params.id);\r\n    default:       return new Response(\"Method not allowed\", { status: 405 });\r\n  }\r\n};\r\n\r\nexport const config: Config = {\r\n  path: \"\u002Fapi\u002Fitems\u002F:id\",\r\n  method: [\"GET\", \"POST\", \"DELETE\"],\r\n};\r\n```\r\n\r\n## Background Functions\r\n\r\nFor long-running tasks (up to 15 minutes). The client receives an immediate `202` response; return values are ignored.\r\n\r\nName the file with a `-background` suffix:\r\n\r\n```\r\nnetlify\u002Ffunctions\u002Fprocess-background.ts\r\n```\r\n\r\nStore results externally (Netlify Blobs, database) for later retrieval.\r\n\r\n## Scheduled Functions\r\n\r\nRun on a cron schedule (UTC timezone):\r\n\r\n```typescript\r\nexport default async (req: Request) => {\r\n  const { next_run } = await req.json();\r\n  console.log(\"Next invocation at:\", next_run);\r\n};\r\n\r\nexport const config: Config = {\r\n  schedule: \"@hourly\", \u002F\u002F or cron: \"0 * * * *\"\r\n};\r\n```\r\n\r\nShortcuts: `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`. Scheduled functions have a **30-second timeout** and only run on published deploys.\r\n\r\n## Streaming Responses\r\n\r\nReturn a `ReadableStream` body for streamed responses (up to 20 MB):\r\n\r\n```typescript\r\nexport default async (req: Request) => {\r\n  const stream = new ReadableStream({ \u002F* ... *\u002F });\r\n  return new Response(stream, {\r\n    headers: { \"Content-Type\": \"text\u002Fevent-stream\" },\r\n  });\r\n};\r\n```\r\n\r\n## Context Object\r\n\r\n| Property | Description |\r\n|---|---|\r\n| `context.params` | Path parameters from config |\r\n| `context.geo` | `{ city, country: {code, name}, latitude, longitude, subdivision, timezone, postalCode }` |\r\n| `context.ip` | Client IP address |\r\n| `context.cookies` | `.get()`, `.set()`, `.delete()` |\r\n| `context.deploy` | `{ context, id, published }` |\r\n| `context.site` | `{ id, name, url }` |\r\n| `context.account.id` | Team account ID |\r\n| `context.requestId` | Unique request ID |\r\n| `context.waitUntil(promise)` | Extend execution after response is sent |\r\n\r\n## Environment Variables\r\n\r\nUse `Netlify.env` (not `process.env`) inside functions:\r\n\r\n```typescript\r\nconst apiKey = Netlify.env.get(\"API_KEY\");\r\n```\r\n\r\n## Resource Limits\r\n\r\n| Resource | Limit |\r\n|---|---|\r\n| Synchronous timeout | 60 seconds |\r\n| Background timeout | 15 minutes |\r\n| Scheduled timeout | 30 seconds |\r\n| Memory | 1024 MB |\r\n| Buffered payload | 6 MB |\r\n| Streamed payload | 20 MB |\r\n\r\n## Framework Considerations\r\n\r\nFrameworks with server-side capabilities (Astro, Next.js, Nuxt, SvelteKit, TanStack Start) typically generate their own serverless functions via adapters. You usually do not write raw Netlify Functions in these projects — the framework adapter handles server-side rendering and API routes. Write Netlify Functions directly when:\r\n\r\n- Using a client-side-only framework (Vite + React SPA, vanilla JS)\r\n- Adding background or scheduled tasks to any project\r\n- Building standalone API endpoints outside the framework's routing\r\n\r\nSee the **netlify-frameworks** skill for adapter setup.\r\n",{"name":5,"description":7},"main","e3091d1b371a9dcd9455d333175f948b286fdfcf","plugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions",1,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh","https:\u002F\u002Fkael-odin.github.io\u002Fcodex-plugins-zh\u002F","https:\u002F\u002Fgithub.com\u002Fkael-odin","https:\u002F\u002Fkael-odin.github.io\u002Fodin-valhalla\u002F","Full-stack development • Open-source • System engineering\r\nTurning ideas into repositories.","2026-11-08 17:05:36",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kael-odin\u002Fcodex-plugins-zh --skill netlify-functions",{"tool":41,"command":42},"bunx","bunx skills add kael-odin\u002Fcodex-plugins-zh --skill netlify-functions",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kael-odin\u002Fcodex-plugins-zh --skill netlify-functions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions\u002FSKILL.md",true,[49,55,61,65],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",358,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fnetlify-small.svg","ASSET","资产文件",1302,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions\u002Fassets\u002Fnetlify-small.svg",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"assets\u002Fnetlify.png",2686,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fnetlify\u002Fskills\u002Fnetlify-functions\u002Fassets\u002Fnetlify.png",{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10977,[71,79,87,95,102,109],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":20},"01M7EDVCKB89EF755PQMKV1BZA","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":20},"01M7EDPX7WHN6HQZ0QKWB0BGVZ","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","MIT","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":20},"01M7EDHHD98T8ZH09F40Q973G3","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":20},"01M7EDH3SGVMS1AFS6Q40B5J48","render-workflows","搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建（通过 CLI 或手动方式）、SDK 安装（Python 或 TypeScript）、任务模式（重试、子任务、扇出）、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":20},"01M7EDH0CYEKQ4VVARHZAQ43S8","render-web-services","配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署，或排查端口绑定问题时使用。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":20},"01M7EDGVDYFBG1CKSNMQ2DD336","render-static-sites","在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React\u002FVue\u002FHugo\u002FGatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header，或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]