[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6K1YFEP0GPPGMQ3D0FPTS27":3,"skill-same:01M6K1YFEP0GPPGMQ3D0FPTS27":176},{"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":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":42,"commitSha":134,"skillDirectory":135,"forksCount":136,"repositoryHtmlUrl":137,"repositoryHomepageUrl":6,"ownerHtmlUrl":138,"ownerBlogUrl":139,"ownerDescription":140,"updatedAt":141,"install":142,"resources":155},"01M6K1YFEP0GPPGMQ3D0FPTS27","vercel-services",null,"Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.","NagyVikt\u002Fcodex-plugins","NagyVikt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F137165288?v=4","01M6K0SJ3R2DAZRJKJJS10VN87","Viktor Nagy","01M6K0SJ9HXN0GBD91QDQ9WNVV",2,"MIT","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"vercel services","services","vercel","up","python backend","error","apps","app","get","project","go backend","aws lambda","main","frontend","fastapi","go api","monorepo","configure","SET","docker compose","2026-11-10 10:12:30",false,"---\nname: vercel-services\ndescription: \"Vercel Services — deploy multiple services within a single Vercel project. Use for monorepo layouts or when combining a backend (Python, Go) with a frontend (Next.js, Vite) in one deployment.\"\nsummary: \"Deploy multiple services in one Vercel project — e.g. a Python backend alongside a JS frontend\"\nmetadata:\n  priority: 7\n  docs:\n    - \"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fservices\"\n  sitemap: \"https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml\"\n  pathPatterns:\n    - 'backend\u002F**'\n    - 'backend\u002Fmain.py'\n    - 'backend\u002Fmain.go'\n    - 'backend\u002Fgo.mod'\n    - 'backend\u002Fpyproject.toml'\n    - 'backend\u002Frequirements.txt'\n    - 'frontend\u002F**'\n    - 'apps\u002F*\u002Fbackend\u002F**'\n    - 'apps\u002F*\u002Ffrontend\u002F**'\n    - 'services\u002F*\u002Fvercel.json'\n    - '*\u002Fpyproject.toml'\n    - '*\u002Fgo.mod'\n  bashPatterns:\n    - '\\bvercel\\s+dev\\b.*-L'\n    - '\\bpip\\s+install\\b.*fastapi'\n    - '\\buv\\s+(sync|pip|run)\\b'\n    - '\\bgo\\s+(run|build|mod)\\b'\n    - '\\bpython\\s+-m\\s+uvicorn\\b'\n    - '\\buvicorn\\b'\n  importPatterns:\n    - \"fastapi\"\n  promptSignals:\n    phrases:\n      - \"services api\"\n      - \"vercel services\"\n      - \"multi-service\"\n      - \"python backend\"\n      - \"go backend\"\n      - \"fastapi\"\n      - \"deploy backend\"\n      - \"backend and frontend\"\n      - \"multiple services\"\n    allOf:\n      - [backend, frontend]\n      - [python, vercel]\n      - [go, vercel]\n      - [backend, deploy]\n      - [service, monorepo]\n      - [fastapi, deploy]\n    anyOf:\n      - \"backend\"\n      - \"monorepo\"\n      - \"service\"\n      - \"python\"\n      - \"golang\"\n    noneOf:\n      - \"turborepo cache\"\n      - \"turbo.json\"\n      - \"aws lambda\"\n      - \"docker compose\"\n    minScore: 6\nvalidate:\n  -\n    pattern: '@app\\.(get|post|put|delete|patch)\\s*\\(\\s*[''\"]\\\u002Fapi\\\u002F'\n    message: 'Do not include routePrefix in backend routes — Vercel strips the prefix before forwarding. Use @app.get(\"\u002Fhealth\") not @app.get(\"\u002Fapi\u002Fhealth\")'\n    severity: error\n  -\n    pattern: 'http\\.HandleFunc\\s*\\(\\s*[''\"]\\\u002Fapi\\\u002F'\n    message: 'Do not include routePrefix in Go handlers — Vercel strips the prefix. Use \"\u002Fhealth\" not \"\u002Fapi\u002Fhealth\"'\n    severity: error\nretrieval:\n  aliases:\n    - multi-service\n    - backend service\n    - services api\n    - monorepo deploy\n    - monorepo services\n  intents:\n    - deploy backend and frontend together on vercel\n    - set up python backend alongside next.js frontend\n    - configure multi-service vercel project\n    - add go backend to vercel project\n  entities:\n    - experimentalServices\n    - routePrefix\n    - entrypoint\n    - Services API\n    - vercel.json services\n  examples:\n    - deploy a fastapi backend with a react frontend\n    - add a go api service to my vercel project\n    - set up a multi-service monorepo on vercel\n---\n\n# Deploy multi-service projects with Vercel\n\nServices let you deploy multiple independently-built units within a single Vercel project. The typical use case is combining different runtimes (e.g. Python + JavaScript) in one deployment with shared routing and environment variables, but services work for any combination — multiple services of the same runtime, different frameworks, or a mix.\n\nThis skill covers **project structure and configuration**. For the actual deployment, defer to the **deployments-cicd** skill.\n\n## How It Works\n\nA service is an independently built unit within your project, deployed to the same domain under a unique subpath. At build time, Vercel builds each service separately. At request time, Vercel routes incoming requests to the correct service based on the URL path prefix (longest prefix wins).\n\n- Services are enabled via the `experimentalServices` field in `vercel.json` (see reference project).\n- `vercel dev -L` auto-detects frameworks and runs all services locally as one application, handling routing automatically. The `-L` flag (short for `--local`) runs without authenticating with Vercel Cloud.\n- Only `vercel.json` lives at the root. Each service manages its own dependencies independently.\n\n## Configuration\n\nDefine services in `vercel.json`:\n\n```json\n{\n  \"experimentalServices\": {\n    \"web\": {\n      \"entrypoint\": \"apps\u002Fweb\",\n      \"routePrefix\": \"\u002F\"\n    },\n    \"api\": {\n      \"entrypoint\": \"backend\u002Fmain.py\",\n      \"routePrefix\": \"\u002Fserver\"\n    }\n  }\n}\n```\n\nThe project's Framework Preset must be set to **Services** in the Vercel dashboard.\n\n### Configuration fields\n\n| Field          | Required | Description                                                |\n|----------------|----------|------------------------------------------------------------|\n| `entrypoint`   | Yes      | Path to the service entrypoint file or directory.          |\n| `routePrefix`  | Yes      | URL path prefix for routing (e.g. `\u002F`, `\u002Fapi`, `\u002Fsvc\u002Fgo`). |\n| `framework`    | No       | Framework slug. Pins detection; auto-detected if unset.    |\n| `memory`       | No       | Max available RAM in MB (128–10,240).                      |\n| `maxDuration`  | No       | Execution timeout in seconds (1–900).                      |\n| `includeFiles` | No       | Glob patterns for files to include in the deployment.      |\n| `excludeFiles` | No       | Glob patterns for files to exclude from the deployment.    |\n\nDo not add unknown fields — they will cause the build to fail.\n\n## Supported runtimes and frameworks\n\nServices is in beta. **Python** and **Go** are tested and production-ready. Other runtimes may work but are not yet validated.\n\n### Python\n\nWorks with FastAPI, Flask, Django, or any ASGI\u002FWSGI application. Framework is auto-detected. Set `entrypoint` to the application file (e.g. `\"backend\u002Fmain.py\"`). Dependencies go in `pyproject.toml` in the service directory.\n\n### Go\n\nSet `entrypoint` to the service **directory** (e.g. `\"backend\"`), not a file. **Must** set `\"framework\": \"go\"` explicitly in `vercel.json` — auto-detection does not work for Go services. Dependencies in `go.mod` in the service directory.\n\n### Other runtimes (untested)\n\nVercel supports Node.js, Bun, Rust, Ruby, Wasm, and Edge runtimes for functions. These can theoretically be used as services but are not yet validated.\n\n## Routing\n\nVercel evaluates route prefixes from longest to shortest (most specific first), with the primary service (`\u002F`) as the catch-all. Vercel automatically mounts services at their `routePrefix`, so service handlers should **not** include the prefix in their routes.\n\nFor frontend frameworks mounted on a subpath (not `\u002F`), configure the framework's own base path (e.g. `basePath` in `next.config.js`) to match `routePrefix`.\n\n## Environment variables\n\nVercel auto-generates URL variables so services can find each other:\n\n| Variable                        | Example value                            | Availability | Use case                              |\n|---------------------------------|------------------------------------------|--------------|---------------------------------------|\n| `{SERVICENAME}_URL`             | `https:\u002F\u002Fyour-deploy.vercel.app\u002Fsvc\u002Fapi` | Server-side  | Server-to-server requests             |\n| `NEXT_PUBLIC_{SERVICENAME}_URL` | `\u002Fsvc\u002Fapi`                               | Client-side  | Browser requests (relative, no CORS)  |\n\n`SERVICENAME` is the key name from `experimentalServices`, uppercased. If you define an env var with the same name in project settings, your value takes precedence.\n\n## Usage\n\n1. Read `references\u002Ffastapi-vite\u002F` for the canonical project layout.\n2. Adapt the structure to the user's chosen runtimes — services can use any supported runtime, not just the ones in the reference.\n3. Define service routes **without** the route prefix — Vercel strips the prefix before forwarding.\n4. Validate that each service in `vercel.json` has `entrypoint` and `routePrefix`. Only set `framework` when auto-detection fails (required for Go).\n\n## Output\n\nAfter scaffolding, present the created file structure to the user. After deployment, present the deployment URL (refer to the **deployments-cicd** skill for details).\n\n## Troubleshooting\n\n### 404 on routes after deployment\n\nThe project needs the Services framework preset:\n\n1. Go to Project Settings → Build & Deployment → Framework Preset\n2. Select **Services** from the dropdown\n3. Redeploy\n\n### Routes return unexpected results\n\n1. Ensure all services are picked up by `vercel dev` — check logs. If a service is missing, verify `vercel.json`. Try setting `framework` explicitly.\n2. Validate route prefix behavior: handlers declare routes without `routePrefix` (e.g. `\u002Fhealth`), but requests from other services use the full prefix (e.g. `\u002Fapi\u002Fhealth`).\n3. For frontend services on a subpath, confirm the framework's base path config matches `routePrefix`.\n","# Deploy multi-service projects with Vercel\n\nServices let you deploy multiple independently-built units within a single Vercel project. The typical use case is combining different runtimes (e.g. Python + JavaScript) in one deployment with shared routing and environment variables, but services work for any combination — multiple services of the same runtime, different frameworks, or a mix.\n\nThis skill covers **project structure and configuration**. For the actual deployment, defer to the **deployments-cicd** skill.\n\n## How It Works\n\nA service is an independently built unit within your project, deployed to the same domain under a unique subpath. At build time, Vercel builds each service separately. At request time, Vercel routes incoming requests to the correct service based on the URL path prefix (longest prefix wins).\n\n- Services are enabled via the `experimentalServices` field in `vercel.json` (see reference project).\n- `vercel dev -L` auto-detects frameworks and runs all services locally as one application, handling routing automatically. The `-L` flag (short for `--local`) runs without authenticating with Vercel Cloud.\n- Only `vercel.json` lives at the root. Each service manages its own dependencies independently.\n\n## Configuration\n\nDefine services in `vercel.json`:\n\n```json\n{\n  \"experimentalServices\": {\n    \"web\": {\n      \"entrypoint\": \"apps\u002Fweb\",\n      \"routePrefix\": \"\u002F\"\n    },\n    \"api\": {\n      \"entrypoint\": \"backend\u002Fmain.py\",\n      \"routePrefix\": \"\u002Fserver\"\n    }\n  }\n}\n```\n\nThe project's Framework Preset must be set to **Services** in the Vercel dashboard.\n\n### Configuration fields\n\n| Field          | Required | Description                                                |\n|----------------|----------|------------------------------------------------------------|\n| `entrypoint`   | Yes      | Path to the service entrypoint file or directory.          |\n| `routePrefix`  | Yes      | URL path prefix for routing (e.g. `\u002F`, `\u002Fapi`, `\u002Fsvc\u002Fgo`). |\n| `framework`    | No       | Framework slug. Pins detection; auto-detected if unset.    |\n| `memory`       | No       | Max available RAM in MB (128–10,240).                      |\n| `maxDuration`  | No       | Execution timeout in seconds (1–900).                      |\n| `includeFiles` | No       | Glob patterns for files to include in the deployment.      |\n| `excludeFiles` | No       | Glob patterns for files to exclude from the deployment.    |\n\nDo not add unknown fields — they will cause the build to fail.\n\n## Supported runtimes and frameworks\n\nServices is in beta. **Python** and **Go** are tested and production-ready. Other runtimes may work but are not yet validated.\n\n### Python\n\nWorks with FastAPI, Flask, Django, or any ASGI\u002FWSGI application. Framework is auto-detected. Set `entrypoint` to the application file (e.g. `\"backend\u002Fmain.py\"`). Dependencies go in `pyproject.toml` in the service directory.\n\n### Go\n\nSet `entrypoint` to the service **directory** (e.g. `\"backend\"`), not a file. **Must** set `\"framework\": \"go\"` explicitly in `vercel.json` — auto-detection does not work for Go services. Dependencies in `go.mod` in the service directory.\n\n### Other runtimes (untested)\n\nVercel supports Node.js, Bun, Rust, Ruby, Wasm, and Edge runtimes for functions. These can theoretically be used as services but are not yet validated.\n\n## Routing\n\nVercel evaluates route prefixes from longest to shortest (most specific first), with the primary service (`\u002F`) as the catch-all. Vercel automatically mounts services at their `routePrefix`, so service handlers should **not** include the prefix in their routes.\n\nFor frontend frameworks mounted on a subpath (not `\u002F`), configure the framework's own base path (e.g. `basePath` in `next.config.js`) to match `routePrefix`.\n\n## Environment variables\n\nVercel auto-generates URL variables so services can find each other:\n\n| Variable                        | Example value                            | Availability | Use case                              |\n|---------------------------------|------------------------------------------|--------------|---------------------------------------|\n| `{SERVICENAME}_URL`             | `https:\u002F\u002Fyour-deploy.vercel.app\u002Fsvc\u002Fapi` | Server-side  | Server-to-server requests             |\n| `NEXT_PUBLIC_{SERVICENAME}_URL` | `\u002Fsvc\u002Fapi`                               | Client-side  | Browser requests (relative, no CORS)  |\n\n`SERVICENAME` is the key name from `experimentalServices`, uppercased. If you define an env var with the same name in project settings, your value takes precedence.\n\n## Usage\n\n1. Read `references\u002Ffastapi-vite\u002F` for the canonical project layout.\n2. Adapt the structure to the user's chosen runtimes — services can use any supported runtime, not just the ones in the reference.\n3. Define service routes **without** the route prefix — Vercel strips the prefix before forwarding.\n4. Validate that each service in `vercel.json` has `entrypoint` and `routePrefix`. Only set `framework` when auto-detection fails (required for Go).\n\n## Output\n\nAfter scaffolding, present the created file structure to the user. After deployment, present the deployment URL (refer to the **deployments-cicd** skill for details).\n\n## Troubleshooting\n\n### 404 on routes after deployment\n\nThe project needs the Services framework preset:\n\n1. Go to Project Settings → Build & Deployment → Framework Preset\n2. Select **Services** from the dropdown\n3. Redeploy\n\n### Routes return unexpected results\n\n1. Ensure all services are picked up by `vercel dev` — check logs. If a service is missing, verify `vercel.json`. Try setting `framework` explicitly.\n2. Validate route prefix behavior: handlers declare routes without `routePrefix` (e.g. `\u002Fhealth`), but requests from other services use the full prefix (e.g. `\u002Fapi\u002Fhealth`).\n3. For frontend services on a subpath, confirm the framework's base path config matches `routePrefix`.\n",{"name":5,"summary":55,"metadata":56,"validate":107,"retrieval":114,"description":7},"Deploy multiple services in one Vercel project — e.g. a Python backend alongside a JS frontend",{"docs":57,"sitemap":59,"priority":60,"bashPatterns":61,"pathPatterns":68,"promptSignals":81,"importPatterns":106},[58],"https:\u002F\u002Fvercel.com\u002Fdocs\u002Fservices","https:\u002F\u002Fvercel.com\u002Fsitemap\u002Fdocs.xml",7,[62,63,64,65,66,67],"\\bvercel\\s+dev\\b.*-L","\\bpip\\s+install\\b.*fastapi","\\buv\\s+(sync|pip|run)\\b","\\bgo\\s+(run|build|mod)\\b","\\bpython\\s+-m\\s+uvicorn\\b","\\buvicorn\\b",[69,70,71,72,73,74,75,76,77,78,79,80],"backend\u002F**","backend\u002Fmain.py","backend\u002Fmain.go","backend\u002Fgo.mod","backend\u002Fpyproject.toml","backend\u002Frequirements.txt","frontend\u002F**","apps\u002F*\u002Fbackend\u002F**","apps\u002F*\u002Ffrontend\u002F**","services\u002F*\u002Fvercel.json","*\u002Fpyproject.toml","*\u002Fgo.mod",{"allOf":82,"anyOf":94,"noneOf":96,"phrases":99,"minScore":105},[83,85,87,89,91,93],[84,43],"backend",[86,32],"python",[88,32],"go",[84,90],"deploy",[92,46],"service",[44,90],[84,46,92,86,95],"golang",[97,98,41,49],"turborepo cache","turbo.json",[100,30,101,34,40,44,102,103,104],"services api","multi-service","deploy backend","backend and frontend","multiple services",6,[44],[108,111],{"message":109,"pattern":110,"severity":35},"Do not include routePrefix in backend routes — Vercel strips the prefix before forwarding. Use @app.get(\"\u002Fhealth\") not @app.get(\"\u002Fapi\u002Fhealth\")","@app\\.(get|post|put|delete|patch)\\s*\\(\\s*['\"]\\\u002Fapi\\\u002F",{"message":112,"pattern":113,"severity":35},"Do not include routePrefix in Go handlers — Vercel strips the prefix. Use \"\u002Fhealth\" not \"\u002Fapi\u002Fhealth\"","http\\.HandleFunc\\s*\\(\\s*['\"]\\\u002Fapi\\\u002F",{"aliases":115,"intents":119,"entities":124,"examples":130},[101,116,100,117,118],"backend service","monorepo deploy","monorepo services",[120,121,122,123],"deploy backend and frontend together on vercel","set up python backend alongside next.js frontend","configure multi-service vercel project","add go backend to vercel project",[125,126,127,128,129],"experimentalServices","routePrefix","entrypoint","Services API","vercel.json services",[131,132,133],"deploy a fastapi backend with a react frontend","add a go api service to my vercel project","set up a multi-service monorepo on vercel","9a4409c8751439c3aeeea2bc3940ba05dc3cd3b5","plugins\u002Fvercel\u002Fskills\u002Fvercel-services",0,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FNagyVikt","https:\u002F\u002Fwebu.hu\u002F","Codex is a tool they said...\r\n\r\nCreator of GitGuardex, CueCards. Tech stack: Next.js · TypeScript · Rust · Linux. ","2026-03-30 02:19:53",{"source":8,"skillName":5,"commands":143,"prompt":153,"zipAvailable":154},[144,147,150],{"tool":145,"command":146},"npx","npx skills add NagyVikt\u002Fcodex-plugins --skill vercel-services",{"tool":148,"command":149},"bunx","bunx skills add NagyVikt\u002Fcodex-plugins --skill vercel-services",{"tool":151,"command":152},"pnpm","pnpm dlx skills add NagyVikt\u002Fcodex-plugins --skill vercel-services","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",true,[156,162,166,172],{"path":157,"resourceType":158,"resourceTypeDesc":159,"sizeBytes":160,"sourceHtmlUrl":161},"references\u002Ffastapi-vite\u002Fbackend\u002Fpyproject.toml","REFERENCE","参考文档",165,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Fbackend\u002Fpyproject.toml",{"path":163,"resourceType":158,"resourceTypeDesc":159,"sizeBytes":164,"sourceHtmlUrl":165},"references\u002Ffastapi-vite\u002Ffrontend\u002Fpackage.json",320,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Ffrontend\u002Fpackage.json",{"path":167,"resourceType":168,"resourceTypeDesc":169,"sizeBytes":170,"sourceHtmlUrl":171},"references\u002Ffastapi-vite\u002Ffrontend\u002Fvite.config.ts","SCRIPT","脚本",133,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Ffrontend\u002Fvite.config.ts",{"path":173,"resourceType":158,"resourceTypeDesc":159,"sizeBytes":174,"sourceHtmlUrl":175},"references\u002Ffastapi-vite\u002Fvercel.json",208,"https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002Freferences\u002Ffastapi-vite\u002Fvercel.json",[177,215,246,269,291,307],{"skillNo":178,"name":179,"nameZh":6,"description":180,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":181,"categories":182,"keywords":195,"publishedAt":50},"01M6K1ZEN8P9R2S6NPNJNJ8JVH","workflow","Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[183,184,187,192],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":188,"categoryName":189,"taxonomyType":190,"taxonomyTypeDesc":191},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":193,"categoryName":194,"taxonomyType":190,"taxonomyTypeDesc":191},"01JBSEEDCAT000000000000038","人力资源",[179,196,197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214],"workflows","create","run","streaming","logs","start","why","loop","wait for","branch","auto","log","conversation","human","lib","condition","rendering","retries","sleep",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":231,"publishedAt":50},"01M6K1Z71NWFSPHK2VJJ73MVSY","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[221,224,225,228],{"categoryNo":222,"categoryName":223,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":226,"categoryName":227,"taxonomyType":190,"taxonomyTypeDesc":191},"01JBSEEDCAT000000000000031","产品经理",{"categoryNo":229,"categoryName":230,"taxonomyType":190,"taxonomyTypeDesc":191},"01JBSEEDCAT000000000000033","数据分析师",[217,232,199,233,234,235,205,236,237,238,239,39,240,37,241,242,35,243,244,245],"auth","routing middleware","api","projects","user story","full stack","jest","local","end","false","unit","middleware","loading","unit test",{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":250,"categories":251,"keywords":253,"publishedAt":50},"01M6K1YPRYJS3BQEDP8HKBHPEJ","vercel-storage","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\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[252],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[254,255,32,256,198,257,258,206,259,260,261,262,263,264,37,210,265,266,267,268],"storage","vercel storage","config","supabase","migrate","router","clerk","expert","prisma","connection pooling","neon","turso","upstash","URL","auth0",{"skillNo":270,"name":271,"nameZh":6,"description":272,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":273,"categories":274,"keywords":275,"publishedAt":50},"01M6K1Y8S3CRD43DPKX0PK1MTT","vercel-sandbox","Vercel Sandbox guidance — ephemeral Firecracker microVMs for running untrusted code safely. Supports AI agents, code generation, and experimentation. Use when executing user-generated or AI-generated code in isolation.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-sandbox\u002FSKILL.md",[],[276,277,32,278,279,197,198,280,281,282,283,284,285,286,287,288,244,289,271,290],"sandbox","vercel sandbox","safe","ai agents","code","ai sdk","Code Generation","playground","generated","spawn","install","runner","io","child","student",{"skillNo":292,"name":293,"nameZh":6,"description":294,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":295,"categories":296,"keywords":298,"publishedAt":50},"01M6K1Y1J8S7AN97H75SHBGF7J","vercel-queues","Vercel Queues guidance (public beta) — durable event streaming with topics, consumer groups, retries, and delayed delivery. $0.60\u002F1M ops. Powers Workflow DevKit. Use when building async processing, fan-out patterns, or event-driven architectures.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-queues\u002FSKILL.md",[297],{"categoryNo":185,"categoryName":186,"taxonomyType":21,"taxonomyTypeDesc":22},[299,32,179,196,199,300,48,234,47,33,301,302,303,304,37,210,305,213,244,306],"vercel queues","beta","message","delivery","across","worker","processing","at",{"skillNo":308,"name":309,"nameZh":6,"description":310,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":311,"categories":312,"keywords":314,"publishedAt":50},"01M6K1XH0K0KC0CB51QFWYQ3NM","vercel-functions","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.","https:\u002F\u002Fgithub.com\u002FNagyVikt\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-functions\u002FSKILL.md",[313],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[315,32,316,199,200,203,259,317,261,318,239,319,39,320,264,37,36,321,213,322],"vercel functions","functions","vercel ai sdk","time","shared","express","cold","move"]