[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6E25EC9YM4QM0KBQ2W5R1SC":3,"skill-same:01M6E25EC9YM4QM0KBQ2W5R1SC":233},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":168,"commitSha":169,"skillDirectory":170,"forksCount":171,"repositoryHtmlUrl":172,"repositoryHomepageUrl":173,"ownerHtmlUrl":174,"ownerBlogUrl":175,"ownerDescription":6,"updatedAt":176,"install":177,"resources":190},"01M6E25EC9YM4QM0KBQ2W5R1SC","vercel-functions",null,"Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.","ByeongminLee\u002Fnextjs-claude-code","ByeongminLee","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F71276006?v=4","01M6E1S467E7GC0NE144SWHC0V","Byeongmin Lee","01M6E1S4AV3W0B08Z2YBK26VG9",3,"MIT","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-functions\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"vercel functions","vercel","functions","apps","create","app","neon","express","project","shared","local","time","expert","vercel ai sdk","router","loop","server","logs","streaming","delete","2026-11-10 10:12:30",false,"---\nname: vercel-functions\ndescription: Vercel Functions expert guidance — Serverless Functions, Edge Functions, Fluid Compute, streaming, Cron Jobs, and runtime configuration. Use when configuring, debugging, or optimizing server-side code running on Vercel.\nmetadata:\n  priority: 8\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\"\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml\"\n  pathPatterns:\n    - 'api\u002F**\u002F*.*'\n    - 'pages\u002Fapi\u002F**'\n    - 'src\u002Fpages\u002Fapi\u002F**'\n    - 'app\u002F**\u002Froute.*'\n    - 'src\u002Fapp\u002F**\u002Froute.*'\n    - 'apps\u002F*\u002Fapi\u002F**\u002F*.*'\n    - 'apps\u002F*\u002Fapp\u002F**\u002Froute.*'\n    - 'apps\u002F*\u002Fsrc\u002Fapp\u002F**\u002Froute.*'\n    - 'apps\u002F*\u002Fpages\u002Fapi\u002F**'\n    - 'vercel.json'\n    - 'apps\u002F*\u002Fvercel.json'\n  bashPatterns:\n    - '\\bvercel\\s+dev\\b'\n    - '\\bvercel\\s+logs\\b'\nvalidate:\n  -\n    pattern: export\\s+default\\s+function\n    message: 'Use named exports (GET, POST, PUT, DELETE) instead of default export for route handlers'\n    severity: error\n  -\n    pattern: NextApiRequest|NextApiResponse\n    message: 'NextApiRequest\u002FNextApiResponse are Pages Router types — use Web API Request\u002FResponse'\n    severity: error\n  -\n    pattern: 'from\\s+[''\"](openai|@anthropic-ai\u002Fsdk|anthropic)[''\"]|new\\s+(OpenAI|Anthropic)\\('\n    message: 'Direct AI provider SDK detected in route handler. Use the Vercel AI SDK for streaming, tools, and provider abstraction.'\n    severity: recommended\n    upgradeToSkill: ai-sdk\n    upgradeWhy: 'Replace vendor-locked provider SDKs with @ai-sdk\u002Fopenai or @ai-sdk\u002Fanthropic for unified streaming and tool support.'\n    skipIfFileContains: '@ai-sdk\u002F|from\\s+[''\"](ai)[''\"]|import.*from\\s+[''\"](ai)[''\"]|streamText|generateText'\n  -\n    pattern: 'setTimeout\\s*\\(|setInterval\\s*\\(|await\\s+new\\s+Promise\\s*\\([^)]*setTimeout'\n    message: 'Long-running or polling logic detected in a serverless handler. Functions have execution time limits.'\n    severity: recommended\n    upgradeToSkill: workflow\n    upgradeWhy: 'Move delayed\u002Fpolling logic to Vercel Workflow for durable execution with pause, resume, retries, and crash safety.'\n    skipIfFileContains: 'use workflow|use step|@vercel\u002Fworkflow'\n  -\n    pattern: 'writeFile(Sync)?\\(|createWriteStream\\(|from\\s+[''\"](multer|formidable)[''\"]|fs\\.writeFile'\n    message: 'Local filesystem write detected. Serverless functions have ephemeral, read-only filesystems.'\n    severity: error\n    upgradeToSkill: vercel-storage\n    upgradeWhy: 'Replace local filesystem writes with Vercel Blob, Neon, or Upstash for persistent, platform-native storage.'\n    skipIfFileContains: '@vercel\u002Fblob|@upstash\u002F|@neondatabase\u002F'\n  -\n    pattern: 'export\\s+(async\\s+)?function\\s+(GET|POST|PUT|PATCH|DELETE)\\b'\n    message: 'Route handler has no observability instrumentation. Add logging and error tracking for production debugging.'\n    severity: warn\n    upgradeToSkill: observability\n    upgradeWhy: 'Add structured logging, error tracking, and OTel instrumentation to route handlers.'\n    skipIfFileContains: 'console\\.error|logger\\.|captureException|Sentry|@vercel\u002Fotel|withTracing'\n  -\n    pattern: 'from\\s+[''\"\"](lru-cache|node-cache|memory-cache)[''\"\"]|new\\s+(LRUCache|NodeCache|Map)\\(\\s*\\).*cache'\n    message: 'In-process memory cache detected in serverless function. Process memory is not shared across invocations.'\n    severity: recommended\n    upgradeToSkill: runtime-cache\n    upgradeWhy: 'Replace in-process caches with Vercel Runtime Cache (getCache from @vercel\u002Ffunctions) for region-aware caching that persists across invocations.'\n    skipIfFileContains: 'getCache|from\\s+[''\"\"]\\@vercel\u002Ffunctions[''\"\"]'\n  -\n    pattern: 'maxRetries\\s*[=:]|retryCount\\s*[=:]|retry\\s*\\(\\s*|for\\s*\\([^)]*retry|while\\s*\\([^)]*retry'\n    message: 'Manual retry logic detected. Use Vercel Workflow DevKit for automatic retries with durable execution.'\n    severity: recommended\n    upgradeToSkill: workflow\n    upgradeWhy: 'Replace manual retry loops with Workflow DevKit steps that provide automatic retries, crash safety, and observability.'\n    skipIfFileContains: 'use workflow|use step|@vercel\u002Fworkflow|from\\s+[''\"\"](workflow)[''\"\"]'\n  -\n    pattern: 'from\\s+[''\"](express)[''\"\"]|require\\s*\\(\\s*[''\"](express)[''\"\"\\)]'\n    message: 'Express.js detected in a Vercel project. Vercel Functions use the Web Request\u002FResponse API — Express middleware, req\u002Fres, and app.listen() do not work in serverless.'\n    severity: recommended\n    upgradeToSkill: vercel-functions\n    upgradeWhy: 'Replace Express with Next.js route handlers (export async function GET\u002FPOST) or Vercel Functions using the Web Request\u002FResponse API.'\n    skipIfFileContains: 'export\\s+(async\\s+)?function\\s+(GET|POST|PUT|PATCH|DELETE)|from\\s+[''\"\"](next\u002Fserver|@vercel\u002Ffunctions)[''\"\"]'\nretrieval:\n  aliases:\n    - serverless functions\n    - api routes\n    - edge functions\n    - lambda\n  intents:\n    - create serverless function\n    - configure function runtime\n    - optimize cold starts\n    - add api route\n  entities:\n    - Serverless Functions\n    - Edge Functions\n    - Fluid Compute\n    - streaming\n    - Cron Jobs\nchainTo:\n  -\n    pattern: 'from\\s+[''\\\"](openai|@anthropic-ai\u002Fsdk|anthropic)[''\"]|new\\s+(OpenAI|Anthropic)\\('\n    targetSkill: ai-sdk\n    message: 'Direct AI provider SDK in route handler — loading AI SDK guidance for unified streaming and tool support.'\n  -\n    pattern: 'setTimeout\\s*\\(|setInterval\\s*\\(|await\\s+new\\s+Promise\\s*\\([^)]*setTimeout'\n    targetSkill: workflow\n    message: 'Long-running or polling logic in serverless handler — loading Workflow DevKit for durable execution.'\n  -\n    pattern: 'writeFile(Sync)?\\(|createWriteStream\\(|from\\s+[''\\\"](multer|formidable)[''\"]|fs\\.writeFile'\n    targetSkill: vercel-storage\n    message: 'Local filesystem write in serverless function — loading Vercel Storage guidance for platform-native persistence.'\n  -\n    pattern: 'from\\s+[''\"\"]@vercel\u002F(postgres|kv)[''\"\"]'\n    targetSkill: vercel-storage\n    message: '@vercel\u002Fpostgres and @vercel\u002Fkv are sunset — loading Vercel Storage guidance for Neon and Upstash migration.'\n  -\n    pattern: 'generateObject\\s*\\(|streamObject\\s*\\(|toDataStreamResponse|maxSteps\\b|CoreMessage\\b'\n    targetSkill: ai-sdk\n    message: 'Deprecated AI SDK v5 API detected — loading AI SDK v6 guidance for migration.'\n  -\n    pattern: 'while\\s*\\(\\s*true\\s*\\)\\s*\\{|for\\s*\\(\\s*;\\s*;\\s*\\)\\s*\\{|setInterval\\s*\\(\\s*async'\n    targetSkill: workflow\n    message: 'Polling loop in serverless function detected — loading Workflow DevKit for durable, crash-safe execution with pause\u002Fresume.'\n    skipIfFileContains: \"use workflow|use step|from\\\\s+['\\\"]workflow['\\\"]\"\n  -\n    pattern: \"from\\\\s+['\\\"]express['\\\"]|require\\\\s*\\\\(\\\\s*['\\\"]express['\\\"]\"\n    targetSkill: vercel-functions\n    message: 'Express.js detected — loading Vercel Functions guidance for Web Request\u002FResponse API route handlers that replace Express middleware and routing.'\n    skipIfFileContains: \"export\\\\s+(async\\\\s+)?function\\\\s+(GET|POST|PUT|PATCH|DELETE)\"\n  -\n    pattern: 'from\\s+[''\"\"](lru-cache|node-cache|memory-cache)[''\"\"]|new\\s+(LRUCache|NodeCache|Map)\\(\\s*\\).*cache'\n    targetSkill: runtime-cache\n    message: 'In-process memory cache in serverless function — loading Runtime Cache guidance for region-aware caching that persists across invocations.'\n    skipIfFileContains: 'getCache|from\\s+[''\"\"]\\@vercel\u002Ffunctions[''\"\"]'\n  -\n    pattern: 'maxRetries\\s*[=:]|retryCount\\s*[=:]|retry\\s*\\(\\s*|for\\s*\\([^)]*retry|while\\s*\\([^)]*retry'\n    targetSkill: workflow\n    message: 'Manual retry logic in serverless handler — loading Workflow DevKit guidance for automatic retries with durable execution.'\n    skipIfFileContains: 'use workflow|use step|@vercel\u002Fworkflow|from\\s+[''\"\"](workflow)[''\"\"]'\n\n---\n\n# Vercel Functions\n\nYou are an expert in Vercel Functions — the compute layer of the Vercel platform.\n\n## Function Types\n\n### Serverless Functions (Node.js)\n- Full Node.js runtime, all npm packages available\n- Default for Next.js API routes, Server Actions, Server Components\n- Cold starts: 800ms–2.5s (with DB connections)\n- Max duration: 10s (Hobby), 300s (Pro default), 800s (Fluid Compute Pro\u002FEnterprise)\n\n```ts\n\u002F\u002F app\u002Fapi\u002Fhello\u002Froute.ts\nexport async function GET() {\n  return Response.json({ message: 'Hello from Node.js' })\n}\n```\n\n### Edge Functions (V8 Isolates)\n- Lightweight V8 runtime, Web Standard APIs only\n- Ultra-low cold starts (\u003C1ms globally)\n- Limited API surface (no full Node.js)\n- Best for: auth checks, redirects, A\u002FB testing, simple transformations\n\n```ts\n\u002F\u002F app\u002Fapi\u002Fhello\u002Froute.ts\nexport const runtime = 'edge'\n\nexport async function GET() {\n  return new Response('Hello from the Edge')\n}\n```\n\n### Bun Runtime (Public Beta)\n\nAdd `\"bunVersion\": \"1.x\"` to `vercel.json` to run Node.js functions on Bun instead. ~28% lower latency for CPU-bound workloads. Supports Next.js, Express, Hono, Nitro.\n\n### Rust Runtime (Public Beta)\n\nRust functions run on Fluid Compute with HTTP streaming and Active CPU pricing. Built on the community Rust runtime. Supports environment variables up to 64 KB.\n\n### Node.js 24 LTS\n\nNode.js 24 LTS is now GA on Vercel for both builds and functions. Features V8 13.6, global `URLPattern`, Undici v7 for faster `fetch()`, and npm v11.\n\n### Choosing Runtime\n\n| Need | Runtime | Why |\n|------|---------|-----|\n| Full Node.js APIs, npm packages | `nodejs` | Full compatibility |\n| Lower latency, CPU-bound work | `nodejs` + Bun | ~28% latency reduction |\n| Ultra-low latency, simple logic | `edge` | \u003C1ms cold start, global |\n| Database connections, heavy deps | `nodejs` | Edge lacks full Node.js |\n| Auth\u002Fredirect at the edge | `edge` | Fastest response |\n| AI streaming | Either | Both support streaming |\n| Systems-level performance | `rust` (beta) | Native speed, Fluid Compute |\n\n## Fluid Compute\n\nFluid Compute is the unified execution model for all Vercel Functions (both Node.js and Edge).\n\nKey benefits:\n- **Optimized concurrency**: Multiple invocations on a single instance — up to 85% cost reduction for high-concurrency workloads\n- **Extended durations**: Default 300s for all plans; up to 800s on Pro\u002FEnterprise\n- **Active CPU pricing**: Charges only while CPU is actively working, not during idle\u002Fawait time. Enabled by default for all plans. Memory-only periods billed at a significantly lower rate.\n- **Background processing**: `waitUntil` \u002F `after` for post-response tasks\n- **Dynamic scaling**: Automatic during traffic spikes\n- **Bytecode caching**: Reduces cold starts via Rust-based runtime with pre-compiled function code\n- **Multi-region failover**: Default for Enterprise when Fluid is activated\n\n### Instance Sizes\n\n| Size | CPU | Memory |\n|------|-----|--------|\n| Standard (default) | 1 vCPU | 2 GB |\n| Performance | 2 vCPU | 4 GB |\n\nHobby projects use Standard CPU. The Basic CPU instance has been removed.\n\n### Background Processing with `waitUntil`\n\n```ts\n\u002F\u002F Continue work after sending response\nimport { waitUntil } from '@vercel\u002Ffunctions'\n\nexport async function POST(req: Request) {\n  const data = await req.json()\n\n  \u002F\u002F Send response immediately\n  const response = Response.json({ received: true })\n\n  \u002F\u002F Continue processing in background\n  waitUntil(async () => {\n    await processAnalytics(data)\n    await sendNotification(data)\n  })\n\n  return response\n}\n```\n\n### Next.js `after` (equivalent)\n\n```ts\nimport { after } from 'next\u002Fserver'\n\nexport async function POST(req: Request) {\n  const data = await req.json()\n\n  after(async () => {\n    await logToAnalytics(data)\n  })\n\n  return Response.json({ ok: true })\n}\n```\n\n## Streaming\n\nZero-config streaming for both runtimes. Essential for AI applications.\n\n```ts\nexport async function POST(req: Request) {\n  const encoder = new TextEncoder()\n  const stream = new ReadableStream({\n    async start(controller) {\n      for (const chunk of data) {\n        controller.enqueue(encoder.encode(chunk))\n        await new Promise(r => setTimeout(r, 100))\n      }\n      controller.close()\n    },\n  })\n\n  return new Response(stream, {\n    headers: { 'Content-Type': 'text\u002Fevent-stream' },\n  })\n}\n```\n\nFor AI streaming, use the AI SDK's `toUIMessageStreamResponse()` (for chat UIs with `useChat`) which handles SSE formatting automatically.\n\n## Cron Jobs\n\nSchedule function invocations via `vercel.json`:\n\n```json\n{\n  \"crons\": [\n    {\n      \"path\": \"\u002Fapi\u002Fdaily-report\",\n      \"schedule\": \"0 8 * * *\"\n    },\n    {\n      \"path\": \"\u002Fapi\u002Fcleanup\",\n      \"schedule\": \"0 *\u002F6 * * *\"\n    }\n  ]\n}\n```\n\nThe cron endpoint receives a normal HTTP request. Verify it's from Vercel:\n\n```ts\nexport async function GET(req: Request) {\n  const authHeader = req.headers.get('authorization')\n  if (authHeader !== `Bearer ${process.env.CRON_SECRET}`) {\n    return new Response('Unauthorized', { status: 401 })\n  }\n  \u002F\u002F Do scheduled work\n  return Response.json({ ok: true })\n}\n```\n\n## Configuration via vercel.json\n\n**Deprecation notice**: Support for the legacy `now.json` config file will be removed on **March 31, 2026**. Rename `now.json` to `vercel.json` (no content changes required).\n\n```json\n{\n  \"functions\": {\n    \"app\u002Fapi\u002Fheavy\u002F**\": {\n      \"maxDuration\": 300,\n      \"memory\": 1024\n    },\n    \"app\u002Fapi\u002Fedge\u002F**\": {\n      \"runtime\": \"edge\"\n    }\n  }\n}\n```\n\n## Timeout Limits\n\nAll plans now default to 300s execution time with Fluid Compute.\n\n| Plan | Default | Max |\n|------|---------|-----|\n| Hobby | 300s | 300s |\n| Pro | 300s | 800s |\n| Enterprise | 300s | 800s |\n\n## Common Pitfalls\n\n1. **Cold starts with DB connections**: Use connection pooling (e.g., Neon's `@neondatabase\u002Fserverless`)\n2. **Edge limitations**: No `fs`, no native modules, limited `crypto` — use Node.js runtime if needed\n3. **Timeout exceeded**: Use Fluid Compute for long-running tasks, or Workflow DevKit for very long processes\n4. **Bundle size**: Python runtime supports up to 500MB; Node.js has smaller limits\n5. **Environment variables**: Available in all functions automatically; use `vercel env pull` for local dev\n\n## Function Runtime Diagnostics\n\n### Timeout Diagnostics\n\n```\n504 Gateway Timeout?\n├─ All plans default to 300s with Fluid Compute\n├─ Pro\u002FEnterprise: configurable up to 800s\n├─ Long-running task?\n│  ├─ Under 5 min → Use Fluid Compute with streaming\n│  ├─ Up to 15 min → Use Vercel Functions with `maxDuration` in vercel.json\n│  └─ Hours\u002Fdays → Use Workflow DevKit (DurableAgent or workflow steps)\n└─ DB query slow? → Add connection pooling, check cold start, use Edge Config\n```\n\n### 500 Error Diagnostics\n\n```\n500 Internal Server Error?\n├─ Check Vercel Runtime Logs (Dashboard → Deployments → Functions tab)\n├─ Missing env vars? → Compare `.env.local` against Vercel dashboard settings\n├─ Import error? → Verify package is in `dependencies`, not `devDependencies`\n└─ Uncaught exception? → Wrap handler in try\u002Fcatch, use `after()` for error reporting\n```\n\n### Invocation Failure Diagnostics\n\n```\n\"FUNCTION_INVOCATION_FAILED\"?\n├─ Memory exceeded? → Increase `memory` in vercel.json (up to 3008 MB on Pro)\n├─ Crashed during init? → Check top-level await or heavy imports at module scope\n└─ Edge Function crash? → Check for Node.js APIs not available in Edge runtime\n```\n\n### Cold Start Diagnostics\n\n```\nCold start latency > 1s?\n├─ Using Node.js runtime? → Consider Edge Functions for latency-sensitive routes\n├─ Large function bundle? → Audit imports, use dynamic imports, tree-shake\n├─ DB connection in cold start? → Use connection pooling (Neon serverless driver)\n└─ Enable Fluid Compute to reuse warm instances across requests\n```\n\n### Edge Function Timeout Diagnostics\n\n```\n\"EDGE_FUNCTION_INVOCATION_TIMEOUT\"?\n├─ Edge Functions have 25s hard limit (not configurable)\n├─ Move heavy computation to Node.js Serverless Functions\n└─ Use streaming to start response early, process in background with `waitUntil`\n```\n\n## Official Documentation\n\n- [Vercel Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Serverless Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Edge Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Fluid Compute](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffluid-compute)\n- [Streaming](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fstreaming)\n- [Cron Jobs](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcron-jobs)\n- [GitHub: Vercel](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel)\n","# Vercel Functions\n\nYou are an expert in Vercel Functions — the compute layer of the Vercel platform.\n\n## Function Types\n\n### Serverless Functions (Node.js)\n- Full Node.js runtime, all npm packages available\n- Default for Next.js API routes, Server Actions, Server Components\n- Cold starts: 800ms–2.5s (with DB connections)\n- Max duration: 10s (Hobby), 300s (Pro default), 800s (Fluid Compute Pro\u002FEnterprise)\n\n```ts\n\u002F\u002F app\u002Fapi\u002Fhello\u002Froute.ts\nexport async function GET() {\n  return Response.json({ message: 'Hello from Node.js' })\n}\n```\n\n### Edge Functions (V8 Isolates)\n- Lightweight V8 runtime, Web Standard APIs only\n- Ultra-low cold starts (\u003C1ms globally)\n- Limited API surface (no full Node.js)\n- Best for: auth checks, redirects, A\u002FB testing, simple transformations\n\n```ts\n\u002F\u002F app\u002Fapi\u002Fhello\u002Froute.ts\nexport const runtime = 'edge'\n\nexport async function GET() {\n  return new Response('Hello from the Edge')\n}\n```\n\n### Bun Runtime (Public Beta)\n\nAdd `\"bunVersion\": \"1.x\"` to `vercel.json` to run Node.js functions on Bun instead. ~28% lower latency for CPU-bound workloads. Supports Next.js, Express, Hono, Nitro.\n\n### Rust Runtime (Public Beta)\n\nRust functions run on Fluid Compute with HTTP streaming and Active CPU pricing. Built on the community Rust runtime. Supports environment variables up to 64 KB.\n\n### Node.js 24 LTS\n\nNode.js 24 LTS is now GA on Vercel for both builds and functions. Features V8 13.6, global `URLPattern`, Undici v7 for faster `fetch()`, and npm v11.\n\n### Choosing Runtime\n\n| Need | Runtime | Why |\n|------|---------|-----|\n| Full Node.js APIs, npm packages | `nodejs` | Full compatibility |\n| Lower latency, CPU-bound work | `nodejs` + Bun | ~28% latency reduction |\n| Ultra-low latency, simple logic | `edge` | \u003C1ms cold start, global |\n| Database connections, heavy deps | `nodejs` | Edge lacks full Node.js |\n| Auth\u002Fredirect at the edge | `edge` | Fastest response |\n| AI streaming | Either | Both support streaming |\n| Systems-level performance | `rust` (beta) | Native speed, Fluid Compute |\n\n## Fluid Compute\n\nFluid Compute is the unified execution model for all Vercel Functions (both Node.js and Edge).\n\nKey benefits:\n- **Optimized concurrency**: Multiple invocations on a single instance — up to 85% cost reduction for high-concurrency workloads\n- **Extended durations**: Default 300s for all plans; up to 800s on Pro\u002FEnterprise\n- **Active CPU pricing**: Charges only while CPU is actively working, not during idle\u002Fawait time. Enabled by default for all plans. Memory-only periods billed at a significantly lower rate.\n- **Background processing**: `waitUntil` \u002F `after` for post-response tasks\n- **Dynamic scaling**: Automatic during traffic spikes\n- **Bytecode caching**: Reduces cold starts via Rust-based runtime with pre-compiled function code\n- **Multi-region failover**: Default for Enterprise when Fluid is activated\n\n### Instance Sizes\n\n| Size | CPU | Memory |\n|------|-----|--------|\n| Standard (default) | 1 vCPU | 2 GB |\n| Performance | 2 vCPU | 4 GB |\n\nHobby projects use Standard CPU. The Basic CPU instance has been removed.\n\n### Background Processing with `waitUntil`\n\n```ts\n\u002F\u002F Continue work after sending response\nimport { waitUntil } from '@vercel\u002Ffunctions'\n\nexport async function POST(req: Request) {\n  const data = await req.json()\n\n  \u002F\u002F Send response immediately\n  const response = Response.json({ received: true })\n\n  \u002F\u002F Continue processing in background\n  waitUntil(async () => {\n    await processAnalytics(data)\n    await sendNotification(data)\n  })\n\n  return response\n}\n```\n\n### Next.js `after` (equivalent)\n\n```ts\nimport { after } from 'next\u002Fserver'\n\nexport async function POST(req: Request) {\n  const data = await req.json()\n\n  after(async () => {\n    await logToAnalytics(data)\n  })\n\n  return Response.json({ ok: true })\n}\n```\n\n## Streaming\n\nZero-config streaming for both runtimes. Essential for AI applications.\n\n```ts\nexport async function POST(req: Request) {\n  const encoder = new TextEncoder()\n  const stream = new ReadableStream({\n    async start(controller) {\n      for (const chunk of data) {\n        controller.enqueue(encoder.encode(chunk))\n        await new Promise(r => setTimeout(r, 100))\n      }\n      controller.close()\n    },\n  })\n\n  return new Response(stream, {\n    headers: { 'Content-Type': 'text\u002Fevent-stream' },\n  })\n}\n```\n\nFor AI streaming, use the AI SDK's `toUIMessageStreamResponse()` (for chat UIs with `useChat`) which handles SSE formatting automatically.\n\n## Cron Jobs\n\nSchedule function invocations via `vercel.json`:\n\n```json\n{\n  \"crons\": [\n    {\n      \"path\": \"\u002Fapi\u002Fdaily-report\",\n      \"schedule\": \"0 8 * * *\"\n    },\n    {\n      \"path\": \"\u002Fapi\u002Fcleanup\",\n      \"schedule\": \"0 *\u002F6 * * *\"\n    }\n  ]\n}\n```\n\nThe cron endpoint receives a normal HTTP request. Verify it's from Vercel:\n\n```ts\nexport async function GET(req: Request) {\n  const authHeader = req.headers.get('authorization')\n  if (authHeader !== `Bearer ${process.env.CRON_SECRET}`) {\n    return new Response('Unauthorized', { status: 401 })\n  }\n  \u002F\u002F Do scheduled work\n  return Response.json({ ok: true })\n}\n```\n\n## Configuration via vercel.json\n\n**Deprecation notice**: Support for the legacy `now.json` config file will be removed on **March 31, 2026**. Rename `now.json` to `vercel.json` (no content changes required).\n\n```json\n{\n  \"functions\": {\n    \"app\u002Fapi\u002Fheavy\u002F**\": {\n      \"maxDuration\": 300,\n      \"memory\": 1024\n    },\n    \"app\u002Fapi\u002Fedge\u002F**\": {\n      \"runtime\": \"edge\"\n    }\n  }\n}\n```\n\n## Timeout Limits\n\nAll plans now default to 300s execution time with Fluid Compute.\n\n| Plan | Default | Max |\n|------|---------|-----|\n| Hobby | 300s | 300s |\n| Pro | 300s | 800s |\n| Enterprise | 300s | 800s |\n\n## Common Pitfalls\n\n1. **Cold starts with DB connections**: Use connection pooling (e.g., Neon's `@neondatabase\u002Fserverless`)\n2. **Edge limitations**: No `fs`, no native modules, limited `crypto` — use Node.js runtime if needed\n3. **Timeout exceeded**: Use Fluid Compute for long-running tasks, or Workflow DevKit for very long processes\n4. **Bundle size**: Python runtime supports up to 500MB; Node.js has smaller limits\n5. **Environment variables**: Available in all functions automatically; use `vercel env pull` for local dev\n\n## Function Runtime Diagnostics\n\n### Timeout Diagnostics\n\n```\n504 Gateway Timeout?\n├─ All plans default to 300s with Fluid Compute\n├─ Pro\u002FEnterprise: configurable up to 800s\n├─ Long-running task?\n│  ├─ Under 5 min → Use Fluid Compute with streaming\n│  ├─ Up to 15 min → Use Vercel Functions with `maxDuration` in vercel.json\n│  └─ Hours\u002Fdays → Use Workflow DevKit (DurableAgent or workflow steps)\n└─ DB query slow? → Add connection pooling, check cold start, use Edge Config\n```\n\n### 500 Error Diagnostics\n\n```\n500 Internal Server Error?\n├─ Check Vercel Runtime Logs (Dashboard → Deployments → Functions tab)\n├─ Missing env vars? → Compare `.env.local` against Vercel dashboard settings\n├─ Import error? → Verify package is in `dependencies`, not `devDependencies`\n└─ Uncaught exception? → Wrap handler in try\u002Fcatch, use `after()` for error reporting\n```\n\n### Invocation Failure Diagnostics\n\n```\n\"FUNCTION_INVOCATION_FAILED\"?\n├─ Memory exceeded? → Increase `memory` in vercel.json (up to 3008 MB on Pro)\n├─ Crashed during init? → Check top-level await or heavy imports at module scope\n└─ Edge Function crash? → Check for Node.js APIs not available in Edge runtime\n```\n\n### Cold Start Diagnostics\n\n```\nCold start latency > 1s?\n├─ Using Node.js runtime? → Consider Edge Functions for latency-sensitive routes\n├─ Large function bundle? → Audit imports, use dynamic imports, tree-shake\n├─ DB connection in cold start? → Use connection pooling (Neon serverless driver)\n└─ Enable Fluid Compute to reuse warm instances across requests\n```\n\n### Edge Function Timeout Diagnostics\n\n```\n\"EDGE_FUNCTION_INVOCATION_TIMEOUT\"?\n├─ Edge Functions have 25s hard limit (not configurable)\n├─ Move heavy computation to Node.js Serverless Functions\n└─ Use streaming to start response early, process in background with `waitUntil`\n```\n\n## Official Documentation\n\n- [Vercel Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Serverless Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Edge Functions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions)\n- [Fluid Compute](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffluid-compute)\n- [Streaming](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fstreaming)\n- [Cron Jobs](https:\u002F\u002Fvercel.com\u002Fdocs\u002Fcron-jobs)\n- [GitHub: Vercel](https:\u002F\u002Fgithub.com\u002Fvercel\u002Fvercel)\n",{"name":5,"chainTo":54,"metadata":90,"validate":111,"retrieval":152,"description":7},[55,59,63,67,70,73,77,81,86],{"message":56,"pattern":57,"targetSkill":58},"Direct AI provider SDK in route handler — loading AI SDK guidance for unified streaming and tool support.","from\\s+['\\\"](openai|@anthropic-ai\u002Fsdk|anthropic)['\"]|new\\s+(OpenAI|Anthropic)\\(","ai-sdk",{"message":60,"pattern":61,"targetSkill":62},"Long-running or polling logic in serverless handler — loading Workflow DevKit for durable execution.","setTimeout\\s*\\(|setInterval\\s*\\(|await\\s+new\\s+Promise\\s*\\([^)]*setTimeout","workflow",{"message":64,"pattern":65,"targetSkill":66},"Local filesystem write in serverless function — loading Vercel Storage guidance for platform-native persistence.","writeFile(Sync)?\\(|createWriteStream\\(|from\\s+['\\\"](multer|formidable)['\"]|fs\\.writeFile","vercel-storage",{"message":68,"pattern":69,"targetSkill":66},"@vercel\u002Fpostgres and @vercel\u002Fkv are sunset — loading Vercel Storage guidance for Neon and Upstash migration.","from\\s+['\"\"]@vercel\u002F(postgres|kv)['\"\"]",{"message":71,"pattern":72,"targetSkill":58},"Deprecated AI SDK v5 API detected — loading AI SDK v6 guidance for migration.","generateObject\\s*\\(|streamObject\\s*\\(|toDataStreamResponse|maxSteps\\b|CoreMessage\\b",{"message":74,"pattern":75,"targetSkill":62,"skipIfFileContains":76},"Polling loop in serverless function detected — loading Workflow DevKit for durable, crash-safe execution with pause\u002Fresume.","while\\s*\\(\\s*true\\s*\\)\\s*\\{|for\\s*\\(\\s*;\\s*;\\s*\\)\\s*\\{|setInterval\\s*\\(\\s*async","use workflow|use step|from\\s+['\"]workflow['\"]",{"message":78,"pattern":79,"targetSkill":5,"skipIfFileContains":80},"Express.js detected — loading Vercel Functions guidance for Web Request\u002FResponse API route handlers that replace Express middleware and routing.","from\\s+['\"]express['\"]|require\\s*\\(\\s*['\"]express['\"]","export\\s+(async\\s+)?function\\s+(GET|POST|PUT|PATCH|DELETE)",{"message":82,"pattern":83,"targetSkill":84,"skipIfFileContains":85},"In-process memory cache in serverless function — loading Runtime Cache guidance for region-aware caching that persists across invocations.","from\\s+['\"\"](lru-cache|node-cache|memory-cache)['\"\"]|new\\s+(LRUCache|NodeCache|Map)\\(\\s*\\).*cache","runtime-cache","getCache|from\\s+['\"\"]\\@vercel\u002Ffunctions['\"\"]",{"message":87,"pattern":88,"targetSkill":62,"skipIfFileContains":89},"Manual retry logic in serverless handler — loading Workflow DevKit guidance for automatic retries with durable execution.","maxRetries\\s*[=:]|retryCount\\s*[=:]|retry\\s*\\(\\s*|for\\s*\\([^)]*retry|while\\s*\\([^)]*retry","use workflow|use step|@vercel\u002Fworkflow|from\\s+['\"\"](workflow)['\"\"]",{"docs":91,"sitemap":94,"priority":95,"bashPatterns":96,"pathPatterns":99},[92,93],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions","https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fruntimes","https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml",8,[97,98],"\\bvercel\\s+dev\\b","\\bvercel\\s+logs\\b",[100,101,102,103,104,105,106,107,108,109,110],"api\u002F**\u002F*.*","pages\u002Fapi\u002F**","src\u002Fpages\u002Fapi\u002F**","app\u002F**\u002Froute.*","src\u002Fapp\u002F**\u002Froute.*","apps\u002F*\u002Fapi\u002F**\u002F*.*","apps\u002F*\u002Fapp\u002F**\u002Froute.*","apps\u002F*\u002Fsrc\u002Fapp\u002F**\u002Froute.*","apps\u002F*\u002Fpages\u002Fapi\u002F**","vercel.json","apps\u002F*\u002Fvercel.json",[112,116,119,125,129,134,141,144,147],{"message":113,"pattern":114,"severity":115},"Use named exports (GET, POST, PUT, DELETE) instead of default export for route handlers","export\\s+default\\s+function","error",{"message":117,"pattern":118,"severity":115},"NextApiRequest\u002FNextApiResponse are Pages Router types — use Web API Request\u002FResponse","NextApiRequest|NextApiResponse",{"message":120,"pattern":121,"severity":122,"upgradeWhy":123,"upgradeToSkill":58,"skipIfFileContains":124},"Direct AI provider SDK detected in route handler. Use the Vercel AI SDK for streaming, tools, and provider abstraction.","from\\s+['\"](openai|@anthropic-ai\u002Fsdk|anthropic)['\"]|new\\s+(OpenAI|Anthropic)\\(","recommended","Replace vendor-locked provider SDKs with @ai-sdk\u002Fopenai or @ai-sdk\u002Fanthropic for unified streaming and tool support.","@ai-sdk\u002F|from\\s+['\"](ai)['\"]|import.*from\\s+['\"](ai)['\"]|streamText|generateText",{"message":126,"pattern":61,"severity":122,"upgradeWhy":127,"upgradeToSkill":62,"skipIfFileContains":128},"Long-running or polling logic detected in a serverless handler. Functions have execution time limits.","Move delayed\u002Fpolling logic to Vercel Workflow for durable execution with pause, resume, retries, and crash safety.","use workflow|use step|@vercel\u002Fworkflow",{"message":130,"pattern":131,"severity":115,"upgradeWhy":132,"upgradeToSkill":66,"skipIfFileContains":133},"Local filesystem write detected. Serverless functions have ephemeral, read-only filesystems.","writeFile(Sync)?\\(|createWriteStream\\(|from\\s+['\"](multer|formidable)['\"]|fs\\.writeFile","Replace local filesystem writes with Vercel Blob, Neon, or Upstash for persistent, platform-native storage.","@vercel\u002Fblob|@upstash\u002F|@neondatabase\u002F",{"message":135,"pattern":136,"severity":137,"upgradeWhy":138,"upgradeToSkill":139,"skipIfFileContains":140},"Route handler has no observability instrumentation. Add logging and error tracking for production debugging.","export\\s+(async\\s+)?function\\s+(GET|POST|PUT|PATCH|DELETE)\\b","warn","Add structured logging, error tracking, and OTel instrumentation to route handlers.","observability","console\\.error|logger\\.|captureException|Sentry|@vercel\u002Fotel|withTracing",{"message":142,"pattern":83,"severity":122,"upgradeWhy":143,"upgradeToSkill":84,"skipIfFileContains":85},"In-process memory cache detected in serverless function. Process memory is not shared across invocations.","Replace in-process caches with Vercel Runtime Cache (getCache from @vercel\u002Ffunctions) for region-aware caching that persists across invocations.",{"message":145,"pattern":88,"severity":122,"upgradeWhy":146,"upgradeToSkill":62,"skipIfFileContains":89},"Manual retry logic detected. Use Vercel Workflow DevKit for automatic retries with durable execution.","Replace manual retry loops with Workflow DevKit steps that provide automatic retries, crash safety, and observability.",{"message":148,"pattern":149,"severity":122,"upgradeWhy":150,"upgradeToSkill":5,"skipIfFileContains":151},"Express.js detected in a Vercel project. Vercel Functions use the Web Request\u002FResponse API — Express middleware, req\u002Fres, and app.listen() do not work in serverless.","from\\s+['\"](express)['\"\"]|require\\s*\\(\\s*['\"](express)['\"\"\\)]","Replace Express with Next.js route handlers (export async function GET\u002FPOST) or Vercel Functions using the Web Request\u002FResponse API.","export\\s+(async\\s+)?function\\s+(GET|POST|PUT|PATCH|DELETE)|from\\s+['\"\"](next\u002Fserver|@vercel\u002Ffunctions)['\"\"]",{"aliases":153,"intents":158,"entities":163},[154,155,156,157],"serverless functions","api routes","edge functions","lambda",[159,160,161,162],"create serverless function","configure function runtime","optimize cold starts","add api route",[164,165,166,47,167],"Serverless Functions","Edge Functions","Fluid Compute","Cron Jobs","main","330a71e3d12264515ce3477e446d29fd34a88a9d","template\u002Fskills-archive\u002Fvercel-functions",1,"https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code","https:\u002F\u002Fbyeongminlee.github.io\u002Fnextjs-claude-code\u002F","https:\u002F\u002Fgithub.com\u002FByeongminLee","byeongmin.dev","2026-03-27 12:45:44",{"source":8,"skillName":5,"commands":178,"prompt":188,"zipAvailable":189},[179,182,185],{"tool":180,"command":181},"npx","npx skills add ByeongminLee\u002Fnextjs-claude-code --skill vercel-functions",{"tool":183,"command":184},"bunx","bunx skills add ByeongminLee\u002Fnextjs-claude-code --skill vercel-functions",{"tool":186,"command":187},"pnpm","pnpm dlx skills add ByeongminLee\u002Fnextjs-claude-code --skill vercel-functions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-functions\u002FSKILL.md",true,[191,197,201,207,211,215,219,225,229],{"path":192,"resourceType":193,"resourceTypeDesc":194,"sizeBytes":195,"sourceHtmlUrl":196},"assets\u002Fexample_post.md","ASSET","资产文件",2321,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Fassets\u002Fexample_post.md",{"path":198,"resourceType":193,"resourceTypeDesc":194,"sizeBytes":199,"sourceHtmlUrl":200},"assets\u002Fpost_templates.md",3873,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Fassets\u002Fpost_templates.md",{"path":202,"resourceType":203,"resourceTypeDesc":204,"sizeBytes":205,"sourceHtmlUrl":206},"references\u002Faccessibility_and_inclusion.md","REFERENCE","参考文档",5914,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Freferences\u002Faccessibility_and_inclusion.md",{"path":208,"resourceType":203,"resourceTypeDesc":204,"sizeBytes":209,"sourceHtmlUrl":210},"references\u002Fhook_and_fold_mechanics.md",6191,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Freferences\u002Fhook_and_fold_mechanics.md",{"path":212,"resourceType":203,"resourceTypeDesc":204,"sizeBytes":213,"sourceHtmlUrl":214},"references\u002Fpost_formats_canon.md",6122,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Freferences\u002Fpost_formats_canon.md",{"path":216,"resourceType":203,"resourceTypeDesc":204,"sizeBytes":217,"sourceHtmlUrl":218},"references\u002Frepurposing_discipline.md",5963,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Freferences\u002Frepurposing_discipline.md",{"path":220,"resourceType":221,"resourceTypeDesc":222,"sizeBytes":223,"sourceHtmlUrl":224},"scripts\u002Fformat_picker.py","SCRIPT","脚本",12046,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Fscripts\u002Fformat_picker.py",{"path":226,"resourceType":221,"resourceTypeDesc":222,"sizeBytes":227,"sourceHtmlUrl":228},"scripts\u002Fpost_linter.py",15831,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Fscripts\u002Fpost_linter.py",{"path":230,"resourceType":221,"resourceTypeDesc":222,"sizeBytes":231,"sourceHtmlUrl":232},"scripts\u002Frepurpose_splitter.py",12165,"https:\u002F\u002Fgithub.com\u002Fmarshadgani\u002FArshad.AI\u002Fblob\u002Fclaude\u002Fai-personal-assistant-main\u002F.claude\u002Fskills\u002Fclaude-skills\u002Flinkedin-content\u002Fscripts\u002Frepurpose_splitter.py",[234,253,261,284,323,344],{"skillNo":235,"name":236,"nameZh":6,"description":237,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":238,"categories":239,"keywords":240,"publishedAt":49},"01M6E263DRDCZ5AX01N6MDYC6Z","zustand","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fzustand\u002FSKILL.md",[],[236,241,242,243,244,245,246,247,248,249,250,251,252],"use","management","guide","implementation","zustand state","state","code","state management","development","src","triggers","actions",{"skillNo":254,"name":255,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":256,"categories":257,"keywords":258,"publishedAt":49},"01M6E260QFP3ZMXY2Y6KTGZYXS","web-vitals","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fweb-vitals\u002FSKILL.md",[],[259,260],"web","web vitals",{"skillNo":262,"name":66,"nameZh":6,"description":263,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":264,"categories":265,"keywords":267,"publishedAt":49},"01M6E25QEKXHH092S5RB0GKM0K","Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fvercel-storage\u002FSKILL.md",[266],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[30,268,269,270,271,272,273,274,275,276,34,35,277,278,41,279,280,281,282,283],"storage","vercel storage","nextjs","supabase","database","auth","mongodb","postgres","click","prisma","SET","up","auto","configure","migrate","api",{"skillNo":285,"name":286,"nameZh":6,"description":287,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":288,"categories":289,"keywords":305,"publishedAt":49},"01M6E25873YRYP96MSQK7E2D9X","ui-ux-pro-max","UI\u002FUX design intelligence for web and mobile. Includes 50+ styles, 161 color palettes, 57 font pairings, 161 product types, 99 UX guidelines, and 25 chart types across 10 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui, and HTML\u002FCSS). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, and check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, and mobile app. Elements: button, modal, navbar, sidebar, card, table, form, and chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, and flat design. Topics: color systems, accessibility, animation, layout, typography, font pairing, spacing, interaction states, shadow, and gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fui-ux-pro-max\u002FSKILL.md",[290,293,296,299,302],{"categoryNo":291,"categoryName":292,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":294,"categoryName":295,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":297,"categoryName":298,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":300,"categoryName":301,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师",{"categoryNo":303,"categoryName":304,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[306,307,308,309,310,311,34,312,313,314,315,316,252,317,33,318,319,320,321,322],"ui ux pro max","ui","ux","max","card","chart","fix","projects","plan","improve","Tailwind","search","react","css","MCP","design","Animation",{"skillNo":324,"name":325,"nameZh":6,"description":326,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":327,"categories":328,"keywords":329,"publishedAt":49},"01M6E251G3FJSRB9019V20QK9X","turborepo","Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines,\ndependsOn, caching, remote cache, the \"turbo\" CLI, --filter, --affected, CI optimization, environment\nvariables, internal packages, monorepo structure\u002Fbest practices, and boundaries.\n\nUse when user: configures tasks\u002Fworkflows\u002Fpipelines, creates packages, sets up\nmonorepo, shares code between apps, runs changed\u002Faffected packages, debugs cache,\nor has apps\u002Fpackages directories.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturborepo\u002FSKILL.md",[],[325,330,331,332,333,247,251,334,335,32,336,337,279,241,338,339,340,341,342,343],"packages","tasks","workflows","cli","filter","environment variables","caching","structure","environment","monorepo","system","canary","Optimization","ci",{"skillNo":345,"name":346,"nameZh":6,"description":347,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":348,"categories":349,"keywords":350,"publishedAt":49},"01M6E24X88FC23VXDNJ58JV24X","turbopack","Turbopack expert guidance. Use when configuring the Next.js bundler, optimizing HMR, debugging build issues, or understanding the Turbopack vs Webpack differences.","https:\u002F\u002Fgithub.com\u002FByeongminLee\u002Fnextjs-claude-code\u002Fblob\u002Fmain\u002Ftemplate\u002Fskills-archive\u002Fturbopack\u002FSKILL.md",[],[346,351,312,352,353,354,41,355,279,241,356,281,357,270,45,358,359,360,361,362],"architecture","speed","next","build","guidance","syntax","Next.js","https","issues","dev","debugging","config"]